36 results found

1. SQLCompareOptions switch should support SQL Data Compare options.

   The SQLCompareOptions switch supports only commandline options from SQL Compare but not from SQL Data Compare that are used for static data compare.

   We need the option "Force binary collation" for detect case-sensitively changes on a case-insensitive collation.

   74 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   5 comments  ·  Delete…  ·  Admin →
   completed  ·  Maya Malakova responded

   As of SQL Change Automation Powershell 3.3.19177 you can now tweak static data comparison behaviour by providing SQL Data Compare options to the cmdlets.

2. Allow online index operations

   Allow online=on option for index creation during deployment process. This is a particular painful problem when deploying to an azure sql database where they have transaction log limits.

   42 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   completed  ·  AdminDavid Atkinson (Product Manager, Redgate) responded

   A schema comparison option now exists to support the ONLINE option. This option is set to OFF by default.

   https://documentation.red-gate.com/sca/developing-databases/concepts/advanced-concepts/comparison-and-script-generation-options

   
   False

3. Support Change Data Capture (CDC)

   You can deploy databases featuring CDC using SQL Server Express, but you need to filter out all objects referencing the CDC system table. I want SQL CI to support databases that use CDC.

   28 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Delete…  ·  Admin →
   completed  ·  Kendra responded

   Thanks for this suggestion.

   Change Data Capture is now supported quite well by SQL Change Automation projects which has plugins in both Visual Studio and SSMS. Configuring this does take some careful implementation as I’ll describe here.

   When setting up the project, I recommend setting the ‘comparison’ option for “Add object existence checks” to true. This can be done in the graphic project wizard in the SSMS plugin, and this means that any commands regarding the CDC schema, etc in your migration script will be written in an idempotent way that won’t cause errors. (Note: I didn’t see CDC system tables included in the baseline script, which is good.)

   It is also helpful to add a pre-deployment script to the project to ensure that cdc is enabled. This will enable project verification against a shadow database and build databases.

   If you wish to manage change tracking in your migration scripts, you can do this as well by adding in commands to do so in your migration scripts, like this:

   IF OBJECT_ID(‘cdc.dbo_NewTable_CT ’) IS NULL
   EXEC sys.sp_cdc_enable_table @source_schema = N’dbo’,
   @source_name = N’NewTable’,
   @role_name = NULL;
   GO

   If teams are also SQL Prompt users, then snippets of reusable code can make adding in these code blocks easier.

   I will follow up on this by adding some additional documentation to SQL Change Automation for this scenario for others who may want to implement this.

   Thanks again.

   Thanks for this suggestion.

   Change Data Capture is now supported quite well by SQL Change Automation projects which has plugins in both Visual Studio and SSMS. Configuring this does take some careful implementation as I’ll describe here.

   When setting up the project, I recommend setting the ‘comparison’ option for “Add object existence checks” to true. This can be done in the graphic project wizard in the SSMS plugin, and this means that any commands regarding the CDC schema, etc in your migration script will be written in an idempotent way that won’t cause errors. (Note: I didn’t see CDC system tables included in the baseline script, which is good.)

   It is also helpful to add a pre-deployment script to the project to ensure that cdc is enabled. This will enable project verification against a shadow database and build databases.

   If you wish to manage change tracking in your migration… more

4. Support for databases using replication

   I should be able to use SQL Release to deploy to a replicated database.

   20 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Delete…  ·  Admin →
   completed  ·  Kendra responded

   SQL 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.

5. Allow the Sync cmdlet (or similar) to generate an upgrade script without additional powershell

   Allow the Sync cmdlet (or similar) to generate an upgrade script without additional powershell

   19 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   completed  ·  Kendra responded

   Thanks for suggesting this.

   I believe that this has been completed in the form of the New-DatabaseReleaseArtifact cmdlet in the time since you made this suggestion, so I’m marking this as completed.

6. Create target database

   "DLM Automation works with your CI server and release management system, so you test, build, and release your database alongside your application code." Unfortunately, DLM only allows for the release of updates to existing databases -- suppose the target database doesn't yet exist? Deploying a NuGet package ought to allow for the possibility of initializing a new database.

   18 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   completed  ·  3 comments  ·  Delete…  ·  Admin →

