15 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Toby Page commented  ·  April 25, 2012 08:17  ·  Flag as inappropriate  ·  Delete

  Hugely important for our implementation. Left us with some horrid code-based solution (merging datatables) and thinking whether Azure is really right for us...

• Sudheer kumar commented  ·  April 12, 2012 01:05  ·  Flag as inappropriate  ·  Delete

  This would be helpful for migrations.

• Dhananjay commented  ·  April 11, 2012 23:41  ·  Flag as inappropriate  ·  Delete

  While Migrating, this will be very usefull feature

• Amit Arora commented  ·  April 05, 2012 00:57  ·  Flag as inappropriate  ·  Delete

  If this feature is available, a substantial number of existing apps can move to sql azure, not just those being written from scratch specifically targetting azure. Can you explain if there are any architeture level restrictions and is this feature at least being mulled over for a future release of azure?

• Anonymous commented  ·  February 17, 2012 02:16  ·  Flag as inappropriate  ·  Delete

  this is a big sad story since it was announced i think.

• Rick Jewson commented  ·  September 03, 2011 05:03  ·  Flag as inappropriate  ·  Delete

  Can we have an indication of whether this feature will be worked on soon? According to everyone I spoke to at AuTechEd, it was thought it must have been an oversight! Some form of roadmap would really help!

• meenxip commented  ·  August 16, 2011 23:41  ·  Flag as inappropriate  ·  Delete

  Cross Database reference is essential feature for many reasons. We must have it!

• Johan van Tonder commented  ·  August 03, 2011 05:41  ·  Flag as inappropriate  ·  Delete

  It would enable more possibilities for true cloud-computing, since our on-premise enterprise systems are based around a core database surrounded by other seperate application databases which "plugs" into the main one, hence cross database queries are the norm. With this in the cloud, building cloud-apps that build other apps becomes possible. If this is your everyday business, and it is not supported by SQL Azure, you cannot and will not move to SQL Azure.

• Aidan G commented  ·  July 22, 2011 13:19  ·  Flag as inappropriate  ·  Delete

  Hi
  This would be perfect for our setup. We have 600+ rules, since we will be running, eventually, 100's of databases, then I will have to replicate and maintain on each database, which is a pain :)

• Mike G commented  ·  June 29, 2011 08:50  ·  Flag as inappropriate  ·  Delete

  Again lots of our software writes queries that is across multiple databases, mostly on the same server. Without this we will not be able to move any of our products to SQL Azure. I can't think of any efficient way of running the queries without just merging all the databases into one big database... which I don;t want to do.

• Sridhar commented  ·  June 23, 2011 18:19  ·  Flag as inappropriate  ·  Delete

  our databases are heavily dependent on these.

• Melissa Sue Perry commented  ·  May 23, 2011 14:55  ·  Flag as inappropriate  ·  Delete

  we should get it for free for windows

• Tim Shaffer commented  ·  November 29, 2010 10:38  ·  Flag as inappropriate  ·  Delete

  I need to be able to Insert/Update data in 1 SQL Azure database with select results from another SQL Azure database inside a stored procedure. This is required to migrate my data warehousing databases to SQL Azure. Urgently needed within 60 days.

• Lukas Swom commented  ·  August 25, 2010 09:54  ·  Flag as inappropriate  ·  Delete

  yes this would be absolutely usefull!

• Simon Lampen commented  ·  December 20, 2009 13:18  ·  Flag as inappropriate  ·  Delete

  This would help with functions like warehousing of reporting data to another database to keep the main transactional db performant.