Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control

Categories

JUMP TO ANOTHER FORUM

(thinking…)

I like this very much. However I am experiencing one problem. (CPU usage is too high)

RG Source Control "seems" to hog the machine with the databases. The CPU goes 75% +, disk activity goes abnormally high, Logical reads is high, compiles is high, etc. (according to Quest Spotlight on SQL Server). Also, users are having queries time out.

I can close SSMS and the machine returns to normal (CPU around 10%, other metrics low).

I will have to remove it for now until this is corrected/changed.

25 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Brett Walker shared this idea  ·   ·  Report…  ·  Admin →
declined  ·  fiona.gazeley responded  · 

I am closing this request as it’s now six years old. If anyone is experiencing similar issues on the latest version of SQL Source Control then please feel free to open a new request or support call.

Show previous admin responses (1)

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Jack commented  ·   ·  Report

    Adjust default polling settings that use a large amount of cpu through queries to tempdb.

    To fix it do this:
    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

    Replace EngineOptions with this this:
    <EngineOptions version="2" type="EngineOptions">
    <DefaultTraceMinimumInterQueryTimeInMillis>0</DefaultTraceMinimumInterQueryTimeInMillis>
    <SysObjectsMinimumInterQueryTimeInMillis>0</SysObjectsMinimumInterQueryTimeInMillis>
    <SysTypesMinimumInterQueryTimeInMillis>0</SysTypesMinimumInterQueryTimeInMillis>
    <DefaultTraceMinimumRequestedInterQueryTimeInMillis>0</DefaultTraceMinimumRequestedInterQueryTimeInMillis>
    </EngineOptions>

    Once the change is made restart SSMS for the change to take effect. Now redgate will only poll when you take an action (like opening the commit changes tab in ssms).

    More Info:
    http://www.red-gate.com/MessageBoard/viewtopic.php?p=52615

  • Jason Kochel commented  ·   ·  Report

    I have this problem as well. My database has almost 6000 stored procedures, and SQL Source Control seems to struggle to manage them.

    Aside from that, this is the exact tool that I've been looking for for years!

  • hmobius commented  ·   ·  Report

    I'd like to second this. I installed v0.3.1.3 and SQL profiler instantly started registering auditing queries from SQL Source Control every few seconds. Again, I've had to uninstall the beta software so it stops thrashing our dev database. Also, SQL Source Control doesn't identify itself in SQL profiler - just that it is a Redgate Software tool.