7. Ability to run pre/post deployment scripts

   I should be able to run pre/post deployment scripts when doing a deployment with SQL Release.

   16 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Delete…  ·  Admin →
   completed  ·  Kendra responded

   Pre and Post deployment scripts are now available in SQL Change Automation, both for SQL Change Automation projects and SQL Source Control projects.

8. Support for deploying static data

   I should be able to deploy static data using SQL Release.

   10 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Delete…  ·  Admin →
   completed  ·  Robin responded

   Available 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

9. Visual Studio Improvements

   I would like to see a few filters added that would make working with the Main table of objects easier.
   Filter by Object type: Table, stored procedure, etc
   Filter Object name: Ability to type / paste in a partial name.
   Filter to show tables with data. With data, without data, all

   I have a project with 575 objects and growing. My main reason for this is working with tables that include data. It is hard to tell which tables include table data. We need a quick reference to see which ones are under source control. As I go through and assign new tables to include table data it is hard to scroll through the giant list and pick the correct objects.

   Thanks

   I would like to see a few filters added that would make working with the Main table of objects easier.
   Filter by Object type: Table, stored procedure, etc
   Filter Object name: Ability to type / paste in a partial name.
   Filter to show tables with data. With data, without data, all

   I have a project with 575 objects and growing. My main reason for this is working with tables that include data. It is hard to tell which tables include table data. We need a quick reference to see which ones are under source control. As I go through and… more

   9 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   completed  ·  1 comment  ·  Delete…  ·  Admin →

10. Add DLM Dashboard fields to VSTS Extension

    I'd like to be able to configure the VSTS extension to update our DLM Dashboard serer. At the moment I have to use a command line task to perform this.

    9 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    completed  ·  Michelle Taylor responded

    The latest VSTS extensions have DLM Dashboard fields available.

11. 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 variables, but that might tie you too closely.

    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… more

    8 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    completed  ·  Michelle Taylor responded

    DLMA v2 now features powershell cmdlets that are more modular than the previous SQLCI.exe and separate verification, testing, and packaging.

12. 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 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    completed  ·  Kendra responded

    Thanks 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

13. Sync Scripts to Database

    I'd like to be able to sync my database scripts which are stored directly in TFS (source control) as my 'source' db and then specify an actual database server as my 'target' database just like you do in the command line options for redgate sql compare.

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    completed  ·  3 comments  ·  Delete…  ·  Admin →

14. 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 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    completed  ·  fiona.gazeley responded

    We 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)

15. 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 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    completed  ·  Michelle Taylor responded

    The Octopus Deploy integrations should be able to allow Octopus Deploy to provide this facility for you.

16. Add AzureAD authentication

    Add the ability for the DLM process to connect to Azure DBs using Azure AD authentication. To me this makes sense as you have already added this functionality to SQL Compare.

    We are moving to Azure and this is the preferred way for us to connect to these databases. Without this functionality, we have to setup a SQL user for our VSTS user so that the DLM process can deploy the database

    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    completed  ·  Kendra responded

    SQL Change Automation now supports Azure Active Directory authentication for deployments via a service connection in Azure DevOps: https://documentation.red-gate.com/sca4/deploying-database-changes/add-ons/azure-devops/use-a-service-connection-to-store-target-database-credentials

    I believe this meets the request here so I am marking this as completed. Thanks very much for the feedback.

17. 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 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    6 comments  ·  Delete…  ·  Admin →
    completed  ·  Michelle Taylor responded

    As described in comments, this is now possible with the Powershell cmdlets. Please get in touch if you need this facility in the Bamboo addon.

18. Use filters and comapre options stored in source control as part of the deploy
    6 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Delete…  ·  Admin →

19. Integration with SQL Monitor
    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Delete…  ·  Admin →
    completed  ·  AdminStephanie (Product Manager, Redgate) responded

    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

20. Make Connection Timeout value configurable

    I am randomly getting the following error:

    'Error: Comparison of 'Scripts.state' and 'MyServer.MyDatabase' failed. Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections.

    When I re-run SQL CI with exactly the same parameters, next time it works.

    Can you make 'Connection Timeout' value configurable from command-line please?

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Delete…  ·  Admin →
    completed  ·  Michelle Taylor responded

    DLMAv2 cmdlets now have a timeout parameter so you can specify your own connection timeout.