Icons only updated after "get latest changes"

BartG

Hi,

I just installed a SQL Source Control trial v6.0.2.6908 in my SSMS v12.0.5000.0 connected to a SQL Server Standard v12.0.4237.0, set up with a shared SVN repository.

I see that the overlay icons on my database object in SSMS Object Explorer only update when I choose right-click > "Get latest changes from source control...". Is that normal?

There's an option "Indicate changed objects and update indicators..." that is checked and set to the default 25 seconds. But I can wait minutes and refresh whatever I want...it doesn't update the icons. Only when I get the latest changes.

It doesn't sound like it's supposed to work like this.

Kind regards,
Bart

BBalboa

Source Control somehow gets out of sync after a bulk check in. I had not seen this error in a couple of months because lately I’ve made small changes to the DB, and all works OK.

This week, I have made several bulk check ins to the DB code, and my base code is out of sync. Facts:

1. This is a brand-new DB our team is working on, started with an empty DB
2. I’m the only person maintaining this source, nobody else in my team has linked their working copy to this source
3. Monday 1/22 – Red-Gate source control – I bulk checked in 38 tables and 64 stored procedures, for a total of 102 SQL objects, entered comments
4. Tuesday 1/23 – Red-Gate source control, I checked in a handful of stored procedures, as alter scripts, entered comments
5. Wednesday 1/24 – Red-Gate source control, I checked in 2 new stored procedures, and 2 or 3 existing stored procedures changes, entered comments
6. Wednesday 1/24 –To validate I’m current (which I should be), I clicked on Get latest tab expecting to see nothing since I’m the only user and I’m current with changes; to my surprise, I found:
a. 4 objects (stored procedures) are different from the repository to my local DB
b. These 4 stored procedures were part of the bulk check in I did on Monday 1/22
c. 2 of them were changed and checked in yesterday Tuesday 1/23
d. 2 of them were changed and checked in this morning Wednesday 1/24
e. Changes History: The dates, author, comments and revision number are incremental, comments are in line with the changes made during the check in step
f. If I go to the affected database and script out these 4 stored procedures, they are an exact copy to what the TFS repository has, which means that Red-Gates’s internal working file got out of sync

I know that I can fix this by
- Executing “get latest”
- Reapply my changes, and check them in again

I agree with this report, I don't think it is supposed to work like this; this appears to be a bug that I found by chance, Source Control somehow leaves one of the sources out of sync.


This is an update (01/26/2018).

- I did what Source Control asked me to do, I got the latest copy from source, the 4 stored procedures.
- Because I know the source control copy and my local database are in sync, now I have a conflict. The visual comparison doesn’t highlight any differences, because there were none in the first place.
- I selected from Show button - Line Differences, and no code is in there (expected).
- I checked in 7 more changes, and only 3 went through, now I have again 4 stored procedures in my list “Get Latest”, and those 4 are the changes I checked in few minutes ago.
-

BBalboa

Note: This happens in Red-Gate Source Control Version 6.0.2.6908
SQL Server v 17.4

Before I upgraded, I had installed on my machine Red-Gate Source Control 4 and SQL 2014 for a few years and never had this issue, until I upgraded in November 2017.

BartG

Hi BBalboa,

Thanks a lot for your detailed reply! This sounds like what I'm experiencing. If there's no feedback from Redgate soon, and a fix, I'll see if there are other source control products on the market (I'm still using a trial, did not buy yet).

Thanks again!

Mike U

No, it definitely shouldn't work like that. Unfortunately though, the cause of the problem is likely to be specific to your environment, so the support team will need to get in touch with you to figure out what's going on. A ticket has already been created for you, @BartG , and I'll ask support to create a ticket for you as well, @BBalboa

BBalboa

This is a new error I got today: