Comments
Sort by recent activity
(But you cannot trigger emails directly from SQL Compare.) / comments
(But you cannot trigger emails directly from SQL Compare.)
I recommend using something like Octopus Deploy to orchestrate your deployments. You can add steps to call Redgate to generate diff reports/upgrade scripts, trigger emails pre/post deployment, carry out a manual review of diff reports, and execute scripts as required.
Octopus Deploy: https://octopus.com/
Integrating Octopus and Redgate DLM Automation (a PowerShell interface for SQL Compare and other RG tools): https://documentation.red-gate.com/display/DLMA2/Octopus+Deploy+step+templates+reference / comments
I recommend using something like Octopus Deploy to orchestrate your deployments. You can add steps to call Redgate to generate diff reports/upgrade scripts, trigger emails pre/post deployment, carr...
Assuming you are using shared model and that you are looking at the objects listed in the commit tab. If that assumption is incorrect please disregard the rest of this answer an clarify.
Short answer: No. This list is calculated by comparing dev database to source control and the info about who committed what is pulled from he default trace.
Longer answer: You could set up an automated SQL Compare job using SQL Compare command line to create a report of the differences between source control and dev database, but this will not have info about who made what changes unless you also cross-reference with default trace, which sounds hard.
My recommendation: Switch to the dedicated model. Then this problem probably mostly goes away. / comments
Assuming you are using shared model and that you are looking at the objects listed in the commit tab. If that assumption is incorrect please disregard the rest of this answer an clarify.
Short answ...
No worries, glad to help.
And I'd be interested to know why the dedicated model is impossible with your existing constraints. I've not yet found any technical constraints that cannot be resolved and I'm pretty sure it is impossible to be agile with a shared database and more than 3 developers.
Alex / comments
No worries, glad to help.
And I'd be interested to know why the dedicated model is impossible with your existing constraints. I've not yet found any technical constraints that cannot be resolved an...
In my experience DevOps is an enabler, not a hoop to jump through. If people are seeing it as hoops they have the wrong idea. The purpose of DevOps is to enable them to respond quickly. Part of DevOps is the freedom to branch, fix, merge, build, test and deploy, in a mostly automated fashion, in minutes. The hoop is simply that theyneed to learn to use modern technologies. And if you start a career in IT and you don't see staying up to date with modern technologies as pert of your job you were mis-sold.
Regarding the users adopting and getting trained up in Git: While Git is undoubtedly the obvious VCS in 2017, it is possible to adopt DevOps using a different VCS. These users, are they developers? If so they need to wake up to the fact that version control is non-negotiable in modern software development - regardless of the software language they use. / comments
In my experience DevOps is an enabler, not a hoop to jump through. If people are seeing it as hoops they have the wrong idea. The purpose of DevOps is to enable them to respond quickly. Part of Dev...
You are right. It sounds like those docs were aimed at TFS/SVN style source control systems which manage branching differently.
If using Git you can switch branch using Source Tree or raw git commands etc as you like. Then, on the database you'll want to go to the Get Latest tab, select any changes and click "Apply changes". (I'm assuming you linked using the "Git" option. If you linked using the "Working Folder" or custom hook file option the process is the same accept the button is called "Get Latest", not "Apply changes".)
Altternatively, you could provision a new database for the other branch. Some people prefer to do it this way because making wholesale changes to a database if the branches are very different can be ... fun. Especially if there are lots of table refactors/migration scripts involved.
I hope you are using the dedicated model. Doing this in the shared model sounds like a nightmare from a provisioning/team workflow perspective. / comments
You are right. It sounds like those docs were aimed at TFS/SVN style source control systems which manage branching differently.
If using Git you can switch branch using Source Tree or raw git comma...
It is easier to learn new things than I thought. And it’s important that I keep doing it. / comments
It is easier to learn new things than I thought. And it’s important that I keep doing it.
Migration scripts are not optimised for your use case. Migration scripts are designed for occasional use, for example when you need to override the default behaviour. (e.g. to handle a column split which SQL Compre can't work out by itself). If you have lots of migration scripts you will hit peformance issues.
If you want to script out *every* change for deployment you should look at ReadyRoll instead. This is designed to serve your specific use case and will perform much better for you. / comments
Migration scripts are not optimised for your use case. Migration scripts are designed for occasional use, for example when you need to override the default behaviour. (e.g. to handle a column split...
SQL Data Compare command line documentation: https://documentation.red-gate.com/display/SDC12/Using+the+command+line / comments
SQL Data Compare command line documentation:https://documentation.red-gate.com/display/SDC12/Using+the+command+line
The build will run on a Bamboo build agent (not the server).
That agent must have a Windows OS and have DLM Automation installed. / comments
The build will run on a Bamboo build agent (not the server).
That agent must have a Windows OS and have DLM Automation installed.