Replicating Data with Azure SQL Data Sync
Do you find you need to keep SQL Server tables in sync across multiple systems? After several projects involving synching data, we return to the topic of Azure SQL Data Sync with some real world examples of why we choose this option and how it worked for us. While there are some limitations, the feature is very stable, and we have had minimal, minor issues with it. Ideal for environments where latency is flexible, Azure SQL Data Sync could be a very helpful feature to get your data moved.
Why would you want to use this? Because you’ve got data that you want to move around, and it doesn’t have to be all of the database.
Meet the Hosts
With more than 10 years of working with SQL Server, Carlos helps businesses ensure their SQL Server environments meet their users’ expectations. He can provide insights on performance, migrations, and disaster recovery. He is also active in the SQL Server community and regularly speaks at user group meetings and conferences. He helps support the free database monitoring tool found at databasehealth.com and provides training through SQL Trail events.
Eugene works as an independent BI consultant and Pluralsight author, specializing in Power BI and the Azure Data Platform. He has been working with data for over 8 years and speaks regularly at user groups and conferences. He also helps run the GroupBy online conference.
Kevin is a Microsoft Data Platform MVP and proprietor of Catallaxy Services, LLC, where he specializes in T-SQL development, machine learning, and pulling rabbits out of hats on demand. He is the lead contributor to Curated SQL, president of the Triangle Area SQL Server Users Group, and author of the books PolyBase Revealed (Apress, 2020) and Finding Ghosts in Your Data: Anomaly Detection Techniques with Examples in Python (Apress, 2022). A resident of Durham, North Carolina, he can be found cycling the trails along the triangle whenever the weather's nice enough.