0

Our MI reporting solution involves pulling data on-prem into a DMZ from an Azure SQL server, via Azure Data-Sync, then performing ETL processes on it etc. The Azure SQL server is maintained by a third party who keeps adding columns to existing tables etc. and there currently aren't suitable change tracking protocols to get this information to us.

In our pre-production server they have altered a column's datatype, which is already established in the Data-Sync, from smallint to nvarchar(50).

This lovely post outlines how to handle the schema changes, however it doesn't outline behaviour for when the schema change isn't properly handled...

When this change gets pushed to production, will it break the data-sync?

Yemp
  • 1
  • 1
  • My guess, is yes. – Dan Bracuk Mar 22 '18 at 16:46
  • It would potentially break data-sync, if you can not alter back datatype in Azure portal, it could be good to handle in ETL packages, Unfortunately, it is only way as u said third party manages destination portal or Ask third party to follow change control process before making any changes to schema, objects and datatypes – Ven Mar 22 '18 at 16:50

0 Answers0