Results 1 to 10 of 10
  1. #1
    Join Date
    Mar 2004
    Posts
    99

    Unanswered: kb934459 has anyone applied this post sp2 hotfix??

    I'm running sql server 2005 servicepack 2 build 3042 (32bit)

    has anyone had any problems with this hotfix????

    http://support.microsoft.com/kb/934459

  2. #2
    Join Date
    Jan 2004
    Location
    In a large office with bad lighting
    Posts
    1,040
    Wasn't 3052 the bad release of sp2? I'vfe got 3054 on 3 boxes and no issues with them.

    -- This is all just a Figment of my Imagination --

  3. #3
    Join Date
    Mar 2004
    Posts
    99
    How do I patch up to 3054?


    I am having such a time trying to figure out which cummulative hotfix to apply. I applied the hotfix mentioned in my original post and brought my release up to 9.0.3159 - now I read somewhere that this might not be a stable release??? Can you suggest what level or release should I patch my 9.0.3042 Production box to???? and how do I find it?
    Last edited by jpotucek; 08-29-07 at 09:19.

  4. #4
    Join Date
    Jan 2004
    Location
    In a large office with bad lighting
    Posts
    1,040
    Here' are links that describe the issue:
    http://support.microsoft.com/kb/933508 and
    http://www.mssqltips.com/tip.asp?tip=1195

    After M$oft issued the first sp2, they pulled it down for a short while then put a corrected version up on the web site. you should be able to go here and get the latest sp2:
    http://support.microsoft.com/kb/913089

    -- This is all just a Figment of my Imagination --

  5. #5
    Join Date
    Mar 2004
    Posts
    99
    Thanks for all your help Tom. Looks like I'll have to install the update to SP2 mentioned in KB933508 because I have the old one - version 9.00.3042.00

    Once I do that. can you tell me how to find the latest post sp2 hotfix???

  6. #6
    Join Date
    Jan 2004
    Location
    In a large office with bad lighting
    Posts
    1,040
    Hotfixes are usually handled by Microsoft PSM on a per case basis. Many times they require a password to open. You will have to contact Microsoft, which means being prepared to pay for the incident, but if the problem is a M$oft issue, they will not charge you for the hotfix.

    -- This is all just a Figment of my Imagination --

  7. #7
    Join Date
    Mar 2004
    Posts
    99
    I did not know that. I thought that if someone opened an issue that they fixed with a hotfix - they then made it available to everyone.

  8. #8
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    Provided Answers: 54
    Microsoft does not release hotfixes because they are often very, very specific and only fix one part of a larger problem. The hotfixes do get analyzed and carried forward into service packs (SPs), but in a very different way that has much more design and QA work than a hotfix gets.

    Hotfixes are intended to be "one off" solutions to a specific problem for a specific customer. Hotfixes generally should not be shared or applied unless there is a specific, critical need.

    -PatP

  9. #9
    Join Date
    Dec 2002
    Posts
    1,245
    At http://www.sqlsecurity.com, they maintain a (pretty current) list of SQL patches and hot fixes.

    The ones that are marked "PSS Only" are not intended to be made publicly available. They are available only by calling MS support and getting (from them) a link to the hotfix (which is zipped and protected by a password which changes every 7 days).

    There are, however, some hotfixes which are NOT password protected and may be downloaded without calling M$.

    Regards,

    hmscott

    PS. I should note that calling MS for any of these hotfixes does not cost anything.
    Have you hugged your backup today?

  10. #10
    Join Date
    Mar 2004
    Posts
    99
    Great info. Thank you for everything!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •