Comments
Sort by recent activity
Yep, I think that's how it works. /sourcecontrol is read inly but/scripts updates the files. But @Alex B can verify. Glad you got it working! / comments
Yep, I think that's how it works. /sourcecontrol is read inly but/scripts updates the files. But @Alex B can verify.Glad you got it working!
That's fair enough. Often "it depends". :-) Good luck with your implementation! / comments
That's fair enough. Often "it depends". :-)Good luck with your implementation!
In this scenario I would expect the files to be created on the filesystem, but not yet added to Git. Just to clarify, is it the case that: 1. The file exists on disk, but is not visible in Git (expected). 2. The file does not exist on disk or in Git (curious). Assuming scenario 1, open a command prompt and navigate to your git repo and run: > git status (It should show you have an untracked file.) Now run: > git add . (This will stage all changes ready to commit. If you wanted to cherry pick specific changes replace the . with the file names.) Finally: > git commit -m "your commit message here" Now the commit should show up in Git. (If you wanted to automate this task, following your schema compare, of course you could.) / comments
In this scenario I would expect the files to be created on the filesystem, but not yet added to Git.Just to clarify, is it the case that: 1. The file exists on disk, but is not visible in Git (expe...
@jschwarz_continuus: I'm afraid SQL Source Control does not have a PS/cli interface, but Git does. You could do what you want by running the SQL Compare command first, and then running a few git commands. However, it's not normally desirable to automate source control commits. Typically in a CI process, a developer will write their code, commit it carefully, and then the automated processes recognise the commit/push and run various builds, tests and deploys etc. / comments
@jschwarz_continuus: I'm afraid SQL Source Control does not have a PS/cli interface, but Git does. You could do what you want by running the SQL Compare command first, and then running a few git co...
It will just update the files. It won't do the commit. Also, SQL Source Control does a lot of clever stuff behind the scenes that SQL Compare won't do for you: https://documentation.red-gate.com/soc7/reference-information/how-sql-source-control-works-behind-the-scenes / comments
It will just update the files. It won't do the commit.Also, SQL Source Control does a lot of clever stuff behind the scenes that SQL Compare won't do for you:https://documentation.red-gate.com/soc7...
Sorry - I neglected to follow replies to this thread and just spotted your responses. Glad you got it figured out. Good luck! / comments
Sorry - I neglected to follow replies to this thread and just spotted your responses. Glad you got it figured out. Good luck!
This is a git question rather than a SQL Source Control question. I've never done it before, but imagine starting somewhere like this would be your best bet: https://gbayer.com/development/moving-files-from-one-git-repository-to-another-preserving-history/ / comments
This is a git question rather than a SQL Source Control question.I've never done it before, but imagine starting somewhere like this would be your best bet:https://gbayer.com/development/moving-fil...
SQL Source Control does not do this out of the box. Neither do other state based source control tools. SQL Change Automation (and other migration based tools) give you this as a side-effect of the deployment process, not solely for auditing purposes. Most people manage what version is deployed where in a separate tool. Something like Jenkins, Octopus Deploy or Azure DevOps Services. This is consistent with, for example, the way most people manage their application releases. It's unusual to update the application in some way just so you can see what's deployed. If you were desperate to achieve this in the database, you could add a post deploy script to your deployment process to (for example) squirt the upgrade script, a timestamp and the Octopus release number into an auditing table. This would provide similar functionality to what you get with an SCA project. Or you could use DLM Dashboard. 😉 / comments
SQL Source Control does not do this out of the box. Neither do other state based source control tools. SQL Change Automation (and other migration based tools) give you this as a side-effect of the ...
Makes sense. But you should get a CI server in place. ;-P / comments
Makes sense.But you should get a CI server in place. ;-P