Shulou(Shulou.com)05/31 Report--

This article mainly introduces the SQLSERVER2008 errorlog is too large to cause the database can not start how to do, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor with you to understand.

In the morning, the application found that the database could not connect.

After restarting the host, it was found that the database service could not be started, and the startup service reported a 17058 error

View permissions are normal.

Enter: C:\ Program Files\ Microsoft SQL Server\ MSSQL10_50.MSSQLSERVER\ MSSQL\ Log

It is found that the errorlog file reaches about 37g.

When the database is started, the errorlog file will record the whole open and run. The process of termination.

The ErrorLog display includes the following:

(1) the version of SQL and the basic information of Windows and Processor

(2) startup parameters of SQL, authentication mode and memory allocation mode

(3) whether each database can be opened normally. If not, what is the reason?

(4) errors related to database corruption

(5) Database backup and recovery action records

(6) DBCC CHECKDB record

(7) memory-related errors and warnings

(8) warning when an exception occurs in SQL scheduling. Generally speaking, SERVER HANG server death is accompanied by these warnings.

(9) warning of a long delay in the SQL Istroke O operation

(10) other high-level errors encountered by SQL during operation

(11) access out of bounds error within SQL (Access Violation)

(12) SQL service shutdown time

Think about it, will the excessive size of this file affect writing? Based on previous experience, rename the backup errorlog file to errorlog.bak. Start the database, as expected. The database starts normally.

Let's take a look at the mechanism of errlog:

By default, SQLSERVER retains 7 errorlog files, which are expressed in chronological order with the file name. 1. 2. 3.

Every time the service is restarted, or the EXEC sp_cycle_errorlog is executed, the file extension is incremented, and the earliest copy is automatically deleted.

Therefore, the errorlog file will not be too large, so why did the file reach more than 30 gigabytes this time?

Thank you for reading this article carefully. I hope the article "what to do if the SQLSERVER2008 errorlog is too large to start the database" shared by the editor will be helpful to everyone. At the same time, I also hope that you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.