How can we improve Azure SQL Database?

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.

1,263 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    anonymousanonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    EllisEllis shared a merged idea: allow interdatabase joins.  ·   · 
    TriciaTricia shared a merged idea: Add ability to reference data in a sql azure database from a stored procedure in another SQL database. Cross Query Azure databases.  ·   · 
    anonymousanonymous shared a merged idea: Linked Server  ·   · 
    anonymousanonymous shared a merged idea: Allow 3-part synonyms (database.schema.object) to use other databases in the server.  ·   · 


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      • XxBladesxXXxBladesxX commented  ·   ·  Flag as inappropriate

        I want:
        SELECT *
        INTO [TargetDB].[dbo].[TargetTable]
        FROM [SourceDB].[dbo].[SourceTable]

      • Adam CallenAdam Callen commented  ·   ·  Flag as inappropriate

        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 WysongCharles Wysong commented  ·   ·  Flag as inappropriate

        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.

      • Anonymous commented  ·   ·  Flag as inappropriate

        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...

      • Anonymous commented  ·   ·  Flag as inappropriate

        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 MillerRoger Miller commented  ·   ·  Flag as inappropriate

        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

      • benjbenj commented  ·   ·  Flag as inappropriate

        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.

      • AnsonAnson commented  ·   ·  Flag as inappropriate

        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 BorrieRichard Borrie commented  ·   ·  Flag as inappropriate

        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.

      • JamesJames commented  ·   ·  Flag as inappropriate

        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.

      • RickRick commented  ·   ·  Flag as inappropriate

        Amazon's MSSQL offering does not have this limitation. I am currently using that with much success, maybe you need to look there.

      • JasonJason commented  ·   ·  Flag as inappropriate

        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.

      • Gowtham KunduruGowtham Kunduru commented  ·   ·  Flag as inappropriate

        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'BrienEd O'Brien commented  ·   ·  Flag as inappropriate

        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 ButlerScott Butler commented  ·   ·  Flag as inappropriate

        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 WagerGraham Wager commented  ·   ·  Flag as inappropriate

        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.

      ← Previous 1 3

      Feedback and Knowledge Base