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?
http://documentation.red-gate.com/displ ... +databases