emergent help with sp3

Question

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

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

Scott D. Jacobson SSCertifiable Points: 6149 More actions · Answer 1

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

sqlfriend SSC Guru Points: 52781 More actions · Answer 2

I found solution from here.

Thanks

sqlfriend SSC Guru Points: 52781 More actions · Answer 3

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

Scott D. Jacobson SSCertifiable Points: 6149 More actions · Answer 4

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.