I found lots of
BTree Split/Shrink in my SQL Server logs.
At the time of these logged events, the performance counters showed that lazy writes were very slow, the log flush rate was high, and write/sec was close to 30000. Disk IO was also very high.
I'm sure that the server traffic was normal and there was no abnormal data file growth at the time, but the log file was twice as large as usual. I used the
dump_log() function to get statistics on logs:
- Windows Server 2008 sp2
- SQL Server 2014
- Database target_recovery_time = 60 seconds
- Database auto shrink and index auto shrink = false
- Log backup hourly
- Physical disk: pcie ssd 3.0T with 70% used
- Cleaned up useless indexes
- Reorganized fragmented indexes
- Increased the automatic archiving data operation about 500w daily backup and delete
Archiving was at 4:00-5:00 very day, I suspect that the ghost cleanup is related to my physical backup deletion and archiving. The logfile was double than the same time yesterday.
- What is the "shrinkd" in SQL Server logs?
- Is it shrink database? I can't find any information about it on the Internet.If the AUTO_SHRINK set off and there is not skrink job,how did it be triggered? Thanks.