Comments
Sort by recent activity
You're absolutely right, @David Atkinson. I made an incorrect assumption based on the command line switch documentation. After some experimentation (and removing 2nd instances of certain objects that prevented SQL Compare from loading the script files), I now have an Excel report showing drift between our db and repo. Thanks for your help! / comments
You're absolutely right, @David Atkinson. I made an incorrect assumption based on the command line switch documentation. After some experimentation (and removing 2nd instances of certain objects t...
A year later and I'm running into this same issue but now with SQL Compare. I have a sql repo reconciliation report that uses SQL Compare to show all objects with sql discrepancies between the repo and the database. CREATE OR ALTER is the preferred way to implement sql changes in our shop, so this report is returning many false positives because of CREATE vs CREATE OR ALTER. I wish there was an ignore option like "Ignore CREATE\ALTER\CREATE OR ALTER." [image] / comments
A year later and I'm running into this same issue but now with SQL Compare. I have a sql repo reconciliation report that uses SQL Compare to show all objects with sql discrepancies between the rep...
Hi David - our original system used the "IF EXISTS....DROP" construct for preexisting objects. After upgrading to SQL16 with querystore we switched to CREATE OR ALTER to keep forced execution plans when possible. If the resulting sql compare script substituted ALTER then it should accomplish the same thing. / comments
Hi David - our original system used the "IF EXISTS....DROP" construct for preexisting objects. After upgrading to SQL16 with querystore we switched to CREATE OR ALTER to keep forced execution plan...