Tag Info

Combing through the docs, I see the following (accidental incorrect details will hopefully (or surely) be pointed out by others): There is a separate server process called the background writer, whose function is to issue writes of "dirty" (new or modified) shared buffers. BW does its work according to its config parameters. It writes at most ...

Use a database snapshot. Create a snapshot, do your worse. If things go ugly, revert to the snapshot, see Revert a Database to a Database Snapshot. Database snapshots are copy-on-write so they take almost no space on disk (the space taken will grow as you update the original db and the copy-on-write must save the previous data). They're fast to create and ...

If Resource Monitor says that SQL Server is actually performing the checkpoint (i.e., it's working okay, just that it's slow), all you can and should do is wait. If the disk subsystem is busy anyway (shared storage?), is it possible the other load has increased and now the I/O subsystem is near or at capacity? If you aren't measuring (recording) metrics ...

I'm not completely certain, but I believe the "thread" in "thread checkpoint" refers to a DBWR thread/process. The "certain target" referenced is configurable; several init.ora parameters influence it, including: FAST_START_MTTR_TARGET LOG_CHECKPOINT_INTERVAL LOG_CHECKPOINT_TIMEOUT