HiveBrain v1.2.0
Get Started
← Back to all entries
debugsqlMinor

Buffer Pool scan took 10 seconds error

Submitted by: @import:stackexchange-dba··
0
Viewed 0 times
tookerrorscansecondspoolbuffer

Problem

Using SQL server 2017 (14.0.3381.3) with Always On High Availability environment.

Getting error:"Buffer Pool scan took 10 seconds: database ID 8, command 'CHECKPOINT', operation 'FlushCache', scanned buffers 144321190, total iterated buffers 150079215, wait time 42 ms. See 'https://go.microsoft.com/fwlink/?linkid=2132602' for more information"

This is a new feature that is included in the 2017 CU23, under the VSTS bug number 13741858.

I see the list of all the operations that can trigger a scan but none of them are happening on my machine, is there a way to tell what causes the scan? - OR - Is there a Trace Flag that can be used to turn off the log of this error?

Solution

I see the list of all the operations that can trigger a scan but none of them are happening on my machine, is there a way to tell what causes the scan?

It's a CHECKPOINT on database ID 8. It says so right in the message.

Do you have INDIRECT CHECKPOINT enabled? What does

select database_id , name, target_recovery_time_in_seconds
from sys.databases
where database_id = 8


return? The default of 60 enables indirect checkpoints.

Code Snippets

select database_id , name, target_recovery_time_in_seconds
from sys.databases
where database_id = 8

Context

StackExchange Database Administrators Q#287632, answer score: 2

Revisions (0)

No revisions yet.