FIX: Problem Using Xp_readerrorlog When Reading Large Error Log

When you use the SQL Enterprise Manager (SEM) 'Server - Error log' or run xp_readerrorlog with a large error log, you may find that it takes a long time to run. If the user closes SEM or ISQL/w before xp_readerrorlog finishes returning results, you may find the following messages repeated in the SQL Server error log and application event log: The size of the error log may grow 20K or more every second, and the server will be very slow. The problem will stop after 15 to 20 minutes, and everything will return to normal. However, during this 15 to 20 minute window, the error log may grow to 30 MB, and any operation on the server will be extremely slow.

To work around this problem, use Notepad, Write, or another text editor to view the SQL Server error log.

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0.

Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:For more information, contact your primary support provider.