Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control: Better Support for Shared Db Dev Model

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Shared Model - multiple instances of the same DB

Most of our enterprise applications have mutiple instances of the same DB schema. We use the shared model and would like to update al instances once we commit changes on one of them. As a workaround we commit the changes and then hit revert changes on the instances we need to update

70 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…)
Tudi 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
  • AdminJames Billings (Admin, Redgate) commented  ·   ·  Report

    It sounds like you're using what we'd term "hybrid" model- where you have several databases with multiple users working on them that are all part of the same project. Unfortunately this leads to the problem you're experiencing as the "Get Latest" tab doesn't do anything when you're working shared model.

    Another option is for one user to temporarily unlink, relink in dedicated, do a Get Latest to update the database (which will update it for all other users working on the same DB) and then relink back in shared model again.

    In the longer term we're looking at improving this, which may well include removing the shared/dedicated choice altogether (it's really a choice that users shouldn't have to worry about and is there more to help the product)