Thank you very much for the patience on this issue. SQL Source Control 6.3.2 now includes an option ‘DisableAutoRefresh’ to disable automatic refresh of the commit and get latest tabs. See https://documentation.red-gate.com/display/SOC6/Refresh+in+commit+and+get+latest+tab+takes+a+long+time for more details. Please get in contact if you have any additional feedback on this issue.

Apologies for the radio silence on this, but the request as described is not currently on the roadmap. In the first instance, we are going to take another hard look at the underlying performance issues.

If you have challenging performance scenarios, now is a great time to bring them to us. The more scenarios we can understand and recreate, the better.

As a workaround for not being able to turn off auto-refresh, you can increase the polling interval (in the SQL Source Control Setup tab) and manually refresh.

We’re currently thinking seriously about adding a SQL Source Control option to stop refreshes of the Commit list automatically.

In the first instance this will be a manual override (probably in an XML config file). When this is turned on, SQL Source Control will never automatically initiate the query to generate the list of objects to be committed. You will have to click the existing Refresh button to generate the list. The generated list will be remembered if you switch SSMS tabs and come back later to SQL Source Control’s Commit tab.

If you visit another database in Object Explorer, then the first database’s commit list will be remembered when you go back to it. However, for memory reasons, the data for only the last two databases will be stored in this way.

If the mechanism works then it is likely that this will be configurable from the user interface at a later date.

Note that this is separate from the background polling query to create the blue blobs in Object Explorer, which can continue to be disabled with its existing configuration item.

If you voted for this suggestion then please comment on whether the proposed solution sounds like it would work for you.

We’ve re-opened this ‘idea’ following your feedback.

Some of you would prefer the commit/get latest refresh process to always be manually initiated, rather than the conditional refresh we have implemented in SQL Source Control.

Please vote for this idea if you would rather have complete control over the refresh of commit and get latest tabs.

This performance improvement now appears in SQL Source Control version 2.2!

For more information about the release, please see:

http://www.red-gate.com/MessageBoard/viewtopic.php?t=13735

This performance improvement now appears in the SQL Source Control 2.2 Release Candidate!

For more information and to try out the release, please see:

http://www.red-gate.com/MessageBoard/viewtopic.php?t=13668

This performance improvement now appears in SQL Source Control 2.2 Early Access Release.
Please see the following RedGate forum posting:

http://www.red-gate.com/MessageBoard/viewtopic.php?p=48466#48466

We’ve started work on this, and hopefully it should be going out in an Early Access release sometime in May.