Episode 90 - Windows Azure Web Sites Update
- Posted: Sep 22, 2012 at 11:51 AM
- 39,743 Views
- 5 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
In this episode Nick and Nate checkout the latest updates to Windows Azure Web Sites and Windows Azure SQL Database.
In the News:
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Good episode. I went and configured my Azure website to use a custom domain in Shared Mode and had it working in minutes. Awesome!
Really exciting stuff! I'm especially interested in the updates on Azure SQL Databases. Does the new Linked server stuff mean that you can have cross-database queries inside Azure as well, or only from on-premise SQL Server?
In real-world cross-database queries are used without a second thought, and porting over to azure is hard when this is not enabled..
Hi hansol,
Currently you can only perform the linked server operation on your on prem db to link to an Azure SQL Database as demonstrated in the video.
If you really need the scenario you described the approach would be to use a SQL VMs in Azure
kind regards,
nick
@nickharris:
Thanks for the quick reply, Nick!
Cross-database is almost always a bad design anyway (schemas anyone?). SQL VMs is cool but they don't provide real high-availability out-of-the-box the way Azure SQL Databases do, you know.
Still wish we could go back (officially) to calling it "SQL Azure" ... "Azure SQL Database" is too long ... to clunky ... sounds dumb. You can't say "SQL Database" all by itself, because that doesn't tell you anything. I still think you should have a chat with marketing about changing it back. "SQL Azure" and "SQL Server" ... quick, easy, right to the point, no minunderstandings. I'm going to be a rebel and keep calling it "SQL Azure."
Remove this comment
Remove this thread
close