Allow "Get Latest" in shared model
We occasionally restore a copy of production db over our development db. With SCC in place I imagine it will work like this:
1) Everyone commits dev changes that they care to keep
2) perform restore
3) One person relinks SSC in dedicated mode and uses "get latest" to pull down latest schema to the newly restored dev db.
4) everyone can resume working in shared model.
To cut out the relink in step 3, it would be nice to be able to use the "Get Latest" tab in shared model for occasions like this
WT Jones
shared this idea
-
Andy Joiner
commented
You may be able to use this work-aound: http://stackoverflow.com/a/19405352/270155
-
Greg Bacchus
commented
This would really be useful, most of our SQL Devs work on their own local database, and then we update the changes out onto a centralized testing database. A couple of devs don't work on local database an just need to make changes to the central database.
So we need a way to manage the commits of their changes as well as updates to that central DB from the repo.
-
Anand
commented
It would be very helpful to allow svn updates across multiple databases like DEV, UAT, QA and PROD.
-
AdminJames Billings
(Admin, Redgate)
commented
We wouldn't normally suggest linking a production database to SQL Source Control. If you need to update the development database with changes from production, you'd ideally look at deploying the changes over using SQL Compare, and then committing the update into SVN from SQL Source Control in the usual way.
-
Anonymous
commented
Same problem for us! Actually it seems that sql source control does only support working with several developers on ONE instance of a database. The moment you work on e.g. two instances of a database (dev and prod), the "shared" mode doesn't work anymore and you need step 3 as per "WT Jones". Hope, we can get this fixed soon! Thanks in advance!