Post reply

SP

  • April 1, 2009 at 2:47 pm

    #208133

    Hi all,

    I ran select @@version to find the service pack version for 2005 SQL server. I got the result that the SP is Service Pack 2.

    But if I run

    SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

    I get Service Pack as RTM..

    Is it different? We are planning on installing SP3.

    Thank you

  • April 1, 2009 at 2:52 pm

    #970245

    [font="Verdana"]That's puzzling. The ProductLevel should give your service pack.

    Either way, why does it matter? Service Pack 3 includes all of the previous service packs. So once you apply it, you can be assured that you will be up to SP3.

    Also, I'm trying to figure out how this bears some relationship to Oracle...

    [/font]

  • April 1, 2009 at 3:13 pm

    #970255

    Thanks. I'm sorry I posted in the wrong forum. I work with Oracle mostly and recently started working with SQL Server.

    To apply the SP3, is there any specifc steps I need to follow or is there a documentation for this?

    Thanks a lot for your help again.

  • April 1, 2009 at 3:17 pm

    #970262

    [font="Verdana"]I suspect if you hit the FAQ (frequently asked questions) for this site, there will be some information on applying service packs.

    You can download the instructions for applying the service pack separately from the Microsoft site. They also come as part of the service pack.

    So my suggestion would be to go to the Microsoft site, find the service pack, and download the instructions. They are usually fairly simple to apply (unpack, run), except if you have a clustered environment.

    Good luck! And if you get stuck, you know where to come. 😀

    [/font]

  • April 1, 2009 at 3:38 pm

    #970284

    psangeetha (4/1/2009)

    I ran select @@version to find the service pack version for 2005 SQL server. I got the result that the SP is Service Pack 2.

    I'm guessing that you saw a reference to Service Pack 2 right at the end. If so, that's not SQL, that's the patch level of the OS. For eg, on my server @@version returns

    Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

    The portion "Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)" refers to SQL and tells me that this is SQL 2005 RTM.

    The portion "Windows NT 5.2 (Build 3790: Service Pack 2)" tells me that the OS is Windows NT 5.2 (Windows Server 2003) Service pack 2

    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

  • April 1, 2009 at 3:46 pm

    #970293

    [font="Verdana"]You know Gail, I bet you're right!

    BTW, applying service packs to Oracle databases is far far more complex than applying service packs to SQL Server. So this explains the level of trepidation.

    That doesn't mean that a service pack should be applied blindly in the SQL Server world. As per usual, test the results of the service pack against your applications. It's not often that a service pack will break applications, but it can happen.

    [/font]

  • April 1, 2009 at 6:04 pm

    #970332

    Thanks much, Bruce and Gail.

    You are right. It did show the SP2 right at the end.

    Microsoft SQL Server 2005 - 9.00.1406.00 (X64) Mar 3 2007 19:53:24 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

    So it should be the Windows SP2 and I guess the SQL server's Service Pack is RTM. Not sure what it is.

    OS is Windows 2003 R2 Standard x64 Edition Service Pack 2. I'm downloading the SP3 for SQL server SQLServer2005SP3-KB955706-x64-ENU.exe. Hope it is the correct file.

    We are trying to certify our application with SP3 on SQL server. I know it will improve performance and will work much better, but are there any issues that I should be concerned about after applying SP3? Is there a way to rollback incase our application doesnt support SP3?

    Thanks again for your help

  • April 2, 2009 at 7:47 am

    #970685

    I just read the documentation, I see I should be able to uninstall the service pack if required.

    Just one doubt, Since our server has Service Pack 2 on Windows 2003 R2 x64 bit, is it okay to install SP3 for SQL server?

    Thanks a lot.

  • April 2, 2009 at 8:01 am

    #970710

    OS service packs and application service packs are completely unrelated and don't affect one another

    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

  • April 2, 2009 at 1:31 pm

    #971035

    [font="Verdana"]I remember that scatter-gather got added to Windows 2000 (?) via a service pack at some point, and there was a service pack of SQL Server that came along that required that service pack for windows. Or was that NT 4 days? Erk.

    I think something similar happened when SQL Server 2005 came out and required a whole bunch of .Net prerequisites. From memory they were shipped along with SQL Server though.

    But yes, Windows is stable enough as a server platform now that SQL Server service packs are independent of Windows service packs. 😀

    [/font]

  • April 27, 2009 at 11:19 am

    #984523

    I've installed SP3 for SQL server and now when i run SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition') I get Productlevel as SP3.

    Are there any specific differences/enhancements/updates from RTM -> SP3 ? We would like to do some high level testing for our application with SP3 and the team would like to know what changes involved in the SP install, so they can do the testing in that area.

    I checked a few links, I didnt get any help yet.

    Please give me your suggestions. Thanks a lot for all your help

  • April 27, 2009 at 11:29 am

    #984532

    Fixes in SP3 - http://support.microsoft.com/?kbid=955706

    Fixes in SP2 - http://support.microsoft.com/?kbid=921896

    Fixes in SP1 - http://support.microsoft.com/?kbid=913090

    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

  • April 27, 2009 at 12:05 pm

    #984553

    psangeetha (4/27/2009)

    I've installed SP3 for SQL server and now when i run SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition') I get Productlevel as SP3.

    :w00t: shocking!

    ... sorry, couldn't help myself 😀

    _____________________________________
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at Amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

  • April 27, 2009 at 12:07 pm

    #984554

    haha, Lol

    Thanks Gail.

  • April 27, 2009 at 3:18 pm

    #984722

    Sorry, I have another doubt. Is it required to rebuild the views after the SP3 install??

    We are having some issues on a few programs that runs a view.

    Thanks again.

Viewing 15 posts - 1 through 15 (of 15 total)

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