switching to Azure, how to keep dev and prod schema up to date if we plan to use external tables

Question

switching to Azure, how to keep dev and prod schema up to date if we plan to use external tables

ebooklub

Hall of Fame

Points: 3905
More actions
June 21, 2018 at 9:24 am

#355625

Hi,
I am creating proof of concept for migration of db application to azure databases (we plan to take advantage of gee-replication, readable replicas, possibility to extend resources and less routine DBA tasks 🙂 )
after migration we need to use elastic queries (application use 3 databases and with cross references)
elastic queries manage cross references by creating external tables.
Since we use external tables our local development servers become useless and we need to move development also in cloud
Does MS charge same amount for development environment in cloud ?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

SteveHaselschwerdt SSC Veteran Points: 295 More actions · Answer 1

I think that you can get discounts like they mention here: https://azure.microsoft.com/en-us/pricing/dev-test/. We have a Microsoft rep that we use on a regular basis to help out with pricing for these things. I don't work directly with that individual, but our IT department has had relatively good experiences. Hope that helps.

ebooklub Hall of Fame Points: 3905 More actions · Answer 2

Thank for the tip, yes if you start pricing calculation from link https://azure.microsoft.com/en-us/pricing/dev-test/ you get DEV cost.

compare to prod cost

SteveHaselschwerdt SSC Veteran Points: 295 More actions · Answer 3

Keep in mind the amount of DTUs you have available. I feel like that contributed a fair bit to that price. I know for a fact that we can have either the S0 or S6 on our prod and dev environments.

Grant Fritchey SSC Guru Points: 398890 More actions · Answer 4

You can do a lot of development locally and then deploy to the cloud.

However, cross database queries are horrifyingly slow and difficult to maintain within Azure SQL Database. You are either better off engineering around that and using some other method, or, work to get into managed instances where you can do cross database queries the old-fashioned way.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

ebooklub Hall of Fame Points: 3905 More actions · Answer 5

Grant Fritchey - Tuesday, June 26, 2018 5:16 AM
You can do a lot of development locally and then deploy to the cloud.
However, cross database queries are horrifyingly slow and difficult to maintain within Azure SQL Database. You are either better off engineering around that and using some other method, or, work to get into managed instances where you can do cross database queries the old-fashioned way.

Thanks for tip about performance of cross database queries
Managed instances do not support geo replication (:
we have several "external tables" in each db, I will convince team to redesign this part