single shared database mode

A SQL Server Management Studio add-in to source control your database in Subversion or Team Foundation Server.

single shared database mode

Postby d.roberts » Mon Oct 11, 2010 10:54 am

I have some suspicions that whilst working in this mode, and I know its not recommended but it works best for us, that some users might be doing a getlatest and potentially overwriting teh changes that other users have made but not yet checked in.

Firstly, is this possible? (maybe when a new user links to an existing TFS controlled db?)
secondly, can GetLatest be disabled for shared db mode (apart from maybe an admin user?)
Posts: 8
Joined: Mon Sep 13, 2010 4:05 pm

additional question about this mode of use

Postby d.roberts » Mon Oct 11, 2010 2:01 pm

SSC is stating that one of the differences is a conflict.

I'd like tounderstand how SSC can determine this if we are using a shared db model?
Posts: 8
Joined: Mon Sep 13, 2010 4:05 pm

Postby eddie davis » Tue Oct 12, 2010 12:58 pm

Thank you for your post into the forum.

When using the shared db model you increase the chance of conflicts in the manner that you have described.

SQL Source Control supports both methods, dedicated and shared but we (Red Gate) recommend the dedicated model as this greatly reduces the known problems using the shared model.

This Knowledge Base article explains the Database Development Models.

I hope this helps to answer your questions.

This second knowledge base article explains Conflict resolution.
Eddie Davis
Technical Support Engineer
Red Gate Software Ltd
eddie davis
Posts: 1146
Joined: Wed Jun 14, 2006 2:47 pm
Location: Red Gate Software

Postby d.roberts » Wed Oct 13, 2010 8:32 am

The article with detail of the shared model limitations is useful, especially as it hints at your use of a local copy of the scripts (on each dev pc, even in shared db mode) to determine changes and conflicts.
Posts: 8
Joined: Mon Sep 13, 2010 4:05 pm

Postby David Atkinson » Wed Oct 13, 2010 9:06 am

We hope to improve the usability of the shared model in a later release, with information in the commit list on who made which change, and maybe a warning if you try to commit a change you may not have made yourself.

At some point we hope to avoid the spurious conflicts, but for now, they can simply be ignored and 'keep mine' selected.

David Atkinson
Product Manager
Red Gate Software
David Atkinson
Posts: 1143
Joined: Mon Dec 05, 2005 3:54 pm
Location: Twitter: @dtabase

Return to SQL Source Control Previous Versions

Who is online

Users browsing this forum: No registered users and 0 guests