Current link (the one above is half-dead):
https://documentation.red-gate.com/soc6/troubleshooting/refresh-in-commit-and-get-latest-tabs-takes-a-long-time

Every time you select a database, SSC automatically does a get latest automatically... This still seems to be an issue with SSC version 6.2.3.7820 and using SSMS version 17.8.1.

The last administrator comment was almost three years ago, with a status of "under review"? What is the real status on this? It would be great to be able to have control over how the application works, rather than having to choose to either use it or not.

That's all very well, but you're no longer allowed to change the polling time and SSSC is getting slower and slower with every single release.

We have over 8000 stored procedures, tons of views, tables, etc... The initial registering and this refresh slowness may make it impossible for us to use the product.

If being able to switch off the auto refresh that occurs when the Commit or Get Latest tabs get focus "is not currently on the roadmap" then Redgate has lost it's way.

And "increase the polling interval" doesn't affect the behaviour.

It makes a reasonably useful product almost unusable.

We are facing the same problem with version 5.5.2.4725. Everytime I change the tab to check something, I have to wait for the auto-refresh to complete when I return to the Source Control Tab. This is very annoying and takes much time, because our development database is quite big. Do you have any news on this?

Its now march 2015, and the latest version still doesn't have this feature/option...

We are using the 3.7.6.281 Trial Version and this problem still exists! Do you have an update on this issue? Many thanks

Fixing this would be a real time saver for every user of SQL Source Control. I just received a reply from Red Gate Support regarding this request, but they couldn't say anything other than the more popular (through votes) the greater chance of it been added.

To all of you out there: Please vote on this feature request and remember you have more than one vote you can use!

It's been 4 years since this issue as been reported and 12 months since an admin update on this. This happens 10+ times a day for me. I find it hard to believe this even made it through user acceptance testing. It's bad enough that SQL Source Control is dog slow, but this effectively forces you to wait for the source control to update every time you want to check in a commit, rather than letting it happen in the background while you do other things in SSMS.

still waiting

Waiting for the tab to be updated steals too much time from our development team. We do have powerful computers (i7 CPU, 16GBRAM, SSD HD and better on our servers) so please take action on this one now. We often switch between tabs in SSMS so this is a problem for us.

Could the determine/calculate prosess go in the background, and if any new changes detected in SVN, then a message over the list could appear saying "Changes detected. Click to refresh/Click refresh button"?

Best regards,
Geir Andre Rasmussen, APTO AS

What is the ETA on this enhancement?

I'd also say to make the refresh button prominent instead of the commit, since refreshing is really the first and foremost action.

This would be better solution.
Can you also add a Combobox for selecting database instead of switching every time when different database selected in Object Explorer. It is not misleading when source control trying trying to show database not linked to source control.

This would work. We have not been able to get the dev team to use source control because of the slow speed.

This is such a good idea, our databases our fairly large and we have multiple work items in TFS. When checking items in I would love to check in bits and pieces to separate user stories without having to wait for a refresh every time.

Excellent! FIXED! Despite not being a SSMS2012 lover, at least it's now fully usable.

Thanks to all.

Hi Stephen,

Thanks for the information about the MDI-mode in SSMS2008R2.

If you upgrade to v3.2, we just persisted user selections on the Commit tab if you leave and come back. Hopefully that means you won't lose everything you've just set up to commit.

NEVER had this issue in MDI-mode in SSMS2008R2 - it's a royal pain in the butt now I'm in SSMS2012.

The auto-refresh is an absolutely nutty idea - we lose everything we've set up to commit!

Cannot understand why this DEFICIENCY is not at the top of the MUST FIX list - "Under Review" @ 2/14/2013 isn't "feeling the love" ;-)

Just upgraded to 3.1.4.72.

Workaround: Use SSMS2008R2 in MDI mode - issue solved for now!

(If I had more votes: +3 at least)