Shared Model Improvements Release

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

Shared Model Improvements Release

Postby csmith » Fri Jun 08, 2012 2:36 pm


I'm pleased to announce the Full Release of SQL Source Control v3.1 that includes improvements to the audit information provided in the 'Shared Model' environment. To install it please install the latest SQL Developer Bundle from and then open SQL Source Control and select the latest update when prompted.

Original post:
I'm pleased to announce an Early Access Release of SQL Source Control v3.1 that includes improvements to the audit information provided in the 'Shared Model' enviroment. Download it from:
" Source Control_3.1.0.458_x86_r209112.exe".

What�s new in this Early Access build?
This release will benefit you if you�re using the �shared database� development model. Schema changes you and your co-developers make will be listed as changes in the SQL Source Control �changed by� column. Unfortunately, the current implementation does not persist the data for very long as it is stored locally for each SQL Source Control installation. This has been an issue that many of you have raised in our Uservoice forum. In this release we have changed the implementation so that the �changed by� data is stored in a database, �RG�, created on your server.

Please let us know if you have any feedback, good or bad, on the RG database implementation.

Release Notes:
* Object drops will come up as �Unknown� (we have already identified a fix for this, and may update the EAP next week as a result)
* Changes to extended properties on objects will come up as �Unknown�

Last edited by csmith on Thu Nov 15, 2012 5:49 pm, edited 2 times in total.
Chris Smith
Project Manager
SQL Lighthouse
Posts: 120
Joined: Thu Jun 30, 2011 1:15 pm
Location: Cambridge

Postby dbdmora » Fri Jun 15, 2012 2:26 pm

What is the ETR (estimated time of release) for V3.1 of SSC? Thanks
Posts: 34
Joined: Mon Nov 21, 2011 8:55 pm
Location: Atlanta, GA

DB usage an option?

Postby celeryisbad » Fri Aug 17, 2012 1:22 pm


I'm using this new version - if the user doesn't have access to create the new required database, there's an error and the tool is unusable...

Can the use of this be optional? Also - would be good to have a single file on a shared drive accessible by all users rather than the db if possible.

What date will we see an official release Chris?

\"If I'd asked the people what they wanted, they'd have said 'Faster Horses' \". Henry Ford
Posts: 1
Joined: Fri Aug 17, 2012 1:18 pm
Location: London

Postby anna.p » Mon Sep 10, 2012 10:06 pm

I second dbdmora's question.
Is there an estimated time of release for this version?
Posts: 23
Joined: Tue Jul 03, 2012 9:59 pm

Postby David Atkinson » Mon Sep 10, 2012 10:10 pm

Thanks for the question. It *should* be days, provided nothing bad turns up in the final phase of testing.

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

Postby MBBW » Wed Sep 26, 2012 4:34 pm

SQL Server 10.50.4000


We are testing the shared model with the SSC changelog database implemented as described at ... ng_changes .

Without deep testing it seems to be necessary that each developer has to be a member of the sysadmin role. Otherwise SSC does not work and errors raise like:

System.Data.SqlClient.SqlException: The user does not have rights to perform this action. (Translated from German)

Can you confirm this statement and in case please update your guide? In this case the goal should be that developers can work with least privileged SQL Server logins.

Posts: 12
Joined: Tue Mar 08, 2011 12:36 pm

Postby anna.p » Wed Nov 14, 2012 2:31 am

Have you guys been able to fix the bug with v3.1 that caused the permission error for non-sysadmin users?
Posts: 23
Joined: Tue Jul 03, 2012 9:59 pm

Postby samssb82 » Mon Dec 17, 2012 2:31 pm

Is there an estimated date as to when the issues outlined in will be corrected?
Posts: 2
Joined: Thu Aug 23, 2012 9:05 pm

changes not being picked up when restarting SSMS

Postby mryhmln » Thu Jan 10, 2013 5:22 pm

After upgrading to 3.1, SQL Source Control no longer seems to pick up changes that I am making to the db through SQL Management Studio. I have to restart SSMS in order for SSC to detect any changes.
Posts: 12
Joined: Mon Aug 29, 2011 3:05 pm

Return to SQL Source Control Previous Versions

Who is online

Users browsing this forum: Yahoo [Bot] and 0 guests