Post reply

SQL2000 SP 4 performance issues

  • August 1, 2006 at 6:42 am

    #114825

    Hi there

    Is there anyone else who is experiencing performance issues after the installation of SP 4? It causes me to reboot my server every 4 days. I've already moved the databases locally to eliminate the SAN, and I'm having the same performance issues.

    The rollup to SP 4 made the performance worse and we had to uninstall.

    We used to run SP 3a, but the server crashed and we did not have the password to the extract. According to Microsoft it was only valid for 7 days in any way, so we were forced to install SP 4.

    Any ideas welcome, I'm getting desperate.

  • August 1, 2006 at 7:04 am

    #652571

    We have not experienced any performance issues after SP4. What is the possible bottleneck that you are experiencing? Perfmon comments etc?

  • August 2, 2006 at 1:35 am

    #652738

    Well, sqlserver.exe takes up 98% of CPU usage, The disc write and reads are extremely high 4000 plus, memory is normal, nothing else runs on that server. I even removed backup exec. It is as if the cache gets full after 4 days, and only a reboot clears it out. I've had 2 SQL specialists to run traces etc and they could not find anything. I really don't know what to do anymore.

  • August 2, 2006 at 1:51 am

    #652742

    Really interesting. I found this blog via int. Check if it's yours or not. I'll keep looking an eye on that and maybe others in this forum know another think that could help you.

    http://blogs.msdn.com/mssqlisv/archive/2006/05/18/601287.aspx

    Cheers,

    Zubeyir

  • August 2, 2006 at 2:04 am

    #652750

    By the way, is your box's RAM is higher than 2 Gigs? Then you need to apply another patch (http://support.microsoft.com/default.aspx?kbid=899761) otherwise you will not able to use full of the memory.

    Zubeyir

  • August 2, 2006 at 2:29 am

    #652754

    Thank you Zubeyir

  • August 2, 2006 at 8:07 am

    #652819

    I had the same problem with sp3 and in the end I had to write a scheduled task to stop and restart the sqlserver service at midnight everyday.

    Maybe stopping and restarting the database engine will save you having to reboot the whole server every 4 days although it's certainly not an ideal solution.

  • August 2, 2006 at 9:39 am

    #652858

    I seem to recall that we had performance issues when we installed SP4. Never had a satisfactory answer, but discovered that it was largely due to the way SP4 was interpreting our SQL commands and views, causing the execution plan to multiply out of all proportion in comparison to pre-upgrade. Ended up re-writing most of our Views and/or ODBC reports - perhaps not a bad thing anyway as some of them were a little amateur, particularly in relation to table joins and unions.

  • August 2, 2006 at 2:44 pm

    #652941

    Did you update statistics with full scan or run dbcc dbreindex?...

  • August 3, 2006 at 5:04 am

    #653033

    A difference between SP3 & SP4 is that SP4 doesn't always convert the variable to the matching datatype of the table column and might choose to convert all rows to the datatype of your variable instead, resulting in a scan instead of a seek.

  • August 7, 2006 at 2:11 am

    #653531

    Thank you for all the advice. After applying http://support.microsoft.com/default.aspx?kbid=899761 my SQL has been running for 8 days without any issues. Thank you.

  • August 7, 2006 at 2:34 am

    #653533

    Enjoy it 

    Zubeyir

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply