John Mitchell-245523 (11/10/2009)
Looking at it rationally rather than empirically, I'd say that since a log file is written to sequentially, any activity (such as truncation) that moves the disk heads away from the end of the file is likely to have some impact on performance.
True, but unless the log is the sole and only file on the physical disk (no other tran logs, no data, no backups, etc) then the head will be moving to write the other files. Also a log backup will move the head, as will a transaction rollback (as far as I know) as both have to read the log.
I'd just like to hear the reason behind the claim and any proof.
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