Choose when to calculate static data changes
Our static data tables can have a few thousand rows each. It's costly to have the rows compared every time the SQL Source Control tab is opened to push/pull schema changes (which are much faster to compute). Can the schema and data aspects of this tool be separated to prevent excessive comparisons on data that by nature changes very infrequently.
The option to disable data change detection is now available from the Setup tab in the Frequent Updates build, and will be available in the next main version of the product.
If you want to get the Frequent Updates builds, more details can be found at http://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates.
Mary Hamlin commented
Exactly. We have some huge static tables containing geographic data, and having to rescan for changes each time you restart ssms and connect to the database is still unacceptable for us. We're going to have to unlink the static data.
Jason Moore commented
It'd be a good start, but it would be more useful for it to be session-independent.
Could you make use of the modify_date from sys.tables to determine whether or not to rescan the table(s)?