Compare not detecting ALLOW_SNAPSHOT_ISOLATION

Compares and synchronizes SQL Server databases, backups and scripts.

Moderators: JonathanWatts, Chris Auckland, David Atkinson, eddie davis, Anu Deshpande, Michelle Taylor, alice.easey, james.billings, chengvoon.tong

Compare not detecting ALLOW_SNAPSHOT_ISOLATION

Postby paulh » Mon Jul 07, 2014 10:27 am

I'm doing a full compare but SQL Compare is not detecting the ALLOW_SNAPSHOT_ISOLATION setting

Is it not supported or do I have to change other parameters?

Paul
paulh
 
Posts: 33
Joined: Sat Oct 08, 2005 5:28 pm

Postby Brian Donahue » Wed Jul 09, 2014 2:51 pm

Hi Paul,

I don't believe SQL Compare is meant to synchronize any database-level configuration properties, except when required to add an object, for instance enabling FULLTEXT so that it can synchronize a full text catalog.

If this setting is causing an object synchronization to fail, I can definitely put in a change request for SQL Compare to support it.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby paulh » Thu Jul 10, 2014 12:46 pm

Brian

The background was that we are doing application development against a database and hit a throughput problem, so we changed the transaction option from serializable to snapshot, which requires the ALLOW_SNAPSHOT_ISOLATION setting to work.

The issue is that every other bit of the database, schema, tables, views, indices etc in in source control which means we can promote changes through the environments in a controller manner - except for this one!

I'd suggest having a database settings comparison section so that we can choose whether these are synchronised or not, ok it's not schema synchronization but it does make a difference to the functionality of the database and if it's out of sync can break applications.
paulh
 
Posts: 33
Joined: Sat Oct 08, 2005 5:28 pm


Return to SQL Compare 10

Who is online

Users browsing this forum: No registered users and 0 guests