Prev: deleting backup history
Next: Trouble with KB 970315
From: Adam Przestroga on 21 Dec 2009 15:46
Hi all,

I am in need of your help. One month ago I have upgraded my 2 node SQL
2005 x64 ENT cluster from SP2 CU1 to SP3 CU5. After this change I have
noticed that my SQL server jobs that take more than 60 minutes keep
failing on me (not even internal jobs such as update statistics, work).
Moreover, the cluster seems to run much heavier than on SP2 in terms of
CPU usage (in the past average CPU usage was around 20-30% on SP2, and
now it runs on average around 50-60% on SP3), though no configuration
changes have been made to it, besides the SP3 with CU5.

Every now and then I am seeing SQL server service restarts, as well.
This was not the case on SP2 CU1.

As I wrote earlier, my SQL cluster is configured as follows:
2x Windows 2003 Enterprise x64
SQL server 2005 Enterprise x64

Any advice on what could be causing this is greatly appreciated.

Regards,
AP
From: Adam Przestroga on 22 Dec 2009 11:32
Geoff N. Hiten wrote:
> See if this helps:
>
> http://support.microsoft.com/kb/943525
>
> The symptoms are not a perfect match, but it sounds close and ay be
> related.
>
Geoff,

Thanks for your input. Indeed I had to tweak these settings in the past
prior to installation of CU3 for SP2. I recall that the SQL server
agents would not start otherwise. However, this time I seem to be facing
a bit different issue as the agents are starting just fine, but on
random occasion my jobs fail not too mention almost doubled CPU usage on
the server throughout a business day.

Per the below article, we have modified both cluster nodes as indicated
below, prior to installation of CU3 for SP2: (ID: 943525:
http://support.microsoft.com/default.aspx?scid=kb;en-us;943525&sd=rss&spid=2855):

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb
- added "ProtectionPolicy" DWORD and set its value to 1
- added "MasterKeyLegacyCompliance" DWORD and set its value to 1
- deleted the following folder C:\Documents and
Settings\SQLAgentAccount\Application Data\Microsoft\Protect\SQLAgentSID

I can see this directory again, and thus wonder whether it has been
automatically re-created during SP2 CU3 or later SP3 CU5 deployment and
should be killed or left as is.

Thanks,
AP
 | 
Pages: 1
Prev: deleting backup history
Next: Trouble with KB 970315