SQL Change Automation 4

Improving performance in Visual Studio and SSMS

Improving performance when refreshing the list of differences

Shadow database location

Performance will inevitably be slightly worse when working with large databases.

This can be alleviated somewhat if the connection to the shadow database is fast. It is usually best if the shadow database is located on the same machine as SQL Change Automation.

The shadow database usually defaults to being on the same machine as the development database. You can instead configure your shadow database explicitly.

Static data

Tracking data on tables that contain a large number of rows can slow down comparisons.

Please see our recommendations on how to work with large sets of data.


Didn't find what you were looking for?