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] >-----Original Message-----
>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.
>>-----Original Message-----
>>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 >***
>>Don't just participate in USENET...get rewarded for it!
>>.
>>
>.