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

Mirroring and the Log File Expand / Collapse
Author
Message
Posted Friday, February 22, 2013 8:04 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, August 5, 2014 6:28 AM
Points: 22, Visits: 200
How does SQL get the logs that it will transfer to mirrored server? Does SQL "scrape" the log files for unsent logs? Are the unsent logs marked or stored seperately?

We have 30 databases that we want to mirror. Over the past few weeks, we have been mirroring these databases, all in asynchronous mode. One day, we mirrored the 10 remaining databases, some of the smallest and least transactional databases we have. At that point, we started seeing odd performance. We are getting timeouts from stored procedures that never timeout. We are experiencing higher than normal signal wait times; however, we are not experiencing higher than normal blocking. The only thing we have noticed is that before the signal wait times jump, our writelog waits increase. We are wondering if the log file is being locked while SQL is checking for logs that need to be sent to the mirror.
Post #1423080
Posted Friday, February 22, 2013 8:11 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 @ 3:38 AM
Points: 42,753, Visits: 35,841
No to scraping the log file, no to separate locations.
The log records are written to the log file and sent to the mirror at the time they're created. No file reading, no file locks.

30 DBs is quite a lot to be mirroring on a single instance, that's going to be a fair bit of overhead on the principal.




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 #1423083
Posted Friday, February 22, 2013 8:26 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, August 5, 2014 6:28 AM
Points: 22, Visits: 200
Thank you. Do you have any thoughts on why we would be seeing higher writelogs waits just before the signal waits get high, even though there is little to no blocking happening?
Post #1423097
Posted Friday, February 22, 2013 9:15 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 @ 3:38 AM
Points: 42,753, Visits: 35,841
Check your IO subsystem? Could also be that CPU is being used elsewhere and the writing to the log file is getting delayed because the CPU is trying to process something else, probably the mirroring transmissions


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 #1423121
Posted Friday, February 22, 2013 10:01 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, August 5, 2014 6:28 AM
Points: 22, Visits: 200
Thank you.
Post #1423144
Posted Tuesday, February 26, 2013 9:00 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Tuesday, August 12, 2014 4:51 PM
Points: 7,097, Visits: 12,597
If you had a large CPU workload in the first place the worker threads used by the additional mirroring sessions (not negotiable) could have pushed you beyond a tipping point on your instance. I agree, 30 databases is quite a few to mirror from one instance, but there are some things you can do to tune your instance besides adding more CPUs.

Mirroring a Large Number of Databases in a Single SQL Server Instance


__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Post #1424316
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse