June 13, 2008 at 8:19 am
I set replication up in SQL Server 2005 from server A to server B, but have a question.
Is server B to be a receiver, as in a "clustering" mode, if server A is shut down? Or are the transactions going to store on server A until it is back online? Essentially, is server B only a dumb recipient from server A or does it stand alone if server A is not there?
Thanks!
June 13, 2008 at 8:38 am
You configured the replication, so this will depend on the options you have selected.
Some replication is one-way - snapshot replication or log-shipping for example. Merge replication is two-way. Transactional replication can be either - if you have your subscribers configured as updatable subscribers.
As far as using replication as a failover solution, that is hit or miss. It was not designed as a real failover DR solution - that is what clustering and mirroring are for.
June 13, 2008 at 9:04 am
Thank you. It is transactional.
Is there an easy way to find out if the publisher/subscribers are updateable? (I was following a checklist from the vendor and cannot find a reference to that ...)
June 13, 2008 at 9:19 am
Ok - BOL helped there. I found in the properties box under subscription that it is a pull subscription and updatable is FALSE. I'll dig through that more to see if it answers my questions.
Thank you!
June 13, 2008 at 1:00 pm
In 2005 you could setup peer-to-peer which is also bi-directional.
There are (as with everything) tradeoffs for each replication type
* Noel
June 13, 2008 at 1:10 pm
Thank you all -- I wound up discussing with the vendor and they sent me a whole set of DR stuff ... supposedly the world will survive in the current setup.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply