36 results found

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

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

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

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

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

4. 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)

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

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

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

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

10. 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 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  ·  fiona.gazeley responded

    Available 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

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

12. Support databases with full text indexes

    I want to use SQL CI with database that contain full text indexes

    1 vote

    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

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

13. 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 vote

    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

    You can now remove any default SQL Compare options by specifying them prefixed with a minus sign.

14. Allow tSQLt tests to be synchronized

    I want to sync my tSQLt tests with my test environment.

    1 vote

    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  ·  Michelle Taylor responded

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

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

    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

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

16. 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 vote

    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.

    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.