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

Stairway to Transaction Log Management in SQL Server, Level 9: Monitoring the Transaction Log Expand / Collapse
Author
Message
Posted Wednesday, April 24, 2013 12:00 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 1:43 PM
Points: 40,411, Visits: 36,861
Comments posted to this topic are about the item Stairway to Transaction Log Management in SQL Server, Level 9: Monitoring the Transaction Log


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1445773
Posted Wednesday, April 24, 2013 8:19 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Yesterday @ 4:46 AM
Points: 82, Visits: 1,014
I work on a busy, highly transactional database server running SQL Server 2008 R2. There were performance problems last year which were wrongly attributed to SAN replication. Replication was switched off, the problems persisted, application changes were made which resolved the problems then Syncronous SAN Replication was switched back on.

WRITE_LOG operations, as a percentage of overall wait time statistics, went from 20% to 50% as a result of re-enabling SAN replication. There's a battery backed write cache on the SAN but Disk Queue Lengths are up a bit and other PERFMON counters show a negative impact. The system is coping with SAN Replication on but there is definitely a cost associated with it, mainly to log writes.

This article - http://blogs.msdn.com/b/psssql/archive/2013/04/22/how-it-works-always-on-when-is-my-secondary-failover-ready.aspx
explains how 'Log Blocks' are replicated in AlwaysOn artictures, rather than discreet transactions, to maintain a syncronized state.

We are about to implement a new (again highly transactional) system using SQL Server 2012 AlwaysOn with syncronous replica's at a DR site, local clusters at each site using shared storage, AlwaysOn data mirroring to the DR site instead of SAN replication.

This and the PSS article compliment each other for certain architectures, both articles are great.
Thanks

Post #1446006
Posted Wednesday, April 24, 2013 4:05 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 1:43 PM
Points: 40,411, Visits: 36,861
Paul Brewer (4/24/2013)
WRITE_LOG operations, as a percentage of overall wait time statistics, went from 20% to 50% as a result of re-enabling SAN replication. There's a battery backed write cache on the SAN but Disk Queue Lengths are up a bit and other PERFMON counters show a negative impact. The system is coping with SAN Replication on but there is definitely a cost associated with it, mainly to log writes.


I've had similar experiences



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1446250
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse