foreword
Doing a good job in daily inspection is an important step in database management and maintenance, and it is necessary to register the date and results of each inspection, and may need to issue an inspection report.
This series aims to address some common pitfalls:
- I don't know what to check
- I don't know how to check easily
- Too many machines, check up trouble
- Difficulty in generating reports and inability to visualize results
The log information of SQL Server often reflects some of your system problems, so the inspection of traditional Chinese medicine can check the errors in these system logs in time and solve them in time. This is also the purpose of inspection.
Log overview
Check the log tab in the [Check Items]-[All] page, and a warning will be given when errors are found in the log.
![]()
![]()
![]()
log details
On the [Log] page, you can view the detailed information of the log.
Error description:
1. File Autogrow: Whether it is a data file or a log file, when the file is full, it will grow according to the set value to ensure that it can continue to be written. When the file has an auto-increment operation and the corresponding time is slow, it will be recorded In log:
Autogrow of file 'templog' in database 'tempdb' was cancelled by user or timed out after 10180 milliseconds. Use ALTER DATABASE to set a smaller FILEGROWTH value for this file or to explicitly set a new file size.
Note: The common cause of this problem is that the set growth is too large, or the file is large and the percentage growth is used (default 10%, it is recommended to use a fixed increment value)
2. Login failed: Login failed, please check whether the password is configured correctly in the program. If public network access is provided, check whether it has been brute force cracked. Whether the account is disabled on the database, etc.
3.Operating system error: Operation error, such problems generally need to be paid attention to and solved in time.
例：Extend Disk Backup: failure on backup device 'D:\autoback\backup_2016_10_02_062001_0859543.bak'. Operating system error 112(磁盘空间不足。).
4. I/O requests ：此类问题主要表现为磁盘IO响应速度慢。请参见磁盘压力分析，响应慢的解决办法。
SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [H:\DATA\zk.MDF] in database [zk] (57). The OS file handle is 0x0000000000001F90. The offset of the latest long I/O is: 0x00000d8a056000
总结
日志的错误往往要得到重视，当在日志中发现异常，请及时排查，这也是巡检的目的，消灭问题与萌芽阶段。