50 results found

1. SQL Change Automation (VS plugin): Select All/Deselect All object

   I very often find myself making partial releases of the DB, and therefore most of my time I waste it selecting and deselecting the objects that I don't want to release.
   Would it be possible to put a "Select All" / "Deselect All" in the migration objects windows?

   For me it would be a really necessary feature :-)

   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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. New SCA cmdlets to quickly provision new Projects

   We have a very modular structure, with multiple SCA projects all targeting the same database. Each module can (and are) be independently releases. Each module in turn actually consists of 3 SCA projects, the Database Module Project, the Tsqlt Unit Test Project, and the Tsqlt Release Test project (smoke/regression/reconciliation tests).

   it would be ideal to have cmdlets that lets us quickly create, in a programmatic way, projects with the settings we have for each of these (references, clone image baseline provisioning, semantic versioning, dataspace, migration log schema etc, filter file etc).

   Include tsqlt files in test projects would be a nice bonus.

   This would allow us to use a simple powershell script to quickly create all 3 projects with the correct base settings (a lot of copy & paste, point and clicks removed...) by simply providing some basic parameters.

   We have a very modular structure, with multiple SCA projects all targeting the same database. Each module can (and are) be independently releases. Each module in turn actually consists of 3 SCA projects, the Database Module Project, the Tsqlt Unit Test Project, and the Tsqlt Release Test project (smoke/regression/reconciliation tests).

   it would be ideal to have cmdlets that lets us quickly create, in a programmatic way, projects with the settings we have for each of these (references, clone image baseline provisioning, semantic versioning, dataspace, migration log schema etc, filter file etc).

   Include tsqlt files in test projects would be a… more

   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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. VS Code project

   Hi,

   I would like to see a VS Code project option, with a much easier to maintain project file, potentially even splitting configurations into separate settings files using yml or similar.

   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…)
   1 comment  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. 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 be even better if the automated steps could then be used to trigger various other features that occur during the current manual SCA VS plugin process described here https://documentation.red-gate.com/sca/developing-databases/working-with-the-visual-studio-extension/generating-migrations-in-visual-studio
   For example the "what has changed" view - as a sanity check to make sure the change made was what was expected by the developer.

   This would be in an effort to reduce the number of manual steps required by a developer to enable a project to use varying complementary technologies (e.g. EF Core code-first for build and RedGate SCA for deployment).

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

   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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Create a branch based on one of the available annotated tags

   Our Create a hot fix procedure is:

   1. Create and get a bug fix into master using the procedures for making changes
   2. Create a local hot fix branch from current/test or current/production annotated tag
   3. Cherry pick bug fix commit(s) from master to the local hot fix branch
   4. Run a full build, all automated tests, and all migrations
   5. Push the local hot fix branch to the remote repository
   6. 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 create or delete & recreate an annotated tag with name current/test when a release is deployed to the Test stage. Similar for the current/production annotated tag and the Production stage.

   Since SQL Change Automation doesn't support creating a branch based on an (annotated) tag, the developer has to use another Git client to do step 2. This complicates the process and I'd prefer that the developer could do step 2 within SQL Change Automation as the process will be simpler and faster.

   This feature request is therefore to support creating a branch based on one of the available annotated tags in SQL Change Automation.

   Our Create a hot fix procedure is:

   1. Create and get a bug fix into master using the procedures for making changes
   2. Create a local hot fix branch from current/test or current/production annotated tag
   3. Cherry pick bug fix commit(s) from master to the local hot fix branch
   4. Run a full build, all automated tests, and all migrations
   5. Push the local hot fix branch to the remote repository
   6. 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… more

   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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. PackageVersion SQLCMD var should be set in PackageScript.sql when calling Export-DatabaseBuildArtifact

   Since we are already required to provide a PackageVersion parameter to Export-DatabaseBuildArtifact, I would like to see the PackageVersion SQLCMD variableset to that input value in the PackageScript.sql with in the build artifact.

   I would also like to see a new parameter for Invoke-DatabaseBuild, SQlCmdVariables, that wouldd allow us to pass in ReleaseVersion, PackageVersionm, and other SQLCMD vars that would be set in the PAckahgeScript.sql (and the PackageScript property of the returned BuildArtifact object.

   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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Set CodeGuard Checking Default to Off

   We use TeamCity and there seems to be no way (or no simple way) to disable CodeGuard checking. It's not really useful there for us (and we use SonarCloud which has nice integration/quality gates for GitHub).

   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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   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  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. 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 for easier debugging and checking.

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

    0 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  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close