Post reply

emergent help with sp3

  • July 17, 2012 at 12:23 pm

    #259572

    I tried to upgrade SQl server 2008 Enterprise edtion from sp1 to sp3.

    But it failed.

    How can I troubleshoot?

    Thanks

  • July 17, 2012 at 1:08 pm

    #1513828

    When you say it failed, what happened? Do you have a specific error message?

  • July 17, 2012 at 1:14 pm

    #1513830

    I found solution from here.

    Thanks

    http://social.msdn.microsoft.com/Forums/en/sqlsetupandupgrade/thread/2298ed3f-95c4-4b26-b099-2596f9639117

  • July 17, 2012 at 6:26 pm

    #1513958

    I think the update failed is because someone logged in SSMS on the server, but I tried to kill the process, it seems it cannot be killed.

    so I went ahead to update, it failed, I guess maybe the login of the SSMS hold on something and maybe some dell not got updated?

    I later asked the developer to log off, and repaired SSMS on the server, then apply the service pack again, it succeeded.

    If I have situation like this again, if I cannot reach the person, how can I log off another person's SSMS session on the server?

    Thanks

  • July 17, 2012 at 10:40 pm

    #1513993

    As with most things, "it depends". Having SSMS installed on the server is bad practice depending on your application.

    That said, sp_who or sp_who2 should tell you who is connected.

    You should absolutely disconnect all active connections before doing any updates.

Viewing 5 posts - 1 through 4 (of 4 total)

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