Method of providing standby

hi all, I am considering what should be the best way of implementing
the following requirement.

I've got a SQL2K production server. Now I've got another machine as the
standby machine for this server
so I'm thinking what method should I be using for this.

Should I be using log shipping or Replication? Or if it's replication,
what kind of replications
should it be?

I am thinking maybe snapshot replication can be just fine, right?Hi

Log shipping is the least intrusive as it requires no table changes.

Replication, IMHO, is a bad form of DR as you can not be guaranteed the time
lag between the primary and secondary being updated.

Regards
----------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@.epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"New MSSQL DBA" <boscong88@.gmail.com> wrote in message
news:1121049035.357996.61730@.g49g2000cwa.googlegro ups.com...
> hi all, I am considering what should be the best way of implementing
> the following requirement.
> I've got a SQL2K production server. Now I've got another machine as the
> standby machine for this server
> so I'm thinking what method should I be using for this.
> Should I be using log shipping or Replication? Or if it's replication,
> what kind of replications
> should it be?
> I am thinking maybe snapshot replication can be just fine, right?|||After researching a bit, I agree with your suggestion.

But the problem is, the SQL2K is just a standard edition and can we
implement log shipping on it? I know log shipping is available only in
EE but is there a way to get it works in standard edition?|||I seem to remember that there's a trimmed down log shipping tool for
Standard Edition in the MSSQL Resource Kit. Or you could implement your
own solution - this article discusses MSSQL 7, but you could also apply
it to MSSQL 2000:

http://www.sql-server-performance.c...og_shipping.asp

Simon|||Thanks a lot for your help.