Cross database reference
The ability to query (read-only) data from a difference database or linked server. This will allow to reference (join) some tables from the source database and build views that uses two or more SQL Azure databases.
We currently have a number of database on a single azure database server. I would like to be able to do joins between these servers. I understand this is not possible. As a work around we have had to copy a lot data and place it on each database rather then share the data between the databases. This is something we done routinly before using the azure cloud base service. Please allow for interdatabase connections.
Add ability to reference data in a sql azure database from a stored procedure in another SQL database.
In our S+S scenario we definitely need to be able to create linked servers against a cloud DB.
We are looking to better understand what customers are trying to do here. Are folks looking for cross DB query, or cross DB movement of data, or fan-out query. I’d love to hear the scenarios that you’re looking at. Please email me at firstname.lastname@example.org if you’d like to help us define how we move forward in this space.
Need cross database query support....now.
Adam Callen commented
This is just stupid. "We are looking to better understand what customers are trying to do here." Are you serious? I'm guessing that it's just technically difficult and you guys are playing dumb as opposed to figuring it out.
Charles Wysong commented
Ideally, cross database query support would exist. I'd be happy with a good way to do remote procedure calls via some analog to Linked Servers.
Any movement on this?
This is proving a blocker for us migrating to PaaS offering in Azure, instead facing the choice of IaaS VM's or going down the AWS route...
We've got an eshop that has it's own database, but takes most of the data about the goods from a replica of the main IS of the company and accesses that data using views referencing the other DB on the same MSSQL server. If we were to move to Azure DB, we'd have to replicate the data into the same database as the eShop and to keep things separate we'd have to change the "schema" and all references all around the system.
I think for more purposes it would not matter whether the crosreferenced databases are really a different databases as long as it looks like two databases to the SQL queries.
Roger Miller commented
We need to connect to a large database provided by a third party supplier and cross join with our own DB's The third party database changes on a regular basis and it's not feasible to import this into another DB. Please address this requirement
We would find this feature useful for migrating data to Azure
Yet another who'd like to see this. Doesn't have to be anything fancy- just let me join to a table in another db on the same instance. Sure I could put it all in one db but like others here I'm trying to keep everything clean and separate. I'd've thought MS would be happy we're paying for extra databases when we could potentially be putting everything in one db- this kind of thing will (at best) drive developers to use as few databases as possible and at worst send them elsewhere.
Cross database reference wasn't a new feature / technology of SQL Server in previous versions and editions, I'm surprised that Microsoft used 4 years to "Review" this request ....I guess it will remains "Review" in 2015.
Richard Borrie commented
Like others here we use multiple databases on the same server, and we can't move to Azure SQL database until we have the ability to "look across" from one DB to the other. We just want to be able to do a "select xyz from otherdb.dbo.othertable", or we want to be able to create a view in the current DB which reads data from the other DB.
We currently load data into a staging database from offline data sources for validation, before it is then loaded via overnight batch into the main database as part of a transaction.
I have come from an self-hosted environment where this is possible to Azure where it is not.
The only viable solution given my current deadline is to merge the databases, which is less than ideal.
Please can this feature be added.
Amazon's MSSQL offering does not have this limitation. I am currently using that with much success, maybe you need to look there.
What is the status of this feature? I'd like to know if we should abandon any hope of Microsoft support this and move off of SQL Database. We're currently still not happy with any alternatives to this problem.
I need cross database query (joins and transactions)
Gowtham Kunduru commented
it has been 4 years, but still the same. cross database query is very useful when you are dealing with multiple databases. please let us know if you are going to provide solution for this or not. if you can provide this so many customers are happy to use the feature.
Ed O'Brien commented
Looking for cross-database movement of data. The new backup/restore feature added last month is a great enhancement - would like the ability to update production database with subset of data from restored database.
Scott Butler commented
Major deal breaker. Many times our app uses other third-party frameworks, which have their own DB's and schema's. We like to keep things clean so we have our separate DB. Then we need to do some cross DB joins for special examples. Think about a Security framework with its own scheam in a Security DB, then I have my data in my separate DB. I want to keep them separate so I can easily upgrade the security framework when needed. However, I need to write some queries that join the two in many situations.
Graham Wager commented
Our current scenario would be greatly eased with this capability. We currently have an old and new system and are slowly migrating clients between the two. Being able to do this using just SQL would greatly reduce the time it would take.
Currently we're having to backup, download, restore then link from a local instance into Azure to perform the operation.
what is the alternate solution?