Skip to content
← Customer Feedback for Redgate

Settings and activity

1 result found

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

    633 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  ·  AdminStephanie (Product Manager, Redgate) responded

    Hi,


    We just added this capability to Flyway, which is our x-database, x-OS cloud- and Git-first Database DevOps solution for versioning and deploying database changes. You can learn more about this feature in Flyway at https://documentation.red-gate.com/fd/working-with-data-138347109.html#Workingwithdata-Controllingstaticdata.


    You can also import your SQL Source Control repos into Flyway while keeping your Git history. Learn more about moving to Flyway and importing your project at https://documentation.red-gate.com/fd/transitioning-from-other-redgate-tools-164167855.html.


    If you have any questions, please comment below or reach out to us at DatabaseDevOps@red-gate.com.


    Thank you!

    Stephanie Herr

    Product Manager - Database DevOps

    An error occurred while saving the comment
    Jason Duffett commented  · 

    The problem we have is that the current EAP builds of SQL Source Control aren't usable because of the limited data support.

    We use the tools in the following way:
    1. A single SVN repository
    2. SQL Source Control for developers to check-in changes to this source tree.
    3. Custom SQL Compare and SQL Data Compare scripts to deploy changes from the repository to our test, staging, production environments

    Testing we've done with the pre-release SQL Source Control have failed because it always tries to overwrite the data in the repository.
    We won't be able to use the new release unless either we can completely disable data support in SQL Source Control, or the data support is enhanced to allow us to specify which columns to source-control.

    Jason Duffett supported this idea  ·