July 28, 2004 at 7:42 pm
Hello all,
I need to reboot my SQL environment because of a Windows security patch. I have one MSX and two TSX servers. I've been hunting around for information on a recommended procedure for rebooting an MSX/TSX environment to no avail (maybe I'm looking for the wrong thing). Anyway, does anyone have a recommendation on how to perform server reboots in this kind of environment?
Do I need to reboot in a specific order (i.e. TSX's first, then MSX)? Do I need to defect the targets prior to rebooting? Do I need to re-sync after all machines come up? Any help is appreciated. Thanks!
James
James Stover, McDBA
July 30, 2004 at 9:28 am
It makes no difference.
I have 20 odd TSX servers and I've had my MSX server (an old one for DBA use only) down for hours at a time.
The TSX servers will just carry on doing their thing, but just logging an error in the SQLAgent log everytime it attempts to poll the MSX server.
No defections/re-enlistments ore re-synchs necessary
You can even play with the MSX job target servers and they'll queue up faithfully while your TSX is re-booting etc. Only if do major re-jigging of your MSX job targeting will a re-synch be necessary.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply