50 results found
-
Deploy to multiple databases concurrently
I want to be able to release database changes across several databases. Once confident that the targets are all ready to go, and that the deployment script is correct, I want the deployment to be concurrent (so that it takes less time).
12 votesWhile we haven’t implemented this exact feature, I want to share some information with similar patterns which may help some readers, or inspire comments or feedback in others.
One common approach is to manage multi-database deployments via an orchestrator, such as Azure DevOps, Octopus Deploy, or similar. This may be managed concurrently or in a simple loop depending on the needs. One example of this with Azure DevOps is demonstrated here: https://www.youtube.com/watch?v=-rZxLCRrgmI
When using a single release artifact to deploy to many databases, it’s important that you control for database drift on a regular basis outside of the deployment process. One way to do that is to set up monitoring that alerts you to schema changes that occur. An example of monitoring for this in SQL Monitor is in this custom metric: https://sqlmonitormetrics.red-gate.com/unauthorized-object-changes/
-
Include the name of the object that failed to deploy in SQL CI error messages
I want to know which object failed to deploy when a SQL Server error is thrown during validation.
6 votes -
Reduce Unnecessary Statements In Deployment Scripts
When deploying database changes (we are using the plugin for Octopus Deploy), it would be useful if there were not so many superfluous statements included in the deployment script. This is particularly prevalent when deploying static data, it appears that the deployment script will drop constraints on a table where it is updating table whether the constraints are material to the update or not. The code seems to be going down the path of least resistance which makes for bloated and hard to read code whereas I would like it if the code were as lean as possible to allow…
0 votes -
Team City Plugin - Timeout Field
During the build portion of our pipeline, builds occasionally fail due to timeout while inserting static data. There is a work around where you open up the powershell scripts underneath DLM to specify the timeout, but it would be much more useful to have this as a field in the Team City plugin.
I'm sure other plugins could use this as well.
4 votes -
Incorporate new/improved SQL Compare differences views into DLM Automation Changes.html
The latest version of SQL Compare introduced improvements to the SQL View as well as a new Summary View, as detailed here: https://www.red-gate.com/hub/product-learning/sql-compare/sql-compare-summary-view
It would be good if the Changes.html file generated by DLM Automation could also display the results in the same format so that it is easier and clearer to see the changes that are being deployed.
It would also be better if changes to static data were broken down so that for each static data table modified it explicitly states which records have been added/removed/modified/remain identical.
6 votes -
Support publishing custom schema names to DLM Dashboard
Please make it possible to specify a custom schema name when publishing a build to DLM Dashboard. The current implementation only supports using the nuget package version which has restrictive formatting rules, so for example it does not work for apps which use a four-part version number.
9 votes -
Add database connection for database testing in VSTS extension
Currently if you use the VSTS extension you can't ask it to run Tests against a database connection. If you allowed this then it would provide more flexibility.
1 vote -
Add the option to skip delete operations
It would be good if you could skip delete operations when deploying database changes automatically. This means if we update our application code and database changes then old versions of the application code can continue to use the old database functionality.
2 votes -
Disable check constraints
When importing static data on a sync operation, I'd like the option to disable (and re-enable afterwards) check constraints.
At the moment the only option I have is to ignore them which means my CI database is not built correctly
3 votes -
As an build engineer I'd like to be able to override the package version number in the TeamCity plugin
We are currently using GitFlow for a small POC and have hit an issue as we are unable to use a NuGet safe version number for our package name without going through some hoops.
Adding support for an optional version number field in the SQL CI TeamCity plugin would be a nice addition and allow us to drive this from another variable.
5 votes
- Don't see your idea?