SQL Server 2005 Processes SLOOOOW

sspratlensspratlen Posts: 2
edited December 6, 2010 3:14PM in SQL Source Control Previous Versions
We just implemented using SQL Source Control 1.0.1.13 on our SQL 2005 Servers. Most of our DB's use 2000 Compatability.

We found that alot of processes are running from Red Gate doing multiple drops and select constantly, causing massive slow downs.

If we close SQL Studio and restart everything is fine for a short time, then it starts running drops and select again, utilizing large chunks of CPU time.

I am seeing these in sp_who2 active to verify that it is the Red Gate processes.

Any ideas? I really like the source control functionality, but I would hate to uninstall because I cannot have it slow other processes down to a crawl.

Thanks,
Scott
· Share on Twitter

Comments

  • StephanieHerrStephanieHerr Posts: 174 Gold 1
    Hello Scott,

    Our internal reference number is SOC-1334. We will follow up with you directly via email to get some more information about your system and try to work through this issue.

    Thank you!
    Stephanie M. Herr :-)
    SQL Source Control Project Manager
    Thank you!
    Stephanie M. Herr    :-)
    Product Manager Database DevOps
    · Share on Twitter
  • BjarneCBjarneC Posts: 1
    Did you find any solution for this, as I am currently expiriencing similar behaviour ?
    /Bjarne
    · Share on Twitter
  • mamuellermamueller Posts: 1
    Hello!

    Is there any news about this issue?

    Started using the tool as well, but are also experiencing the DB Load issue, which causes problems in our Dev Environment.

    We´re using a Shared Dev DB, maybe thats the issue ?

    thx
    cheers
    · Share on Twitter
  • Chris AucklandChris Auckland Posts: 769
    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.
    &lt;?xml version="1.0" encoding="utf-16" standalone="yes"?&gt;&lt;!----&gt;&lt;EngineOptions version="2" type="EngineOptions"&gt;&lt;DefaultTraceMinimumInterQueryTimeInMillis&gt;0&lt;/DefaultTraceMinimumInterQueryTimeInMillis&gt;&lt;SysObjectsMinimumInterQueryTimeInMillis&gt;0&lt;/SysObjectsMinimumInterQueryTimeInMillis&gt;&lt;SysTypesMinimumInterQueryTimeInMillis&gt;0&lt;/SysTypesMinimumInterQueryTimeInMillis&gt;&lt;DefaultTraceMinimumRequestedInterQueryTimeInMillis&gt;0&lt;/DefaultTraceMinimumRequestedInterQueryTimeInMillis&gt;&lt;/EngineOptions&gt;

    THE v1 DEFAULT VALUES ARE:
    25000 DefaultTraceMinimumInterQueryTimeInMillis
    2500 SysObjectsMinimumInterQueryTimeInMillis
    3500 SysTypesMinimumInterQueryTimeInMillis
    5000 DefaultTraceMinimumRequestedInterQueryTimeInMillis

    I hope this helps.
    Chris
    · Share on Twitter
Sign In or Register to comment.