Keeping SQL up 24/7

Hi all,
I have been asked to propose a production system whereby a SQL server
machine can be up 7/24.
My question is, how do you keep a production box up 7/24 when you need to
add the OS or SQL patches to it?
Do you need to have 2 boxes, and somehow switch between the to for this
maint. Any advice would be helpful.
Thanks in advance.
TomIf you have no time for maintenance, you may need to look
into Clustering or at least Replication.
>--Original Message--
>Hi all,
>I have been asked to propose a production system whereby
a SQL server
>machine can be up 7/24.
>My question is, how do you keep a production box up 7/24
when you need to
>add the OS or SQL patches to it?
>Do you need to have 2 boxes, and somehow switch between
the to for this
>maint. Any advice would be helpful.
>Thanks in advance.
>Tom
>
>.
>|||I don't think replication, in general, would help reducing the potential
down time caused by applying OS/SQL patches.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"chris" <chris@.NoEmail.com> wrote in message
news:0d1d01c38855$c6b404b0$a101280a@.phx.gbl...
> If you have no time for maintenance, you may need to look
> into Clustering or at least Replication.
> >--Original Message--
> >Hi all,
> >
> >I have been asked to propose a production system whereby
> a SQL server
> >machine can be up 7/24.
> >My question is, how do you keep a production box up 7/24
> when you need to
> >add the OS or SQL patches to it?
> >Do you need to have 2 boxes, and somehow switch between
> the to for this
> >maint. Any advice would be helpful.
> >
> >Thanks in advance.
> >Tom
> >
> >
> >
> >.
> >