The Recovery Interval option can be configured automatically.
SQL Server setup sets it to 0, which means autoconfiguration. In SQL Server
2008, this means that the recovery time should be less than one minute.
This
option lets the database administrator control the checkpoint frequency by
specifying the maximum number of minutes that recovery should take, per
database. SQL Server estimates how many data modifications it can roll forward
in that recovery time interval. SQL Server then inspects the log of each database
(every minute, if the recovery interval is set to the default of 0) and issues
a checkpoint for each database that has made at least that many data
modification operations since the last checkpoint. For databases with relatively
small transaction logs, SQL Server issues a checkpoint when the log becomes 70
percent full, if that is less than the estimated number.
The Recovery Interval option does not affect the time it
takes to undo long-running transactions. For example, if a long-running
transaction takes two hours to perform updates before the server becomes
disabled, the actual recovery takes considerably longer than the Recovery
Interval value.
The frequency of checkpoints in each database depends on the
amount of data modifications made, not on a time-based measure. So a database
that is used primarily for read operations will not have many checkpoints
issued. To avoid excessive checkpoints, SQL Server tries to make sure that the
value set for the recovery interval is the minimum amount of time between
successive checkpoints.
Most writing to disk doesn’t actually happen during checkpoint operations. Checkpoints are just a way to guarantee that all dirty pages not written by other mechanisms are still written to the disk in a timely manner. For this reason, you should keep the Recovery Interval value set at 0 (self-configuring).
http://www.mybasicknowledge.com/2012/09/sql-server-recovery-models-and.html
