36 results found
-
Ability to run build and package steps separately
It would be good to be able to just run the build phase of sql CI, without running the package step, and then run the package step subsequently.
Granted, the reason that this would be useful is so that we can modify the scripts used to build the CI database (via a custom script that does variable replacements based on OctopusDeploy project variables), but then we want to revert to the original files to package.
So, potentially, http://redgate.uservoice.com/forums/263916-sql-ci/suggestions/7647198-as-an-deployment-engineer-i-d-like-to-run-environm is a fix for this.
Another way of solving this (that would be more work) is to integrate better with OctopusDeploy for…
8 votesDLMA v2 now features powershell cmdlets that are more modular than the previous SQLCI.exe and separate verification, testing, and packaging.
-
Ability to force error code to zero for failed unit tests
When running SQL CI in Bamboo if any unit tests fail, SQLCI.exe returns non-zero which is interpreted as a failure code by Bamboo. This means that the next step which is to parse the unit test results won't run, and you wont' know what test failed.
Can we have a way of forcing a zero return code for failed unit tests?6 votesAs described in comments, this is now possible with the Powershell cmdlets. Please get in touch if you need this facility in the Bamboo addon.
-
Be able to generate script for azure and non azure
I could be great to be able to generate both the script for azure and non azure at the same time.
A scenario where I need it: I have 3 environments: one non azure and 2 azure and I need to deploy on it by using the octopus.2 votesThis is now possible using SQL Change Automation projects, which support development and deployment to Azure SQL Database.
Migration scripts allow you to use conditional logic and to detect the type of target you are deploying to, which should support this scenario.
-
As a developer I would like to be able to deploy to a database using integrated security.
We use a service account to deploy changes. I would like to be able to use integrated security of the tentacle service account.
3 votesMarking as completed since SQL Release already supports this. However if the original poster of this comment meant something other than what Peter has described then please do let us know.
-
A better ability for a DBA signoff.
A better ability for a DBA signoff. That the changes are ok.
Ex Automated A HTML mail with a link to the update script and the changes report for the DBA team to review.
A GO/ NO GO button to continue or halt the deployment.6 votesThe Octopus Deploy integrations should be able to allow Octopus Deploy to provide this facility for you.
-
Support for databases using replication
I should be able to use SQL Release to deploy to a replicated database.
20 votesSQL Change Automation projects now allow:
- Creating granular scripts for deployment
- Customizing isolation levels
SQL Change Automation does not generate scripts to add and drop articles, but it does support having this code added into migration scripts.
There is certainly more which could be added feature-wise to support replicated database, but at this is an older request for basic deployment support, I am going to close this as completed.
I very much welcome new suggestions with current use cases related to SQL Change Automation.
-
Support for deploying static data
I should be able to deploy static data using SQL Release.
10 votesAvailable in SQL Release version 1.0.5
SQL Release will now apply changes in static data when creating an update from a package or scripts folder.
Download the new version by visiting http://www.red-gate.com/products/dlm/sql-release/
Please see the following page for more details. http://www.red-gate.com/sqlreleasestaticdata -
Better integration with Octopus Deploy
I should be able to download an Octopus Deploy step template which will provide richer GUI for common use cases of SQL Release.
6 votesWe are pleased to announce we have released four step templates for Octopus Deploy to support some common use cases for SQL Release. You can find them here http://library.octopusdeploy.com/#!/listing/redgate
Fiona (Project Manager Redgate DLM Automation) -
Ability to perform the pre-deployment check separately from the deployment
New-DatabaseUpdate command makes a database update which can take a database from version X to version Y. When you use SQL Release to deploy this database update to a target database, it does a pre-schema check.
Between making of the database update and applying it, the database could have drifted from version X. The check ensures that the target database is actually in version X.
This feature will give you an ability to run the pre-schema check separately from deploying of the update.
6 votesThanks for this suggestion.
This suggestion can now be handled with the ‘Drift’ features in SQL Change Automation 4. It is possible to, just prior to deploying a release artifact, quickly re-rerun the generation of a release artifact simply for the purposes of checking for any new drift, and canceling the deployment if any new drift has occurred.
More info is here: https://documentation.red-gate.com/sca4/reference/powershell-cmdlets/new-databasereleaseartifact
-
4 votes
Any release with a Redgate tool now appears in SQL Monitor’s timeline. Learn more at https://www.red-gate.com/hub/product-learning/sql-monitor/unearthing-bad-deployments-sql-monitor-redgates-database-devops-tools
-
Support comparison options
I should be able to fine tune my deployments by specifying comparison options when using SQL Release. An example of a comparison option would be the ability to ignore comments when comparing two databases to make a database update.
3 votesAvailable in SQL Release version 1.0.4
You can now change the SQL Compare options that are applied when generating update scripts and running pre-deploy and post-deploy schema checks.
Download the new version by visiting http://www.red-gate.com/products/dlm/sql-release/
Please see the following page for more details. http://documentation.red-gate.com/display/SR1/Using+SQL+Compare+options+in+SQL+Release -
Support different collations when validating (as part of build) and testing deployments
I want to use different collations when validating and testing my database.
1 voteSome changes which we have made to SQL Change Automation projects now give you flexibility that will allow this behavior.
SQL Change Automation projects now have a Provisioning folder with a CreateDatabase.sql script in it. Modifying this script will impact how the databases used for validation are created. You can therefore use this to validate against different collations if desired.
-
Support Azure connections when validating (as part of build) and testing deployments
SQL CI can synchronize with Azure databases, but they can’t be used as temporary databases during the build and test process. I want to use an Azure temporary database.
1 voteThanks for this suggestion.
Azure SQL Databases can now be used for building with SQL Change Automation.
In addition, Azure SQL Databases can also be used as the “shadow” databases for SQL Change Automation projects.
-
Allow tSQLt tests to be synchronized
I want to sync my tSQLt tests with my test environment.
1 voteIf you use the -SQLCompareOptions parameter you can apply additional options – see https://documentation.red-gate.com/display/DLMA2/Using+SQL+Compare+options+with+DLM+Automation+cmdlets for more details.
Note that some of the options (including ignoretSQLt) are selected by default. You can deselect the default options by adding a minus sign (-) as documented on the above page.
-
Support databases with full text indexes
I want to use SQL CI with database that contain full text indexes
1 voteIf you specify your own database server to use as a temporary database rather than defaulting to LocalDB, DLMA will support databases with full text indexes.
-
Allow users to turn off the defaults when validating (as part of build) and testing deployments
When creating the temporary database, SQL CI uses the SQL Compare option: /default (http://documentation.red-gate.com/display/SC10/Options+used+in+the+command+line). I want to turn off these options so I can include items like filegroups.
1 voteYou can now remove any default SQL Compare options by specifying them prefixed with a minus sign.
- Don't see your idea?