Good morning,
We are migrating databases to SQL Azure to leave the current older infrastructure. The decisions was made to not upgrade the infrastructure. The thought was to migrate to the new cloud technology.
The issue we are seeing is that SQL Azure appears to be slower and more complicated.
1. We normally deploy major vendor applications with the vendor database. We would normally create another database outside of the vendor database for custom tables. However, with SQL Azure, you can't just query across databases. You have to create elastic queries. I am reading that you need to create shards, shard manager, a shard application and a bunch of other things.
2. The cross database querying with SQL Azure elastic querying seems to be a lot slower.
Has any one deployed a major vendor application using SQL Azure as the database backend? Does it seem to anyone that for major vendor applications that it may still be better to spin up a real good SQL Server VM on premise?
Thanks for any opinion that you may have to share as we plan our databases deployments for this year.
Tony
Out of interest, is the application a web app, or a desktop app, and will the app piece be on Azure or on premise?
The app is a web app. It will be mostly hosted in SQL Azure. However, some components will be in SQL Server 2016 on premise.
Things will work out. Get back up, change some parameters and recode.