Friday, April 27, 2012 2:03 PM
We are using the Database mirroing in high-protection mode , we do not want to loose any data and at the same time we don't want to degrade the perfromance to very high level.
I knew that in Protection mode , it will have no loss of data and it waits for confirmation from mirrioring server and then commit that transaction on primary server. but this will create a delay for the user who is doing a workflow on the primary server.
So basically i am alloking for the figures or percenatge by how much it will get decreased and any best practices in high perfromance mode to achieve this.
Any Suggestions/Ideas will be defently helpful.
Friday, April 27, 2012 3:45 PM
Stuff like transaction log size, number of VLFs, transactional throughput can affect performance, but there are also other factors that contribute to mirroring throughput. For example, network latency, disk subsystem, SQL Server Editions and Versions will all affect how fast your mirroring can be.
Can you provide details about your SQL Server versions and Editions?
http://sqlcat.com/sqlcat/b/technicalnotes/archive/2007/09/17/database-mirroring-log-compression-in-sql-server-2008-improves-throughput.aspx - DB mirroring log compression in SQL Server 2008
http://sqlcat.com/sqlcat/b/whitepapers/archive/2007/11/19/database-mirroring-best-practices-and-performance-considerations.aspx performance considerations and best practices
http://www.microsoft.com/en-us/download/details.aspx?id=23365- EE vs standard
SQL Server DBA
Please click "Propose As Answer" if a post solves your problem, or "Vote As Helpful" if a post has been useful to you