January 23, 2013 at 5:57 am
Hi,
I am trying to create a replica of production server, so that we can divert some traffic. I am thinking of setting up mirroring and taking the database snapshots and making the data available for read only operations and for DR sites. Can we make the data continuously available during the snapshot process for read only operation? It's a high OLTP environment. Can snapshot replication/ Peer to Peer be used over here? We already have transactional replication in prod environment. Can we have both transactional and snapshot/peer to peer replication working together. If yes, what's the impact on prod server? We tried SAN replication but some reason the databases are going to suspect mode. Any thoughts??
January 24, 2013 at 7:53 am
any suggestions????
January 24, 2013 at 11:23 pm
This document talks about replication and database mirroring (including information on trace flag 1448 which allows the log reader to replicate changes regardless of the mirroring state):
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
January 29, 2013 at 3:07 pm
Hi,
Log shipping to a secondary server is also an option . You can query on the secondary log shipping database as well. LS is also very easy to implement.
February 6, 2013 at 8:55 am
while restoring the database cannot be accessed in log shipping. Peer to Peer replication just works perfectly over here.
February 8, 2013 at 6:11 pm
I agree with that. While restoring the transaction logs to the secondary server, the users will be disconnected from the secondary database. Although it is a good practice to setup the backup interval and copy/restore interval of the Logshipping setup same ( Eg. backup trans log every 30 mins , and restore to secondary server every 30 mins) It is not uncommon to setup the log shipping to Restore the Transaction logs only few times a day, so that users won't be kicked out of the restoring database.
Drawbacks are:
Doing so, you would not get an exact near Production copy of the database.
Your Transaction log to be restored in the secondary database will take more time across the network since there will be more transactional log files.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply