SQL SERVER problem on version 9.0.5057

  • Hi DBAs,

    I have installed sql server 2005 sp4 last month.today i came to office i checked all the servers.now the server RTM is 9.0.5057 but previous is 9.0.5000.i don't no how it has been changed.Is there any problem with changing with version.

    please provide the solution.

    Regards
    venkat

  • Windows update? There have been a couple patches lately.

    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
  • but how it has been changed sql server 9.0.5000 to 9.0.5057 .is there any effect.

    I got some information from C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary.txt

    Time: 07/03/2011 12:43:10.877

    KB Number: KB2494120

    OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790)

    Package Language: 1033 (ENU)

    Package Platform: x86

    Package SP Level: 4

    Package Version: 5057

    Command-line parameters specified:

    /quiet

    /allinstances

    Cluster Installation: No

    **********************************************************************************

    Prerequisites Check & Status

    SQLSupport: Passed

    **********************************************************************************

    Products Detected Language Level Patch Level Platform Edition

    SQL Server Database Services 2005 (MSSQLSERVER) ENU SP4 2005.090.5057.00 x86 STANDARD

    SQL Server Integration Services 2005 ENU SP4 9.00.5057.00 x86 STANDARD

    SQL Server Tools and Workstation Components 2005 ENU SP4 9.4.5057 x86 STANDARD

    **********************************************************************************

    Products Disqualified & Reason

    Product Reason

    **********************************************************************************

    Processes Locking Files

    Process Name Feature Type User Name PID

    **********************************************************************************

    Product Installation Status

    Product : SQL Server Database Services 2005 (MSSQLSERVER)

    Product Version (Previous): 5057

    Product Version (Final) :

    Status : Not Selected

    Log File :

    Error Number : 0

    Error Description :

    ----------------------------------------------------------------------------------

    Product : SQL Server Integration Services 2005

    Product Version (Previous): 5057

    Product Version (Final) :

    Status : Not Selected

    Log File :

    Error Number : 0

    Error Description :

    ----------------------------------------------------------------------------------

    Product : SQL Server Tools and Workstation Components 2005

    Product Version (Previous): 5057

    Product Version (Final) :

    Status : Not Selected

    Log File :

    Error Number : 0

    Error Description :

    ----------------------------------------------------------------------------------

    **********************************************************************************

    Summary

    Success

    Exit Code Returned: 0

    Regards
    venkat

  • Yes, that's what I'm saying. Windows update could have applied a SQL patch hence upping the version. Did you check? Also check the MS kb articles for that build number.

    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
  • Now i understood the concept.Thank you for the reply "Gail Shaw

    "

    Regards
    venkat

  • Hi Gail,

    Your answers are really good.

    Is there a way to check which update cause the problem and can it be rolled back. I know it happened on one of our servers and that's sitting out of load balance now.I am not in Sql Team but trying to learn these things.

    Thanks

    ImI

  • Why do you consider it a problem?

    Did you search the MS kb articles as I suggested? Or look through recently installed updates? You've got the KB number (KB2494120) so go and read the associated article.

    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

Viewing 7 posts - 1 through 6 (of 6 total)

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