Comments
Sort by recent activity
Oof, that sounds fun. Good luck! / comments
Oof, that sounds fun. Good luck!
You are right, that is nuts. EITHER: One DLM Dash install per team and the team is responsible for maintaining it - but that relies on each individual team having a neat division of responsibilities and not needing to look after more than 50. OR: Set up an automated process to drift check before deployment. https://documentation.red-gate.com/sca3/automating-database-changes/automated-deployments/handling-schema-drift OR: Build your own thing with triggers: https://www.red-gate.com/simple-talk/sql/database-administration/database-deployment-the-bits-database-version-drift/ OR do several of those. But 13 instances of DLM Dash really is nuts if there are people who will need to look at many different instances. / comments
You are right, that is nuts.EITHER: One DLM Dash install per team and the team is responsible for maintaining it - but that relies on each individual team having a neat division of responsibilities...
Hi Annette, Off the top of my head, try: $project = "C:\Work\scripts"
$targetDb = New-DatabaseConnection -ServerInstance "test01\sql2014" -Database "Test" $options = "ignoreadditional" Sync-DatabaseSchema -Source $project -Target $targetDb -SQLCompareOptions $options See example 6 here: https://documentation.red-gate.com/sca3/reference/powershell-cmdlets/sync-databaseschema And further docs here: https://documentation.red-gate.com/sca3/automating-database-changes/automated-deployments/using-sql-compare-options-with-sql-change-automation-powershell-module / comments
Hi Annette,Off the top of my head, try:$project = "C:\Work\scripts"
$targetDb = New-DatabaseConnection -ServerInstance "test01\sql2014" -Database "Test"$options = "ignoreadditional"Sync-DatabaseSch...
Not sure why that's not working, one for support I guess. In the meantime, reverting to the raw SQL Compare command line is my de facto quick fix where possible. / comments
Not sure why that's not working, one for support I guess.In the meantime, reverting to the raw SQL Compare command line is my de facto quick fix where possible.
The way it works behind the scenes is documented here: https://documentation.red-gate.com/soc6/reference-information/how-sql-source-control-works-behind-the-scenes If this was a fresh link to source control I normally see it come up as a conflict, since SQL Source Control does not know whether the source control or database version is the most up to date. / comments
The way it works behind the scenes is documented here:https://documentation.red-gate.com/soc6/reference-information/how-sql-source-control-works-behind-the-scenesIf this was a fresh link to source ...
You've already found the page to download old versions, but you are right - DLM Automation v2 doesn't seem to be there. If you want the latest version you should instead be looking for SQL Change Automation. It was renamed a few months ago. More info here: https://documentation.red-gate.com/display/SCA3/DLM+Automation+licenses+and+SQL+Change+Automation / comments
You've already found the page to download old versions, but you are right - DLM Automation v2 doesn't seem to be there.If you want the latest version you should instead be looking for SQL Change Au...
This is typically a much bigger problem than just buying a tool - it's how you use it. Yes, in some cases you need to write the scripts to deliberately work around some specific scenarios - this could either be handled using pre- and post-deploys or switching to a migration based source control solution, such as SQL Change Automation. (I mean by using the VS extension that was formerly called ReadyRoll INSTEAD of SQL Source Control. You will still use SQL Change Automation for deployment in either case. Redgate recently renamed stuff and now it's way harder to explain this.) Generally, however, downtime is caused because of dependencies between different systems that need to be upgraded at the same time and the system cannot run while some parts have been deployed and others have not. In that case you should look at the 'expand-contract' pattern and consider the wider reaching implications for the way your teams work together and co-ordinate your deployments. You may find these resources valuable: https://martinfowler.com/bliki/ParallelChange.html https://medium.com/continuousdelivery/expand-contract-pattern-and-continuous-delivery-of-databases-4cfa00c23d2e Apologies in advance - this isn't easy. / comments
This is typically a much bigger problem than just buying a tool - it's how you use it.Yes, in some cases you need to write the scripts to deliberately work around some specific scenarios - this cou...
I'll let the (current) Redgate folks respond to the support issue since I don't work there any more. / comments
I'll let the (current) Redgate folks respond to the support issue since I don't work there any more.
So how SoC* works out what should go into the commit vs the get latest tab is explained here: https://documentation.red-gate.com/soc6/reference-information/how-sql-source-control-works-behind-the-scenes (*Sorry, SSC means SqlServerCentral to most Redgate and ex-Redgate folks. SC is SQL Compare. SoC is SQL Source Control. No reason you would know that but it's a habbit that's hard for me to break!) Clearly in your case for some reason SoC has failed to work out whether the change was changed by someone else in source control and needs to be added to your database (Get Latest) or removed by you on the DB and a needs to be deleted in source control (Commit). That's why it shows up in the wrong tab. Removing it from your local repo manually should flush out the issue... I hope. Yes, you can use SQL Compare to diff the DB vs the files and deploy the DB version into the files. Then you would need to do the git add and commit manually as in my prior comment or through VS Code, rather than through SoC. / comments
So how SoC* works out what should go into the commit vs the get latest tab is explained here:https://documentation.red-gate.com/soc6/reference-information/how-sql-source-control-works-behind-the-sc...
Out of curiosity, does it erroneously show up in the Get Latest tab? You could try hand cranking it in raw git. Delete the stubborn file in the local git repo manually. Then, from the appropriate directory in the command prompt: > git status (to review your changes) Then: > git add . (Stages all manual file changes for commit. Alternatively you could specify specific changes.) > git commit -m "your message" (Commits the change locally) Then go back into SSMS/SQL Source Control and verify whether everything has sorted itself out. / comments
Out of curiosity, does it erroneously show up in the Get Latest tab?You could try hand cranking it in raw git.Delete the stubborn file in the local git repo manually.Then, from the appropriate dire...