Comments
Sort by recent activity
It's back up now. Thanks for your patience and for trying this, Alex. SQL Source Control v6.3 - https://documentation.red-gate.com/soc6/release-notes-and-other-versions/sql-source-control-6-3-release-notes. Remember to configure Frequent Updates in SQL Source Control > Help and then Check for Updates in SQL Source Control > Help. / comments
It's back up now. Thanks for your patience and for trying this, Alex.SQL Source Control v6.3 - https://documentation.red-gate.com/soc6/release-notes-and-other-versions/sql-source-control-6-3-relea...
SQL Change Automation integrates with existing build and release systems. It's not a replacement for them and it is not a version control system. So, SQL Change Automation may not help with this. I'll send you a message and maybe we could have a quick call so I can understand what you're doing better. Thanks! / comments
SQL Change Automation integrates with existing build and release systems. It's not a replacement for them and it is not a version control system. So, SQL Change Automation may not help with this....
There's a webinar about Database DevOps using ReadyRoll and the new VSTS extension (which also works with TFS) for CI/CD tomorrow Tues Nov 28th at noon ET - https://attendee.gotowebinar.com/register/817288270091583491?source=FORG. / comments
There's a webinar about Database DevOps using ReadyRoll and the new VSTS extension (which also works with TFS) for CI/CD tomorrow Tues Nov 28th at noon ET - https://attendee.gotowebinar.com/registe...
I had a similar issue.
It was looking for sqlCI.exe in C:Program Files (x86)Red Gate. I had to copy and paste this folder from C:Program Files (x86)Red GateSQL Automation Pack 1, which seemed to work. Maybe there's a better way to solve this? / comments
I had a similar issue.
It was looking for sqlCI.exe in C:Program Files (x86)Red Gate. I had to copy and paste this folder from C:Program Files (x86)Red GateSQL Automation Pack 1, which seemed to w...
Hi Joseph,
We should have a command line that will do what you need within the next week or 2. This will pick up migration scripts and also do a SQL Compare of the source and target to either generate a deployment script or synch the target directly. Just like SQL Compare will do.
It's separate for now while we integrate Migrations v2 into the SQL Compare GUI. Once this integration is done, then we'll have a release of SQL Compare with the updated command line to pick up the new migrations.
So, you can use this alternative command line to do automated deployments (esp. in CI environments) until SQL Compare is ready. It will have the same licensing requirements as SQL Compare.
I hope this helps! We'd love to hear how you get on with the SQL Source Control Early Access Release and this migration command line tool. / comments
Hi Joseph,
We should have a command line that will do what you need within the next week or 2. This will pick up migration scripts and also do a SQL Compare of the source and target to either gene...
Hi Joseph,
Thanks for clarifying. In Migrations v2, a migration script doesn't have to be tied to DDL changes. So, you can just write your UPDATE script as a migration script and this will be picked up like all the other migrations. To do this, use the "Add migration script..." button on the Migrations tab. / comments
Hi Joseph,
Thanks for clarifying. In Migrations v2, a migration script doesn't have to be tied to DDL changes. So, you can just write your UPDATE script as a migration script and this will be pic...
Hi Joseph,
The early access release of SQL Source Control with Migrations v2 is now available. You can read more about this and download it from http://documentation.red-gate.com/displ ... ss+release.
We do not have a command line yet, but should have that shortly (within a week or 2). I will update this forum as soon as it's available. This will help with automated deployments and pick up Migration scripts. It will then go into SQL Compare and SQL Data Compare (GUI and command lines), but I don't have an estimate for this yet.
Regarding your requirements:
1) Migration scripts should work across the branches. Means, I need to deploy the database changes from Branch to database including migration scripts.
This should work. We no longer rely on repository location or revision number so that Migrations will work across branches.
2) I need to include custom scripts for the deployment, this also should work in branch architecture.
I don't understand how a custom script is different from a migration script that is used during deployment. Could you explain this more?
3) Both Migration scripts and Custom scripts need to deploy from one Branch to databases through the command line scripts
As mentioned above, we should have a command line shortly that will pick up Migration scripts to be used in automated deployments. I'm not sure about what you mean by Custom scripts. Migration scripts are custom scripts that are re-used by SQL Compare during deployment.
Cheers! / comments
Hi Joseph,
The early access release of SQL Source Control with Migrations v2 is now available. You can read more about this and download it from http://documentation.red-gate.com/displ ... ss+rele...
Hello.
You can modify the CommandLineHooks.xml to do nothing in the commit. This will just save the files to your working folder. You'll need to add them to the changelist and commit using your own tool.
You can also use the new link to "Working Folder" option. This option just scripts out the files and saves them to this folder from the commit tab. In SQL Source Control, the button on the commit tab is actually changed to say "Save." You would then use your own version control system's tool to add the files to the pending changelist and commit them.
Strange that the powershell is not exiting.
Cheers!
Stephanie Herr [image]
SQL Source Control Product Manager / comments
Hello.
You can modify the CommandLineHooks.xml to do nothing in the commit. This will just save the files to your working folder. You'll need to add them to the changelist and commit using your o...
This process can cause issues if a developer by accident checks in the development version of the synonym by accident if the checkmark is not deselected during the checkin process to SVN.
Have you tried using SQL Source Control's filter feature so that synonyms don't accidentally get checked into SVN? Right click on the db in the Object Explorer and then select Other SQL Source Control tasks > Edit filter rules... Then, uncheck synonyms on the left and save and close. Now, the synonyms should not show up on the commit list anymore so developers don't have to remember to deselect them every time they commit.
Make sure you commit the filter configuration so other developers stop seeing the synonyms on their commit lists too.
I hope this helps! / comments
This process can cause issues if a developer by accident checks in the development version of the synonym by accident if the checkmark is not deselected during the checkin process to SVN.
Have...