I have a active/passive clustered SQL Server 2005 Enterprise. If the
data file becomes corrupt, I've lost my high availability and because
the database is over 200GB, a restore operation will take hours. Does
anyone have any suggestions for creating a warm stand-by in a
clustered environment? Is this even possible, since the stand-by
would
need to become the virutal server resource owner?

I've used third-party products such as WanSync HA, as well as SQL
Server replication and log shipping in the past, just never with a
cluster.

You can use database mirroring that will get you up and running in a matter
of seconds. But this solution can also suffer from issues such as human
error. for instance if a DBA issues a DELETE and forgot the WHERE clause.
This would immediately be applied to the mirror and it is as useless as the
principle in this case. Log shipping with a slight delay can give you a warm
stand by and allow you to recover form errors like that, or at least deal
with them better than in a cluster or mirror.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Curtis Morrison" <curtmorrison (AT) hotmail (DOT) com> wrote

You can use database mirroring that will get you up and running in a matter
of seconds. But this solution can also suffer from issues such as human
error. for instance if a DBA issues a DELETE and forgot the WHERE clause.
This would immediately be applied to the mirror and it is as useless as the
principle in this case. Log shipping with a slight delay can give you a warm
stand by and allow you to recover form errors like that, or at least deal
with them better than in a cluster or mirror.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Curtis Morrison" <curtmorrison (AT) hotmail (DOT) com> wrote

You can use database mirroring that will get you up and running in a matter
of seconds. But this solution can also suffer from issues such as human
error. for instance if a DBA issues a DELETE and forgot the WHERE clause.
This would immediately be applied to the mirror and it is as useless as the
principle in this case. Log shipping with a slight delay can give you a warm
stand by and allow you to recover form errors like that, or at least deal
with them better than in a cluster or mirror.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Curtis Morrison" <curtmorrison (AT) hotmail (DOT) com> wrote

You can use database mirroring that will get you up and running in a matter
of seconds. But this solution can also suffer from issues such as human
error. for instance if a DBA issues a DELETE and forgot the WHERE clause.
This would immediately be applied to the mirror and it is as useless as the
principle in this case. Log shipping with a slight delay can give you a warm
stand by and allow you to recover form errors like that, or at least deal
with them better than in a cluster or mirror.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Curtis Morrison" <curtmorrison (AT) hotmail (DOT) com> wrote

You can use database mirroring that will get you up and running in a matter
of seconds. But this solution can also suffer from issues such as human
error. for instance if a DBA issues a DELETE and forgot the WHERE clause.
This would immediately be applied to the mirror and it is as useless as the
principle in this case. Log shipping with a slight delay can give you a warm
stand by and allow you to recover form errors like that, or at least deal
with them better than in a cluster or mirror.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Curtis Morrison" <curtmorrison (AT) hotmail (DOT) com> wrote

You can use database mirroring that will get you up and running in a matter
of seconds. But this solution can also suffer from issues such as human
error. for instance if a DBA issues a DELETE and forgot the WHERE clause.
This would immediately be applied to the mirror and it is as useless as the
principle in this case. Log shipping with a slight delay can give you a warm
stand by and allow you to recover form errors like that, or at least deal
with them better than in a cluster or mirror.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Curtis Morrison" <curtmorrison (AT) hotmail (DOT) com> wrote

You can use database mirroring that will get you up and running in a matter
of seconds. But this solution can also suffer from issues such as human
error. for instance if a DBA issues a DELETE and forgot the WHERE clause.
This would immediately be applied to the mirror and it is as useless as the
principle in this case. Log shipping with a slight delay can give you a warm
stand by and allow you to recover form errors like that, or at least deal
with them better than in a cluster or mirror.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Curtis Morrison" <curtmorrison (AT) hotmail (DOT) com> wrote

You can use database mirroring that will get you up and running in a matter
of seconds. But this solution can also suffer from issues such as human
error. for instance if a DBA issues a DELETE and forgot the WHERE clause.
This would immediately be applied to the mirror and it is as useless as the
principle in this case. Log shipping with a slight delay can give you a warm
stand by and allow you to recover form errors like that, or at least deal
with them better than in a cluster or mirror.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Curtis Morrison" <curtmorrison (AT) hotmail (DOT) com> wrote

You can use database mirroring that will get you up and running in a matter
of seconds. But this solution can also suffer from issues such as human
error. for instance if a DBA issues a DELETE and forgot the WHERE clause.
This would immediately be applied to the mirror and it is as useless as the
principle in this case. Log shipping with a slight delay can give you a warm
stand by and allow you to recover form errors like that, or at least deal
with them better than in a cluster or mirror.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Curtis Morrison" <curtmorrison (AT) hotmail (DOT) com> wrote