Sorry for the slow reply.
We're still looking into performance improvments for SQL Source Control, but I can give you a workaround which might help you in the mean time.
The workaround is to disable the code that polls your database. This will mean that the blue indicators in the Object Explorer are often out of date, but it should reduce the load on your database server to acceptable levels.
To apply the workaround, you will need to edit the 'RedGate_SQLSourceControl_Engine_EngineOptions' in your SQL Source Control configuration directory. This is either: C:\\Users\\<username>\\AppData\\Local\\Red Gate\\SQL Source Control 1 or C:\\Documents and Settings\\<username>\\Local Settings\\Application Data\\Red Gate\\SQL Source Control 1 depending on your operating system version.
The following XML is an example of setting the polling frequency to '0'. This will mean that SQL Source control will not check for changes, but you can still manually perform the check if you hit 'refresh'. You might want to try different values between 0 and the defaults, until you have an acceptable performance.
- Code: Select all
<?xml version="1.0" encoding="utf-16" standalone="yes"?><!----><EngineOptions version="2" type="EngineOptions"><DefaultTraceMinimumInterQueryTimeInMillis>0</DefaultTraceMinimumInterQueryTimeInMillis><SysObjectsMinimumInterQueryTimeInMillis>0</SysObjectsMinimumInterQueryTimeInMillis><SysTypesMinimumInterQueryTimeInMillis>0</SysTypesMinimumInterQueryTimeInMillis><DefaultTraceMinimumRequestedInterQueryTimeInMillis>0</DefaultTraceMinimumRequestedInterQueryTimeInMillis></EngineOptions>
THE v1 DEFAULT VALUES ARE:
I hope this helps.