Where I work our MS production systems have to get rebooted weekly or they
automatically reboot themselves.( or become so unusable/unstable that you
have to turn the machine physically off.) I have never seen an MS
production server with uptime over a couple of months max and usually get
rebooted weekly as a preventative measure. (often on the recommendation of
MS support) We did not get hit with the slammer virus, but MS and Siebel
did. Siebel's support site was down for several days because of it. (They
had made a pact with MS to use their .net tools and this burned them)
with family. Remove the negative part, keep the minus sign. You can figure
> > > Bullshit. What exactly would you call robust?
> > > Multi-year uptimes with no unscheduled downtimes?
> > > I've got several SQL Servers that would meet that bill.
> > I have worked with several unix systems that have not
> > been powered down or rebooted for years using databases.
> > Are you saying you have M$ SQL servers that have not been
> > powered down or rebooted for years? Or are you saying
> > that because you choose to reboot it - that it does not count
> > as down time?
> I had replied privately, but I'll reply for the benefit of the group, but
> yes, I've had several machines with uptimes over a year.
> The only reason 3-4 of them were rebooted recently is they were moved 6-7
> Oh, and none of them were hit by Slammer.
> > If so, that would be the first time I have ever heard
> > of any M$ system being up for years.
> It can be done. One reason I've also seen it NOT done is some NT admins
> so USED to rebooting that they will reboot at the slightest sign of a
> problem, rather than debug it with the machine up.
> > --
> > Doug Royer | http://INET-Consulting.com
> > -------------------------------|-----------------------------
> > Doug AT Royer.com | Office: (208)612-INET
> > http://Royer.com/People/Doug | Fax: (866)594-8574
> > | Cell: (208)520-4044
> > We Do Standards - You Need Standards