Shared Model Improvements Release
csmith
Posts: 138 Bronze 1
Hi
UPDATE:
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 http://downloads.red-gate.com/SQLDeveloperBundle.exe 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:
"http://downloads.red-gate.com/EAP/SQLSourceControl/SQL 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�
Thanks,
Chris
UPDATE:
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 http://downloads.red-gate.com/SQLDeveloperBundle.exe 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:
"http://downloads.red-gate.com/EAP/SQLSourceControl/SQL 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�
Thanks,
Chris
Divisional Development Lead
Redgate Software
Redgate Software
Comments
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?
Thanks!
Joe
Is there an estimated time of release for this version?
David Atkinson
Red Gate
Product Manager
Redgate Software
SQL Server 10.50.4000
Hello!
We are testing the shared model with the SSC changelog database implemented as described at http://www.red-gate.com/supportcenter/c ... 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.
Thanks!