49 results found
-
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 -
Add Multisubnet failover support to Azure Devops pipeline plugin
When deploying to HA environments with servers in multiple subnets, you get an error if the sqlcmd runs on the wrong one. Per support the functionality was added to the powershell but was not exposed to the plugin.
4 votes -
Change behaviur for $(DefaultDataPath) or add new SQLCMD variable that reflects the location of the primary ile group
The default script options for creating additional files and filegroups relies on the $(DefaultDataPath) variable. This value is given by the server.
But: if you are using SQL Clone, using this value, you get orphaned files when the clone is either dropped or reset.
If you place the files within the vhd of the clone however, reset and dropping the clone works as expected.
4 votes -
Svn integration for SSMS SQL Change automation
Could you please add svn integration to Change Automation SSMS plugin.
4 votes -
Add support for command line switches to the TeamCity plugin
The current TeamCity SQL Change Automation Sync plugin supports SQL Compare and SQL Data Compare options, which is great. What it does not support are SQL Compare and SQL Data Compare command line switches such as /exclude:table<tablename> or any of these switches listed in this documentation https://documentation.red-gate.com/sc/using-the-command-line/switches-used-in-the-command-line
So, if I have a requirement to exclude certain objects for certain environments then my only option currently is to run the actual commandline.exe instead of the using the plugin.
Please add two new fields to the TemCity plugin so I can enter the command line switches for my SQL Compare and SQL…
3 votes -
Add an option to filters.scpf to ignore filestream properties
In our development databases we never set the filestream property on any column.
On some production servers, our DBA turns filestream on for specific customers that store large blobs.
When we deploy a new version the filestream property gets removed.It would be great if an option could be added to the .scpf filters format to ignore the filestream property.
Currently we need to exclude tables that have columns with potential filestream properties as a workaround.
3 votes -
Way to Subscribe to Updates/Release Notes for SCA PowerShell & Other Products
Given the latest release of SCA contains breaking changes due to Microsoft.Data.SqlClient version updates, it would be nice to have an RSS feed for updates to RedGate products, particularly those used in CI/CD pipelines like SQL Change Automation PowerShell commandlets.
This isn't possible to do through PowerShell gallery (e.g. https://www.powershellgallery.com/packages/SqlChangeAutomation/4.5.22279.31986) and changes are buried away in the Package Details section, nor through the release notes on RedGate's site (e.g. https://documentation.red-gate.com/sca/release-notes-and-other-versions/powershell-module-release-notes/sql-change-automation-powershell-4-5-release-notes). Some sort of heads up about changes would be nice rather than just finding broken pipelines.
3 votes -
Consider using shorter names for localdb name
The name for localdb appears to be sqlchangeautomation_ + a guid. I'm using Azure Devops deployment using sql change automation, when I use an agent name that is longer than 4 characters and use localdb in the build, I get an error message that states there is a path error. The generated localdb name is in the pattern sqlchangeautomation_ + a guid. This causes by builds to fail because part of the path is longer than 256 characters when the product is putting the necessary object into the user temp directory. if the pattern for generating…
3 votes -
Please re-add the condition feature in the migration script in the packaged script
SQL Change Automation idea: Please re-add the condition feature in the migration script in the packaged script since this was working before in ReadyRoll.
More details in https://productsupport.red-gate.com/hc/en-us/requests/133672?page=1
3 votes -
New powershell cmdlet: Export-DatabaseDocumentation
I would like the option of creating my documentation outside of a database artifact. I would rather it not be embedded in a nuget or zip file with the deployment files. Currently the object created by New-DatabaseDocumentation can only be passed to New-DatabaseBuildArtifact. It would be great to just pass it to a new export cmdlet so it can be saved to disk.
3 votes -
Allow artifact names to be modified in OctopusDeploy step template via new parameter
In the "RedGate - Create Database Release" step template for OctopusDeploy, the powershell script contains logic for uploading Change.html, Warning.xml and Update.sql files (among others) as artifacts on the current Release. The only text added to the resulting artifact file name besides these keywords is the name of the database. In our environment, every single release produces each of the above artifacts, and if you view a Release that has been promoted through multiple environments the Artifact listing just shows the exact same artifact names repeated over and over with no indication of the environment in which they were produced.…
3 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 -
Support Deployments to Azure SQL Data Warehouse
Allow a change script to run on Azure SQL Data Warehouse
3 votes
Kendra
responded
Thanks for this suggestion.
In the year since your request, Redgate has acquired Flyway. Flyway is an automated deployment tool, and while it doesn’t offer help in authoring scripts or a full continuous integration process, it can help you automate deployments to Azure SQL Data Warehouse (now known as Azure Synapse).
More information on flyway is here: https://flywaydb.org/documentation/database/azuresynapse
Since this doesn’t offer the same level of full CI/CD support as in SQL Change Automation, I am keeping this request open for further comments and feedback.
-
Support Nuget references in Sql Projects
Allow project/assembly references to be nugets.
This would allow better project/build separation and/or less staging work.
2 votes -
SQL Clone: Add a 2nd extended property to the clone databases with the image name
Currently when deploying clones from SQL Clone images, the database level extended property IsSQLCloneDatabase gets set to 1. It would be helpful to be able to see the image name the clone is created from.
This would allow for handling "sliding window" scenarios in terms of phasing out out-of-date images when you have a weekly image created in a graceful/programmatic way).
2 votes -
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 -
Create a branch based on one of the available annotated tags
Our Create a hot fix procedure is:
- Create and get a bug fix into master using the procedures for making changes
- Create a local hot fix branch from current/test or current/production annotated tag
- Cherry pick bug fix commit(s) from master to the local hot fix branch
- Run a full build, all automated tests, and all migrations
- Push the local hot fix branch to the remote repository
- Build & release pipelines are triggered
This procedure will help prevent regressions due to developers forgetting to merge hot fixes to master.
This feature request relates to step 2. The CI/CD release pipeline will…
1 vote -
add generate migrations automation commands/options in SCA VS plugin
when working on a VS project that includes a SCA project it would be useful to allow the developer to "automate" the capturing of changes in their development database (e.g. connection string that is defined in the sqlproj.user file) through some form of automation either as:
- part of a local build step (for example where a EF Core project has created and applied database a migration to a development database) that automatically generates and adds the new migration script to the SCA project; or
- is triggered as part of a git pre-check-in command (e.g. SCA PowerShell?)It would…
1 vote -
Handle system named column default constraints when importing and generating scripts
When maintaining a database, like to assign names to unnamed default constraints. However, generated script only works if the target database has identically named "unamed" default constraints.
To add robustness to the script, I modify these to a short snippet that works on the schema+table+column. (Using a snippet in SQL Prompt to speed the process :)
But why do I need to do this - after all it is replacing machine generated code?
Here is the SQL Prompt snippet I use:1 vote -
Add SQL Change Automation Core option as an add-on for SQL Toolbelt Essentials
Since there is no add-in for SQL Source Control for Visual Studio, there is no mechanism for effectively versioning changes inside Visual Studio.
The SQL Change Automation Core (only currently available as part of VS 2017 Enterprise) provided a mechanism for maintain changes scripts that are fully integrated into VS Project (and therefore can be placed under source control as a part of the project).
This combination is Developer focused (rather than dev-ops focus of full SQL Change Automation)
1 vote
- Don't see your idea?