Monthly SQL Crashes

  • You will need to apply an hot fix. It will be in next service pack. The hot fix is Update package 4 for Service Pack 2. This will bring you to build 3215. The KB article for this is 941450. And the bug # is 50001279. You will have to contact Microsoft put out the patch for you.

  • Minor point: I thought CU4 was build 3200 and CU5 (which you had to explicitly request last time I checked) was 3215. Still if the bug addresses the issue (I didn't actually check that out) may not have a choice - that is the first thing PSS will make you do anyway I bet.

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • fwiw it searches for startup procedures...

    ... Are there startup procs ?

    What kind of stuff do they perform ?

    If I'm correct the $300 PSS is refunded if it is confirmd as a bug:unsure:

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • I just had the same issue, Had to do lock pages in memory (918483).

    Fixed the message i had

  • I've just setup a new SQL box. Win2K3 (x64) SP2 with SQL2005 - nothing else on it - didn't show up any errors untill I put SQL SP2 on it and then it started giving me the "significant portion has been paged out" error. I followed the advice in KB918483 and rebooted, but it's still doing it. I've even tried changing the config of Windows so that it has no physical paging file to use anymore and it still comes up with the error. It's got to be an SP2 "undocumented feature" 😉

  • SP2 by itself is a bad place to be. I recommend applying at least CU4, if not 5 or 6. The paging out can be caused by a NUMBER of other things tho - completely unrelated to sql server. Maybe time to call Microsoft PSS.

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • Make sure you did the lock pages with the SQL Server account that runs the sql

    and on SQL its self set the Memory and put in the MAX memory you have say you got 12 GIG put in say 9 GIG..not leave it as default

    Try that

  • The physcial memroy, total, available, system cahce,

    Commit Charge, total, limit, peak

    Under which permon performance object are these.

    Thanks

  • You should use SP2 or even SP2 + hot fix, if you have done it, your SQL will have the following version number :

    SP2 only : 9.0.3042,

    SP2 + hot fix : 9.0.3054

    Once you installed SP2 + hot fix, the problem will be fixed.

  • Please upgrade to SP2 + HOT FIX.

  • I paid Microsoft Support their exorbitant fee and spoke to a support person. They sent me CU4 (which brings SQL to version number 9.00.3200) and, so far, I haven't had any more problems with SQL crashing 😀 , although it still comes up with "A significant part of sql server process memory has been paged out" in the error log, but I'm just going to ignore this 😉

  • What is "CU4" ?

  • onlo (7/15/2008)


    What is "CU4" ?

    Cumulative update 4. Big collection of hotfixes since SP2. Currently the latest is cumulative update 8 (CU8)

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Stu (7/15/2008)


    although it still comes up with "A significant part of sql server process memory has been paged out" in the error log, but I'm just going to ignore this 😉

    Does the sql service account have the Lock Pages in memory privilidge?

    Basically, that message means that the OS has forced SQL's working set (or part of it) out of physical memory and to the swap file. This usually leads to very, very bad performance.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • btw the HowTo for lock pages in memory:

    See bol: "How to: Enable the Lock Pages in Memory Option (Windows)"

    http://msdn2.microsoft.com/en-us/library/ms190730.aspx

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

Viewing 15 posts - 31 through 45 (of 56 total)

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