Red Gate forums :: View topic - Source Control
Return to RSS Feed Available

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

Source Control

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

Joined: 09 Jul 2013
Posts: 3

PostPosted: Mon Oct 07, 2013 10:34 pm    Post subject: Source Control Reply with quote

We are using Source Control with TFS, in shared mode. I put different servers under different projects.

Every time I restart SSMS, all the databases are marked as "possibly having uncommitted changes", even if there were no changes.

If I open "Commit Changes", it searches for changes, and then after some delay, returns with "no objects with changes to be committed to source control". The database icon also changes, indicating it has no uncommitted changes.

Has anyone else seen this problem? It's quite inefficient. Is there a way to avoid having to refresh source control for every database? Or, is there a batch script to refresh all databases in SSMS, instead of manually refreshing each database?

Also, I suspected that the problem might be related to using tempdb. The following seemed promising, but this article seems to assume that only one database server is used with the source control. Does anyone know what happens, if there is a way to specify this "per" database server?

Back to top
View user's profile Send private message

Joined: 16 Jun 2010
Posts: 1144
Location: My desk.

PostPosted: Thu Oct 10, 2013 2:19 pm    Post subject: Reply with quote

Hi Ben- I might need a little clarification on your exact setup. Shared mode is indeed intended to be used when one set of files in TFS maps back to one single database that is used by several developers at once.

If you have a few different SQL Servers, each having their own copy of the database, and these are all linked to the same TFS location, then that is "dedicated" mode. I can't quite tell if that's exactly the case from your post though...

In general, we show the blue blob when we detect a change to an object (by picking up an entry from tempdb, as you mentioned).
When you refresh the Commit tab, a full comparison between the database and the working base folder is performed and the blue blobs and commit tab will update according to whatever differences are picked up. This article which explains the architecture may help a bit: SQL Source Control architecture
Back to top
View user's profile Send private message
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