Comments
2 comments
-
Hi,
If you're changing a lot of data, yes, this doesn't sound too unusual. The reason for this is that with the default options, SQL Data Compare makes all changes within a transaction. This means that if anything goes wrong, it can roll everything back and leave the database as it was before the attempt.
You can disable the use of transactions in the project "Options" tab - under Synchronization Behaviour, there's an option for "Use transactions in SQL scripts". However, if an operation does fail, the database may be left partially synchronized.
Alternatively, there's documentation on how to shrink a log file that's grown beyond what you'd normally need at MSDN.
Hope that helps,
Robert -
Thanks that worked.
Add comment
Please sign in to leave a comment.
I am running SQL Express 2005.