Activity overview
Latest activity by michmela44
http://redgate.uservoice.com/forums/390 ... are-option
Any chance someone from Red Gate will actually look at this? / comments
http://redgate.uservoice.com/forums/390 ... are-option
Any chance someone from Red Gate will actually look at this?
I see. I misread what you wrote, however, I would say we both still have the same problem. SQL Source Control chooses to do what it wants and doesn't let us control how the sync happens the way SQL Compare and SQL Data Compare do. / comments
I see. I misread what you wrote, however, I would say we both still have the same problem. SQL Source Control chooses to do what it wants and doesn't let us control how the sync happens the way SQL...
This is a bad bug/oversight.
Every time we "Get Latest" we now have "WITH NOCHECK" added on every table that had data changes....
Does Red Gate really think that all constraints should be disabled on the database? Why is that default across all of the tools when moving data?
Since I can't pick and choose which pieces of Schema changes I want to check in, it becomes a huge mess of manual updates that have to happen to remove the "WITH NOCHECK".
I've tried setting the defaults in Data Compare to force the constraints to be re-enabled, but SQL Source Control ignores them.
Seems obvious that for each database linked to Source Control, there should be a set of options for both Schema and Data compare similar to what is in the UI of each separate product so we can control how the sync takes place. Contraints, Case-Sensitive naming, column order, etc. / comments
This is a bad bug/oversight.
Every time we "Get Latest" we now have "WITH NOCHECK" added on every table that had data changes....
Does Red Gate really think that all constraints should be disabled...