Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

replica of prod server Expand / Collapse
Author
Message
Posted Wednesday, January 23, 2013 5:57 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 8:28 PM
Points: 351, Visits: 1,657
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??
Post #1410519
Posted Thursday, January 24, 2013 7:53 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 8:28 PM
Points: 351, Visits: 1,657
any suggestions????
Post #1411148
Posted Thursday, January 24, 2013 11:23 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, March 14, 2014 2:19 AM
Points: 2,820, Visits: 3,916
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):

http://download.microsoft.com/download/d/9/4/d948f981-926e-40fa-a026-5bfcf076d9b9/ReplicationAndDBM.docx


-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done
Post #1411485
Posted Tuesday, January 29, 2013 3:07 PM


SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, April 15, 2014 8:28 AM
Points: 38, Visits: 431
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.
Post #1413354
Posted Wednesday, February 06, 2013 8:55 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 11:40 PM
Points: 117, Visits: 715
while restoring the database cannot be accessed in log shipping. Peer to Peer replication just works perfectly over here.
Post #1416564
Posted Friday, February 08, 2013 6:11 PM


SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, April 15, 2014 8:28 AM
Points: 38, Visits: 431
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.

Post #1417963
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse