With MySQL secondary/primary, sync_binlog and innodb_flush_log_at_trx_commit control log and disk flushing, and are important to maintain consistency between primary and secondary (so that the secondary can never be ahead of the primary in case of a crash). An admin is free to set this (and mess this up), for performance reasons for instance. I was wondering, how is this arranged in Microsoft SQL Server in mirroring or replication mode? Does it even have the same tunables?
Specific questions would be:
- Being more 'click-and-go', does SQL server set everything to safe values?
- What are equivalent settings, or settings one must know when dealing with primary/secondary consistency, and their performance impact?