sql server 2005 - SQLSERVER mirroring VS Log shipping -
i need understanding mirroring follwoing example.
primary server in fl mirror server in germany
my application doing insert table fl system
case 1 : mirror server down -- network issue -- assume insert written transaction log on principal -- not commited disk happen if tries query fl database.will see last transaction[insert]? when sql server perform query, @ both db , tlog?.
case 2: if mirror server down 2 days. guess transation log continue grown. can explain how affect response time of appplication
case 3 : if mirror down while (week). better break mirroring. also, means have take full backup of db again in order reconfigure mirroring
you haven't specified kind of mirroring, assume high safety automatic failover
case 1 : principal in 'disconnected' state. transactions committed disk on principal, not mirror (obviously). transactions remain in 'active' part of log , not backed up. i.e. see transaction log grow , log_reuse_wait_desc column in sys.databases mirroring. fl database remain offline , in disconnected state. not able query unless use force_service_allow_data_loss
bring online @ point you've broken mirror (although principal doesn't know yet & continue hold logs)
case 2: transaction log keep growing in accordance autogrow settings. usual case autogrowing logs, have overhead everytime autogrow , potentially end lots of virtual log files. best set autogrow reasonable it's not growing in 50mb increments.
case 3: depends on how data change you've had changed compared size of full database backup need copied between sites re-init mirroring. in sql server 2008 have options log compression means can stuff more transaction down wire less bandwidth (if you're using it)
Comments
Post a Comment