Comments
Sort by recent activity
Does your git repo already have a remote configured? Assuming you followed this process - the push button should appear: 1. Create your remote repo 2. Clone remote repo locally 3. Link to local repo 4. Make some commits Now you should have a push button. However, if you have just done the following: 1. Created a local repo without a remote 2. Linked to S~QL Source Control 3. Made some commits In this scenario you will not see a push buttong because SQL Source Control does not know any information about your remote repo. Bottom line - you need to set up your remote repo outside of SQL Source Control. Once this is set up, SQL Source Control will be able to push to it. A test: Can you run the following from the command prompt?: C:/your/repo> git push If you can, and you have some commits locally that have not yet been pushed to the remote, SQL Source Control should display a push button in the "Commit" tab. However, if that command does not work, you should not expect SQL Source Control to work either. / comments
Does your git repo already have a remote configured?Assuming you followed this process - the push button should appear:1. Create your remote repo2. Clone remote repo locally3. Link to local repo4. ...
You probably can't do this using a SQL Compare project, but if you used the /Scripts1 switch instead this should probably work. So a few questions: 1. What is the use case? 2. Why do you want to use the project file instead of just pointing directly at the source code. 3. Why are the developer's tests not in source control? / comments
You probably can't do this using a SQL Compare project, but if you used the /Scripts1 switch instead this should probably work.So a few questions:1. What is the use case?2. Why do you want to use t...
In settings, there's an "under the hood" section. It should have the references to all your transient and working base repos. For more info on these: https://documentation.red-gate.com/soc/reference-information/how-sql-source-control-works-behind-the-scenes Assuming your developer does not have any work they are afraid to lose, have you tried making a note of the working base/transient locations, unlinking everything, deleting all working base / transients, and re-linking? / comments
In settings, there's an "under the hood" section. It should have the references to all your transient and working base repos. For more info on these:https://documentation.red-gate.com/soc/reference...
This would be awesome. :-) +1 / comments
This would be awesome. :-)+1
Am I reading it correctly, it literally only says: <div>SQL Data Compare Command Line for DLM Automation V13.8.0.12547
</div><div>==============================================================================</div><div>
Copyright Copyright c Red Gate Software Ltd 2019</div><div><br></div><div>
DLM Automation: in trial, expires 2019/09/26 05:17:58 +05:30</div><div>
Automation License: in trial, expires 2019/09/26 05:17:58 +05:30</div><div>
Registering databases</div>
That doesn't look right to me. I would have expected either some feedback about the results, or some error message. Unless the process was exited before it had finished? I've emailed the official Redgate support team and asked them to have a look at this thread. / comments
Am I reading it correctly, it literally only says:<div>SQL Data Compare Command Line for DLM Automation V13.8.0.12547
</div><div>===================================================================...
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...
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...