all groups > sql server replication > december 2003 >
You're in the

sql server replication

group:

Logshipping AND replication overdoing it?


Logshipping AND replication overdoing it? hansje
12/5/2003 6:41:57 AM
sql server replication: Hi there,
Every now and then I read about a setup of transactional replication AND
logshipping. I wonder why you would want both? Any benefits I'm
overlooking? I would think either option would so.
Also, what would be the more advisable option to keep a warm standy
backup, transactional replication or logshipping?

Tnx,

Hans Brouwer

*** Sent via Developersdex http://www.developersdex.com ***
Logshipping AND replication overdoing it? Allan Hirt
12/5/2003 7:05:33 AM
They have different uses. Log shipping is the best way to
set up a warm standby. Transactional replication is great
when you have a subset of data you need to make absolutely
available elsewhere (in HA thinking, not general
replication stuff), but if you need you're whole DB, log
shipping. It is the most common thing to do.

Some may need both protection.
[quoted text, click to view]
Logshipping AND replication overdoing it? chris
12/5/2003 1:58:08 PM
My setup;

Me- Publisher
Client- Subscriber

I log ship the Publication DB to another box in case the
Publisher goes down.

[quoted text, click to view]
Re: Logshipping AND replication overdoing it? hansje
12/8/2003 2:41:13 AM
Tnx for the response, fellows.
Alan, you state logshipping is the thing to do when needing a warm
standby. I was thinking continuous transactional replication would be
better: the subscriberdb is practically the same as the publishing db.
When using logshipping say every half hour, the db's are not
synchronized. So why would you prefer logshipping, or why would it be
the common thing to do?

Tnx,

Hans Brouwer

*** Sent via Developersdex http://www.developersdex.com ***
Logshipping AND replication overdoing it? Joshua Lakin
12/12/2003 12:27:25 PM
I am acutally in the process a setting up an environment
that uses both just for this purpose. Replication (both
transactional and merge) takes place between the "master"
server and the "locational" servers. Log shipping takes
place between the "master" and the warm standby. I am
also log shipping the distribution database. My question
is: is it necessary to log ship the distribution database
(and if I did how would I use it to make sure the warm
standby is in synch with the locational servers). Also,
how do I (re)establish replication with the warm standby
once its promoted to an active server?
[quoted text, click to view]
AddThis Social Bookmark Button