Keeps showing uncommited changes even if there are none
needbrew99
Posts: 8
Using TFS and the latest version, I keep getting the icon that there are changes to commit. When I open the tab to check, there are no changes to commit and the icon goes back to normal. A few seconds later it changes back and says there are changes to commit.
Comments
Could you send me the DDL for the object that keeps popping up on the commit tab? It could be some syntax were not handling correctly.
I take it you're on the latest version (3.1.0.4583)
When using the shared model in the latest version (3.1) we now record the changes in a table called 'RG_AllObjects' in tempdb. If this table is removed or couldn't be created for whatever reason, then it might cause strange behaviour with the blue indicators.
Could you check if you have this table and if it's populated with data?
We have had this and a few other problems with the 3.1 release, so we've actually now pulled it from the website until we fix these issues with the shared model.
I would recommend downgrading to version 3.0 for the time being:
http://downloads.red-gate.com/checkforu ... 3.4214.exe
Sorry for the inconvenience.
I am running version 3.1.0.4829 so do I still need to downgrade to version 3.0.13.4214.exe
By downgrading does that mean we cannot use Team Foundation Server Service?
I'll live with the fake-blue-dots as I'm the only DB developer, but it is rather confusing to see.
Decide wisely...
It is becoming a big problem. Object explorer shows many items that it thinks need submitting, by highlighting with blue bubble, but SQL Source Control states no changes have been made. Getting to a stage where we might revert to another method of source control until a reliable version becomes is available.
As stated in earlier post we cannot downgrade as we are using Team Foundation Service which is only supported in the latest release I was told.
Any update would be most appreciated
I have the persistently misleading blue dots with SVN.
Decide wisely...
We work in a dedicated model and I am seeing this issue as well. Very big problem as we have 24 databases that we may have to work against on multiple instances and refreshing each one to see if there really are changes to commit is very very time consuming. Reminds me of the old MS DBproj process of building and deploying to your local.
We have never worked in a shared model so I am not sure if the tempdb table is even relevant. I have checked and I do have that table and it has over 10622 rows in it.
I am still not sure why these source control tools from RedGate don't use the physical files on the developers machines that are written out when they perform a get latest to their local workspace.
Seems like the only source control aspect of SSC is the web service or command line operations for performing check-ins and associating the changes to work items for the relevant source control system.
Red Gate Technical Support Engineer
Do we have any further information on when the update will be available?
Many Thanks
Many Thanks
I can get it to reproduce every time now.
1. Close SSMS
2. Open SSMS and connect to server
3. Click on a database that is linked and that has no changes pending. Wait for it to finish comparing. (Click on "Get Latest" tab and wait for "no new changes in source control")
4. Click on different database, can be linked or not, the database that was clicked in step 3 above, now shows that everything is out of data. (Blue circle on Green Server Icon and on every object in that database.)
Software Engineer
NTS Data Services, LLC
Thank
Software Engineer
NTS Data Services, LLC
1. Open SSMS
2. Click on Linked Database
3. Wait for it complete compairson
4. Click on differetn Linked Database. Database in step 2 above now shows everything is out of data....
Software Engineer
NTS Data Services, LLC
There's two ways you can work around this right now:
1. Downgrade to a version of SQL Source Control that used the previous version of the polling query - the last version to use the old query was 3.0.13.4829, available here:
ftp://support.red-gate.com/patches/SQLS ... 0.4829.exe
You'll need to uninstall SQL Source Control and delete the following objects from tempdb before you run that installer:
Table : RG_AllObjects
Stored Procedures: RG_WhatsChanged
Scalar functions : RG_PersistentTableVersion, RG_ProcVersion
2. Disable polling in SQL Source Control. This means that you won't get blue blobs on objects without going to the Commit Changes tab yourself and performing the full comparison to source control.
To do this, open %localappdata%\Red Gate\SQL Source Control 3\RedGate_SQLSourceControl_Engine_EngineOptions.xml and add the line
as a child of the main <EngineOptions> node.
If there isn't a RedGate_SQLSourceControl_Engine_EngineOptions.xml file in that folder, you can create one yourself - the entire file contents should look like:
Red Gate Technical Support Engineer
Software Engineer
NTS Data Services, LLC
The latest release (3.1.4.72) which was made available yesterday, has a fix that should stop blue blobs displayed following the first click on a database in a new Management Studio session.
We are aware of some cases where blue blobs are erroneously shown later on in the workflow, but the initial startup one should be fixed.
Could you try upgrading and see if that fixes the problem for you?
Regards
Chris
SQL Source Control
Red Gate Software