Skip to content
← Customer Feedback for Redgate

Settings and activity

3 results found

  1. Commit data and schema changes separetly

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  SQL Source Control » Static Data  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Michael Melancon supported this idea  · 

  2. SQL Source Control Static Views (or Table Subsets using WHERE clause)

    636 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    30 comments  ·  SQL Source Control » Static Data  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    under review  ·  Kendra responded

    Hi everyone. I have merged some User Voice items on this topic of “filtered” static data, as there was significant overlap. I want to share our current guidance on handling scenarios where you need to version a subset of the columns and/or rows in the table.

    With SQL Source control, the best option at this point is to use a post-deployment script for this purpose.

    SQL Source Control introduced pre- and post- scripts in v6.3.

    A post-deployment script gives you a good amount of flexibility over exactly which rows or columns of data you want to include in your project. Example post-deployment scripts for static data are here: https://documentation.red-gate.com/soc7/common-tasks/working-with-pre-post-deployment-scripts/static-data

    If you make heavy use of Static Data, we have stronger support for this in SQL Change Automation.

    SQL Change Automation:

    • Supports column filtered static data tables in the SCA plugin in SSMS
    • Supports multiple post-deployment scripts, in case there is…
    An error occurred while saving the comment
    Michael Melancon commented  · 

    Really need to be able to select data to commit like the merge in Data Compare. I'm currently having to keep 2 copies of each database in my instance so I can make sure only the data I want to commit gets in

    Michael Melancon supported this idea  · 

  3. SQL Source Control Configuring Data Compare Options

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  SQL Source Control » Static Data  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Michael Melancon supported this idea  · 
    An error occurred while saving the comment
    Michael Melancon commented  · 

    And also to re-enable constraint checks. It's extremely annoying to have to go back and remove 'WITH NOCHECK' from every table when there is a data change.

    Why would anyone want the default to be to leave their database with all contraints disabled?? I have them there for a reason...