Skip to content
← SQL Data Compare

How can we improve SQL Data Compare?

SQL Data Compare

Categories

JUMP TO ANOTHER FORUM

(thinking…)

SQL Data Compare - Automatically select linked static tables for comparison when using Source Control

When I am comparing a SQL Source Control Repository against a DB, we need find an option to only compare tables which are linked for static data in source control.
This seems like a glaring missing feature, since I now have to create a project that manually maps all the tables that have static data and ignore everything else, and manually update it when new static tables are included in the repository.

4 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…)
Alex Harper shared this idea  ·   ·  Report…  ·  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

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Alex Harper commented  ·   ·  Report

    Hi Kendra,

    In this case, Source Control is the source of truth based on a model database rather than the development database, and the static data needs to be updated in source control and then these updates deployed from source control to test/production.

    There's no need to update static data in source control from external DBs EXCEPT the cherry picked updates from the development DB.

    I know this isn't the typical scenario, but I've inherited a messy development DB that can't be used as a model for deployment.

  • AdminKendra (Admin, Redgate) commented  ·   ·  Report

    Hi Alex,

    I am curious how often you need to do this task / what the workflow is with your static data tables is that makes this useful?

    I think typically "static data" has a bit of a one-way flow, and simply gets added to the development database, committed, and deployed from there.

    But it sounds like you have a case where the data may be added to other databases in your environment, and then needs to get added back into the static data table in the development environment after? Almost like a kind of static data drift that needs to be handled?

    I'd love to learn more about the scenario to understand it better.

    Kendra