SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Stairway to Transaction Log Management in SQL Server, Level 9: Monitoring the Transaction Log


Stairway to Transaction Log Management in SQL Server, Level 9: Monitoring the Transaction Log

Author
Message
GilaMonster
GilaMonster
SSC Guru
SSC Guru (414K reputation)SSC Guru (414K reputation)SSC Guru (414K reputation)SSC Guru (414K reputation)SSC Guru (414K reputation)SSC Guru (414K reputation)SSC Guru (414K reputation)SSC Guru (414K reputation)

Group: General Forum Members
Points: 414266 Visits: 47128
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, MVP, M.Sc (Comp Sci)
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


Paul Brewer
Paul Brewer
SSC Eights!
SSC Eights! (979 reputation)SSC Eights! (979 reputation)SSC Eights! (979 reputation)SSC Eights! (979 reputation)SSC Eights! (979 reputation)SSC Eights! (979 reputation)SSC Eights! (979 reputation)SSC Eights! (979 reputation)

Group: General Forum Members
Points: 979 Visits: 1333
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
GilaMonster
GilaMonster
SSC Guru
SSC Guru (414K reputation)SSC Guru (414K reputation)SSC Guru (414K reputation)SSC Guru (414K reputation)SSC Guru (414K reputation)SSC Guru (414K reputation)SSC Guru (414K reputation)SSC Guru (414K reputation)

Group: General Forum Members
Points: 414266 Visits: 47128
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, MVP, M.Sc (Comp Sci)
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


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search