Comments
Sort by recent activity
Cool, is this for reporting? If so I recommend you check out the /report switch: https://documentation.red-gate.com/sc13/using-the-command-line/switches-used-in-the-command-line?_ga=2.261896781.1791667307.1566837276-1706698906.1534783619#Switchesusedinthecommandline-/Report:%3Cfilepath%3E If this is to set up some sort of automated deployment, remember to use the /synchronise switch: https://documentation.red-gate.com/sc13/using-the-command-line/switches-used-in-the-command-line?_ga=2.261896781.1791667307.1566837276-1706698906.1534783619#Switchesusedinthecommandline-/Synchronize However, it sounds like what you want to do is track which changes are made and maybe which changes are associated with the development of this or that feature. If that's the case, I strongly recommend you consider looking at Redgate SQL Source Control and basing your change management and deployment processes off source control. This will make it much easier for you to track this stuff and deploy with confidence: https://www.red-gate.com/products/sql-development/sql-source-control/ / comments
Cool, is this for reporting? If so I recommend you check out the /report switch:https://documentation.red-gate.com/sc13/using-the-command-line/switches-used-in-the-command-line?_ga=2.261896781.1791...
My humble apologies. I misread the question and sent you the SQL Compare (schema comparing) command line docs rather than the SQL Data Compare (data comparison). https://documentation.red-gate.com/sdc13/using-the-command-line/command-line-syntax There are some simple examples here: https://documentation.red-gate.com/sdc13/using-the-command-line/examples-using-the-command-line/simple-examples-using-the-command-line It might be because you are cd'ing to the SQL Compare directory but then calling SQL Data Compare (which lives in a different directory). Try adding the path to SQL Compare / Data Compare to your PATH environment vartiable. That should negate the need for all the CD stuff. Also, have you tried the syntax: sqldatacompare /project:"C:\Users\UserName\Desktop\Project.sdc" >> "D:\Results\log.txt" Beyond that, it would help if you could share the error message. / comments
My humble apologies. I misread the question and sent you the SQL Compare (schema comparing) command line docs rather than the SQL Data Compare (data comparison).https://documentation.red-gate.com/s...
You'll want to use the SQL Compare command line. There's a getting started page here: https://documentation.red-gate.com/sc13/using-the-command-line/command-line-basics There are some simple examples here: https://documentation.red-gate.com/sc13/using-the-command-line/simple-examples-using-the-command-line And full documentation of all the command line switches is here: https://documentation.red-gate.com/sc13/using-the-command-line/switches-used-in-the-command-line Once you've figured out the command you need, you should be able to schedule that using your automation tool of choice. If you don't have one, sticking that command into a batch file and running it from Windows Scheduler would do what you ask. But I'd love to know exactly what are you trying to achieve? Depending on the answer you may be better off looking at SQL Change Automation. / comments
You'll want to use the SQL Compare command line. There's a getting started page here:https://documentation.red-gate.com/sc13/using-the-command-line/command-line-basicsThere are some simple examples...
Actually, I've just solved my own problem. I'm embarrassed to admit that it was user error. I forgot that we'd restructured the directory tree in the git repo. I had forgotton to unlink and relink the repo with the new path to the source control directory. So if anyone else sees this behaviour, check the path you are linking to is correct. That said, the error message was a little misleading. It sent me down a rabbit hole checking my git config. An error message stating that the path specified doesn't exist would have more helpful. Keep up the good work folks! / comments
Actually, I've just solved my own problem. I'm embarrassed to admit that it was user error.I forgot that we'd restructured the directory tree in the git repo. I had forgotton to unlink and relink t...
OK - I assume it's fine. Axel has already tweeted and blogged about it: https://flywaydb.org/blog/next-chapter / comments
OK - I assume it's fine. Axel has already tweeted and blogged about it:https://flywaydb.org/blog/next-chapter
This is a pretty big deal. Can we talk/tweet about this publicly? I assume yes, since the press release looks like it's already gone out, but I just wanted to check here that it's OK with you guys before I go and draw attention to something that you weren't planning to shout about yet. / comments
This is a pretty big deal. Can we talk/tweet about this publicly?I assume yes, since the press release looks like it's already gone out, but I just wanted to check here that it's OK with you guys b...
Readyroll is now called SQL Change Automation too. / comments
Readyroll is now called SQL Change Automation too.
SCA projects have a couple of concepts which support this: - Programmable objects: https://documentation.red-gate.com/sca3/developing-databases-using-sql-change-automation/generating-scripts-to-capture-database-changes/programmable-objects - Offline schema model: https://documentation.red-gate.com/sca3/developing-databases-using-sql-change-automation/generating-scripts-to-capture-database-changes/offline-schema-model As far as I know these features aren't going anywhere - but deployment of tables and data is via the migration scripts. The offline schema model is basically a reference point, handy for spotting conflicts, but it is not used for deployment. If you would like to stick with with a purely state-based deployment process, use SQL Source Control for script management/source control, and the SCA powershel cmdlets for deployment. In this scenario SCA basically does a fancy SQL Compare job, through a PowerShell interface, with various handy features like drift detection and pretty deployment reports to support script review and static code analysis. / comments
SCA projects have a couple of concepts which support this:- Programmable objects:https://documentation.red-gate.com/sca3/developing-databases-using-sql-change-automation/generating-scripts-to-captu...
It's horrible. That's one of the reasons to move to the dedicated model. If you are all working on the same dev database but trying to do different things that won't end well. What most people do is set up a separate shared database for their other branch... But this leads to long lived branches, which is bad. Sorry if it's not the answer you wanted, but ultimately the shared model really doesn't work well when branching. If you want frequent branching I highly recommend you move to the dedicated model. Why do you want/need to use the shared model? / comments
It's horrible. That's one of the reasons to move to the dedicated model. If you are all working on the same dev database but trying to do different things that won't end well.What most people do is...
Thanks for the prompt response. May I politely request that you stop designing tools to be deliberately annoying. Thank you. / comments
Thanks for the prompt response.May I politely request that you stop designing tools to be deliberately annoying.Thank you.