Hi,

I have followed this article to develop a dataflow which will move data between two tables on different Azure SQL databases:

https://learn.microsoft.com/en-us/azure/data-factory/concepts-data-flow-schema-drift

I also enable schema drift in the data flow on both source and sink, and made sure auto mapping is enabled, and both source and destination data sets have no schema definitions.

When I run the flow, it works and move data but it doesn’t detect schema changes. If I add a new column in the source table it won’t come through to a destination table.

The only reason I can think of is that schema drift is not supported by Managed Virtual Network runtime, which I have used to create linked services for source and destination.

Can someone confirm wheter that would be the case?

Many Thanks,

WJ

​Hi, I have followed this article to develop a dataflow which will move data between two tables on different Azure SQL databases: https://learn.microsoft.com/en-us/azure/data-factory/concepts-data-flow-schema-drift I also enable schema drift in the data flow on both source and sink, and made sure auto mapping is enabled, and both source and destination data sets have no schema definitions. When I run the flow, it works and move data but it doesn’t detect schema changes. If I add a new column in the source table it won’t come through to a destination table. The only reason I can think of is that schema drift is not supported by Managed Virtual Network runtime, which I have used to create linked services for source and destination. Can someone confirm wheter that would be the case? Many Thanks, WJ  Read More

​