Red Gate forums :: View topic - Change tracking already enabled, can we use that?
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Source Control 3
SQL Source Control 3 forum

Change tracking already enabled, can we use that?

Search in SQL Source Control 3 forum
Post new topic   Reply to topic
Jump to:  
Author Message
EvilGreebo



Joined: 04 Jun 2014
Posts: 3

PostPosted: Wed Jun 04, 2014 7:02 pm    Post subject: Change tracking already enabled, can we use that? Reply with quote

I'm starting the trial period on SQL SC 3 and I had alerted our DBAs that I was creating a new test DB for change log tracking and what would be the plan moving forward if we adopt...
Quote:

One requirement of this plugin is that in order to be able to keep a full history of who changed what, a custom ChangeLog database must be created. The tool will work without this database but changes are kept in TempDB which means every time the server restarts, we lose the history. (See: http://documentation.red-gate.com/display/SOC3/Logging+changes+to+shared+databases )


This was the reply from the senior DBA:
Quote:

Reviewing..would rather see dedicated db instead of tempdb. But, if we want to do this – why not just have us enable change log tracking on specific databases?


So - question - CAN SC3 use existing sql change log tracking if it's been enabled?
Back to top
View user's profile Send private message
EvilGreebo



Joined: 04 Jun 2014
Posts: 3

PostPosted: Fri Jun 06, 2014 1:30 pm    Post subject: Reply with quote

Any support team members even reading these forums?
Back to top
View user's profile Send private message
Evan Moss



Joined: 12 Jun 2013
Posts: 93

PostPosted: Mon Jun 09, 2014 4:17 pm    Post subject: Reply with quote

Hello,

Thanks for your post.

Unfortunately the only way for SQL Source Control to keep track of usernames in the shared model (http://documentation.red-gate.com/display/SOC3/Database+development+models) is a table we create called RG_AllObjects (this is in tempdb by default, but you can create a dedicated database for it like in the article you mentioned.)

(Also, if you need to get a support ticket started quickly in the future, emailing support@red-gate.com creates a ticket immediately, whereas on the forums, a ticket is only created if no one responds in two days.)

Regards,
Evan
_________________
Evan Moss
Product Support
(866) 627-8107
Back to top
View user's profile Send private message Send e-mail
EvilGreebo



Joined: 04 Jun 2014
Posts: 3

PostPosted: Wed Jun 11, 2014 6:49 pm    Post subject: Reply with quote

Understood.

One disappointing find was that when I checked in changes to a db made by a co-worker into SVN, our repository logged those changes as belonging to me, even though the checkin tool showed that he made them.

So is the idea here that the table is used to show the developer who made each change in the shared db so that they don't inadvertently check in someone else's stuff?
Back to top
View user's profile Send private message
Evan Moss



Joined: 12 Jun 2013
Posts: 93

PostPosted: Thu Jun 12, 2014 4:31 pm    Post subject: Reply with quote

Hello,

You're correct -- the username recorded by the source control repository is associated with the user that does the commit (it's because that's the user actually checking in files to your source control system). The "changed by" column is so that you can track for your own purposes.

Thanks,
Evan
_________________
Evan Moss
Product Support
(866) 627-8107
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group