Keeps showing uncommited changes even if there are none

A SQL Server Management Studio add-in to source control your database in Subversion or Team Foundation Server.

Moderators: Chris Auckland, David Atkinson, sherr, PhilScrace, andy.campbell.smith

Keeps showing uncommited changes even if there are none

Postby needbrew99 » Fri Sep 21, 2012 3:14 pm

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.
needbrew99
 
Posts: 7
Joined: Fri Sep 21, 2012 3:11 pm

Postby Chris Auckland » Mon Sep 24, 2012 8:14 pm

This sounds like a bug.

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.
Chris
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.

Postby needbrew99 » Mon Sep 24, 2012 8:29 pm

It keeps changing objects. If I open the SQL Source Control tab and it syncs up, there are no differences and the icons change to normal, almost immediately the icon changes to changed objects, and if I expand the tables folder or Stored procedures it will be a different one
needbrew99
 
Posts: 7
Joined: Fri Sep 21, 2012 3:11 pm

Postby Chris Auckland » Mon Sep 24, 2012 8:34 pm

Are you using the shared model? Could other users linked to the same database be committing the changes?
Chris
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.

Postby needbrew99 » Mon Sep 24, 2012 8:37 pm

Using the shared, but there are no other changes going on. When I Click on the Commit Changes Tab and it sync's up, the icons change in the Object Explorer to show nothing is different. Then when you click on something else, the change icon appears again.
needbrew99
 
Posts: 7
Joined: Fri Sep 21, 2012 3:11 pm

Postby Chris Auckland » Mon Sep 24, 2012 8:40 pm

ok, I think this needs investigating. Leave it with me.

I take it you're on the latest version (3.1.0.4583)
Chris
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.

Postby needbrew99 » Mon Sep 24, 2012 8:44 pm

yes I am
needbrew99
 
Posts: 7
Joined: Fri Sep 21, 2012 3:11 pm

Postby needbrew99 » Mon Sep 24, 2012 8:44 pm

Was working fine before I upgraded to the new version.
needbrew99
 
Posts: 7
Joined: Fri Sep 21, 2012 3:11 pm

Postby Chris Auckland » Thu Sep 27, 2012 10:22 am

Sorry for the delay.

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?
Chris
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.

Postby needbrew99 » Thu Sep 27, 2012 1:10 pm

The table is there and is populated with 7183 rows of data
needbrew99
 
Posts: 7
Joined: Fri Sep 21, 2012 3:11 pm

Any update on this issue.

Postby needbrew99 » Tue Oct 02, 2012 2:41 pm

This is really getting to be a pain. Every DB shows as having changes to commit, even though nothing has changed.
needbrew99
 
Posts: 7
Joined: Fri Sep 21, 2012 3:11 pm

Postby Chris Auckland » Thu Oct 04, 2012 11:52 am

This seems to be an issue with the query we use to check for changes. It seems to be picking up on all sorts of system objects that it should really filter out.

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.
Chris
Chris Auckland
 
Posts: 757
Joined: Tue Oct 24, 2006 2:12 pm
Location: Red Gate Software Ltd.

Postby achamp » Tue Nov 13, 2012 9:37 am

I am also getting random blue dots on databases where there are no changes to commit and where I know the database hasn't been changed behind the scenes.

I am running version 3.1.0.4829 so do I still need to downgrade to version 3.0.13.4214.exe
achamp
 
Posts: 11
Joined: Wed Aug 16, 2006 3:10 pm

Postby mikehalford » Thu Nov 22, 2012 1:37 pm

I am also getting the same issue. I thought you had to be running at least v3.1 to use TFS service.

By downgrading does that mean we cannot use Team Foundation Server Service?
mikehalford
 
Posts: 7
Joined: Thu Nov 22, 2012 1:32 pm

Postby PDinCA » Tue Nov 27, 2012 2:55 am

Any update on this issue, please...?

I'll live with the fake-blue-dots as I'm the only DB developer, but it is rather confusing to see.
PDinCA
 
Posts: 512
Joined: Mon Jul 25, 2005 11:42 pm
Location: Costa Mesa, CA, USA

Next

Return to SQL Source Control 3

Who is online

Users browsing this forum: No registered users and 1 guest

cron