InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 26 May 2013 00:22:38 GMT20http://www.sqlservercentral.com/Forums/Topic1423080-1549-1.aspxIf 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.[u][url=http://sqlcat.com/sqlcat/b/technicalnotes/archive/2010/02/10/mirroring-a-large-number-of-databases-in-a-single-sql-server-instance.aspx]Mirroring a Large Number of Databases in a Single SQL Server Instance[/url][/u]Tue, 26 Feb 2013 21:00:41 GMTopc.threehttp://www.sqlservercentral.com/Forums/Topic1423080-1549-1.aspxThank you.Fri, 22 Feb 2013 10:01:20 GMTsudonjnhttp://www.sqlservercentral.com/Forums/Topic1423080-1549-1.aspxCheck 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 transmissionsFri, 22 Feb 2013 09:15:53 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1423080-1549-1.aspxThank 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?Fri, 22 Feb 2013 08:26:38 GMTsudonjnhttp://www.sqlservercentral.com/Forums/Topic1423080-1549-1.aspxNo 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.Fri, 22 Feb 2013 08:11:15 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1423080-1549-1.aspxHow 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.Fri, 22 Feb 2013 08:04:24 GMTsudonjn