This counter is the % of log reads that were satisfied from the log cache.

The log cache is used to hold information that will be written to the
transaction log and also used when the log information that has recently been
written inot the log cache is read.

with this information how I could analyze the the % of my log cache hit
ratio and when I could say it's bad or not bad %?

is it SQl Server who read the information in the transaction log and when?

Manuel
SQL Server DBA

I found two thing about this counter.

1- this counter indicate some problem with the transaction log or for
transaction. For exemple, if your transaction log is set to no grow up and
you did a lot of transaction (begin tran-commit) . To test that, put your
transaction log to no grow up and run some insert,delete and update in a
transaction and you will see.

2- There are som query with to large and complex where clause.

N.B There is some key notes, this counter will be reset when you put offline
the BD or your server.


"Manuel" wrote:

> This counter is the % of log reads that were satisfied from the log cache.
>
> The log cache is used to hold information that will be written to the
> transaction log and also used when the log information that has recently been
> written inot the log cache is read.
>
> with this information how I could analyze the the % of my log cache hit
> ratio and when I could say it's bad or not bad %?
>
> is it SQl Server who read the information in the transaction log and when?
>
> Manuel
> SQL Server DBA
>
>