Comments
Sort by recent activity
When you use backups (which retain the target meta) rather than restoring to a local or aliased database for the comparison, then the USE statement option would certainly be appropriate.
jimboh / comments
When you use backups (which retain the target meta) rather than restoring to a local or aliased database for the comparison, then the USE statement option would certainly be appropriate.
jimboh
Further to this issue, I am noticing that even if I have 2 or 3 backup files referenced in the list, and check a particular one (other than the first) of these for the comparison, that it will still only use the initial backup file. Thus the ability to switch is not as expected.
Jimboh / comments
Further to this issue, I am noticing that even if I have 2 or 3 backup files referenced in the list, and check a particular one (other than the first) of these for the comparison, that it will stil...
I am also concerned about a solution to this.
In a current case script there were 15 cases of FK DROP CONSTRAINT statement duplication ( out of 18 needed).
Note: I am running the script in SQL Server Management Studio. The issue did not occur on prior occasions running directly from SQLDataCompare.
One also wonders whether it would be better to Disable rather than DROP and ADD Constraints. / comments
I am also concerned about a solution to this.
In a current case script there were 15 cases of FK DROP CONSTRAINT statement duplication ( out of 18 needed).
Note: I am running the script in SQL Serv...
[image] There must be a poormans solution.. / comments
There must be a poormans solution..