Is it better to have 2 Managed SQL Instances RRS feed

  • Question

  • We have an app that connects to a SQL both in CA and an App that connects to a SQL Both in NJ. Migrating to Managed Azure SQL. Is it better to have just one managed SQL Instance or should I have 2 Managed SQL Instances in the East and West Coast?

    Software by spearWare

    Thursday, November 7, 2019 3:54 AM

All replies

  • https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-connectivity-architecture

    Best Regards,Uri Dimant SQL Server MVP, http://sqlblog.com/blogs/uri_dimant/

    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting: Large scale of database and data cleansing
    Remote DBA Services: Improves MS SQL Database Performance
    SQL Server Integration Services: Business Intelligence

    Thursday, November 7, 2019 4:58 AM
  • Hi CraigBB,

    What is the issue you are attempting to resolve, such as latency? If you had two SQL instances, one in West US and the 2nd in East US, would there be a requirements to keep the two in sync? This would be the case if you were to store customer account data, etc.

    Part of the solution would be to use geographic traffic routing where you have an application deployed in West US and a second deployed in East US, and the Azure Traffic Manager will route requests to the closest region. Please see: Configure the geographic traffic routing method using Traffic Manager

    This functionality will mitigate latency and ensure your user(s) are connecting to the closest deployed application instance on each coast. You could deploy a Central US instance so that customers in the midwest and south central US had a closer endpoint than each coast to connect with.

    The other part of this solution is the database deployment. You could deploy the database in Central US, which would take advantage of Azure high bandwidth network traffic, and mitigate the complexities of data sync. Or you could also deploy an Azure SQL instance along with each application instance, and run data sync between the two to keep each database in sync.

    Azure has a concept of Paired Regions which is more about business continuity and disaster recovery but there is also additional network capacity built-in that you could leverage. It also ensures one instance of your solution is always available during planned maintenance, etc. West US and East US is an example of a paired region. This is also something to consider.

    Please let us know if you have additional questions or please detail more information about your requirements, as this will narrow down your options.



    Thursday, November 7, 2019 8:17 PM
  • I am substantiating Mike's response and I am going to propose it as the answer.

    If it answers your query, do click “Mark as Answer” and Up-Vote for the same which might be beneficial to other community members reading this thread .

    And, if you have any further query do let us know. 

    Monday, November 11, 2019 3:03 AM