Replication Options -- sql server replication

Mrpush
4/24/2007 12:12:02 PM

Hello,

New to SQL Replication.

Have SQL 2000 and wanted to replicate my business & core databases to a
server at another site to increase availability.

Is SQL replication able to keep my business application running without end
users ever knowing that one of the serves went down or are there manual steps
to be taken to get end users reconnected if I lose or down one of the SQL
servers?

Which type of replication is best suited for this?

Also, my WAN bandwidth is around 768 K upto about 1 M max betweeen sites.

Will these speeds support SQL replication ok?

Thanks much,

Mark

Paul Ibison
4/24/2007 10:37:10 PM

Hi Mark and welcome to the group :)
For DR, you might want to look at log shipping. In SQL Server 2005 there is
database mirroring which is similar but offers automatic failover that you
mention, but this isn't there in log shipping and there willbe some final
tweaking to get things ready, and then you'll need to point the client apps
at the new server. Have a look here for a little more info:
http://www.replicationanswers.com/Standby.asp, and BOL for the final steps
needed in log shipping to bring up the standby server.
HTH,
Paul Ibison

Mrpush
4/25/2007 6:24:00 AM

Paul,

Thanks for the info. Seems I'm a bit limited. I read that log shipping
requires SQL 2000 Enterprise, and I don't have it!

I quess one of the forms of Replication or an upgrade to SQL 2005 may be my
only options.

Thanks much,

Mark

[quoted text, click to view]

Mrpush
4/25/2007 7:36:03 AM

Paul,

Could I just do a manual database transfer of a full backup every night to
the standby server, and just send a copy of the transaction logs to the
standby server say every hour without using Replication?

Any reason not to do it this way?

Thanks,

Mark

[quoted text, click to view]

Paul Ibison
4/25/2007 8:16:02 AM

You can do log shipping in other editions, but it is a bit more difficult as
it isn't out of the box. At the end of the day you just need jobs to back up
logs on one server, copy to a network share on another server then a third
job to restore there (no recovery). Procedures to make this setup are on the
SQL Server resource kit and on some websites so you can use someone else's
scripts if you don't want to make your own.
Cheers,

Paul Ibison
4/25/2007 8:32:02 AM

Exactly - you can roll your own log shipping. Just be sure to restore using
NO RECOVERY and the rest is pretty straightforward.
Cheers,

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server replication

sql server replication : Replication Options