Comments
Sort by recent activity
Might be worth thinking about using tSQLt to create some basic unit tests. Or, if accidental drops are a regular issue for you, you could automated a test on your build server to throw a warning whenever an object is dropped. There are a few ways to achieve that. / comments
Might be worth thinking about using tSQLt to create some basic unit tests.Or, if accidental drops are a regular issue for you, you could automated a test on your build server to throw a warning whe...
What underlying source control system are you using with Redgate? Git? TFVC? SVN? Might be easier to use the underlying source control tool. / comments
What underlying source control system are you using with Redgate? Git? TFVC? SVN?Might be easier to use the underlying source control tool.
This is not possible with SQL Compare. However, what is possible is to ignore the table in SQL Source Control/SQL Change Automation and use post-deploy scripts to manage this column. If you do this, source control would be "the truth" and any changes made in production would be ignored. Without understanding your use case in a bit more detail it's hard to know whether this would be an acceptable solution for you. / comments
This is not possible with SQL Compare.However, what is possible is to ignore the table in SQL Source Control/SQL Change Automation and use post-deploy scripts to manage this column.If you do this, ...
That's correct. You would need to ensure everyone understands that changes to triggers on filtered out tables need to use the post deploy script instead. If you extract the trigger creation into a sproc, and then call the sproc from the poat-deploy, changes will be spotted by SoC, but you would still need to remember to update the poat-deploy. Alternatively, you could have a DEPLOY_ALL_TRIGGERS sproc that loops through all the DEPLOY_TRIGGER_1, DEPLOY_TRIGGER_2, etc scripts based on some naming convention. That way all you need to put in your poat-deploy is: EXEC DEPLOY_ALL_TRIGGERS And you shouldn't ever need to update it again. Of course, folks will still need to remember that the triggers are handled with the associated sprocs. An alternative approach would be to add some tests to your build/deploy pipelines to ensure that all the appropriately named deploy_trigger sprocs are referenced by the coordinating script and vice versa. / comments
That's correct.You would need to ensure everyone understands that changes to triggers on filtered out tables need to use the post deploy script instead.If you extract the trigger creation into a sp...
Wow, not sure why post-deploy auto corrected to poat-deploy? / comments
Wow, not sure why post-deploy auto corrected to poat-deploy?
I would use a post-deploy script for this that does a: CREATE OR ALTER TRIGGER <TRIGGER_NAME> ON TABLE <TABLE_NAME> etc (Note, OR ALTER is only supported from SQL 2016 up.) If I have a lot of these I would extract them into a helper script or sproc so that the post-deploy script can simply reference the helper script/sproc to update all the triggers. / comments
I would use a post-deploy script for this that does a:CREATE OR ALTER TRIGGER <TRIGGER_NAME>ON TABLE <TABLE_NAME>etc(Note, OR ALTER is only supported from SQL 2016 up.)If I have a lot of these I wo...
Alternatively, if you are only after the PowerShell cmdlets... Install-Module sqlchangeautomation / comments
Alternatively, if you are only after the PowerShell cmdlets...Install-Module sqlchangeautomation
Do you have the full Toolbelt or just "essentials"? You need the full Toolbelt. / comments
Do you have the full Toolbelt or just "essentials"? You need the full Toolbelt.
Could you explain what you want to do in a little more detail? I'm not sure I understand. SCA is part of the SQL Toolbelt installer, which you can download for from the Rg website. It has a 14-28 day trial. (I forget which.) / comments
Could you explain what you want to do in a little more detail? I'm not sure I understand.SCA is part of the SQL Toolbelt installer, which you can download for from the Rg website. It has a 14-28 da...
Try disabling the option to force column order: https://documentation.red-gate.com/soc/configuring/change-the-comparison-options / comments
Try disabling the option to force column order:https://documentation.red-gate.com/soc/configuring/change-the-comparison-options