What order should I shut down and restart?

Question

What order should I shut down and restart?

Roy Ernest

SSC-Dedicated

Points: 38780
More actions
March 3, 2009 at 10:25 am

#197660

Hi All,
I have to shutdown my production Server and restart it to do some Maintenance. My production Db Server is replicated over to two Subscribers. The distributor is in a separate box as well.
The questions I have is
1. Do I have to shutdown the distributor and subscribers if I need to restart only my Production?
From what I think, I dont need to. Just need confirmation.
2. If I need to restart the distributor as well for any reason, should I first shutdown the Production, Then shutdown the distributor, restart the Distributor and then the Publisher?
Thats what I think should be followed but maybe I am wrong.
Can someone please clarify on these please?
Thanks
Roy
PS : The reason I am restarting the publisher is because I am getting "There is insufficient system memory to run this query". I tried DROPCLEANBUFFERS. No use.
-Roy

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

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

noeld SSC Guru Points: 96590 More actions · Answer 1

1. Do I have to shutdown the distributor and subscribers if I need to restart only my Production?
From what I think, I dont need to. Just need confirmation.

No Need to shutdown distributor nor subscribers

2. If I need to restart the distributor as well for any reason, should I first shutdown the Production, Then shutdown the distributor, restart the Distributor and then the Publisher?

No need for that either, just restart the box. SQL 2005 Agents are very resilient.

IF it was SQL 2000 I would tell you otherwise.

PS : The reason I am restarting the publisher is because I am getting "There is insufficient system memory to run this query". I tried DROPCLEANBUFFERS. No use.

You should verify that you are not using too much sp_OA or extended procedures with memory leaks...

Also check if you are running out of "desktop memory" (google it)...

Hope it helps

* Noel

Roy Ernest SSC-Dedicated Points: 38780 More actions · Answer 2

Thanks Noel. I will be doing the Restart late night tonight.

About the memory leak, it was actually one stupid Stored Proc that had no SET NOCOUNT ON. (I missed it when I reviewed the SP) This I had to run in the SSMS because of another small stupidity. It was writing quite a bit on Info in the Message tab. And used up all the resource. After this was run, My traces stopped working.

-Roy

noeld SSC Guru Points: 96590 More actions · Answer 3

noeld

SSC Guru

Points: 96590

March 4, 2009 at 8:31 am

#953268

glad you figure it out!

* Noel

Roy Ernest SSC-Dedicated Points: 38780 More actions · Answer 4

Hey Noel,

Just wanted to update. The server was rebooted. The Log reader was stopped since the publisher was not there. I started it back on and everything is Green now..:)

Upgraded the memory of my Baby as well. From 8 gig to 32 gig... Yippie 😀

Thanks for your advice.

-Roy

noeld SSC Guru Points: 96590 More actions · Answer 5

Roy Ernest (3/5/2009)
Hey Noel,
Just wanted to update. The server was rebooted. The Log reader was stopped since the publisher was not there. I started it back on and everything is Green now..:)
Upgraded the memory of my Baby as well. From 8 gig to 32 gig... Yippie 😀
Thanks for your advice.

NICE!

* Noel

Roy Ernest SSC-Dedicated Points: 38780 More actions · Answer 6

I did make a dump stupid mistake though... I had the perfmon up and running from my desktop for the SQl Server. And then I restarted it. Now I dont have SQL Server Perfmon counters... :crying:

-Roy