Behaviour of SP_READERRORLOG in SQL 2000 and 2005
You may be aware that SP_READERRORLOG can be used from a query analyzer or query editor to read the error log contents without opening the file on the disk or from Management Studio (or Enterprise Manager).
I'm not sure whether you have observed that there is a change in behaviour between SQL 2000 and 2005 versions. The problem here is this is not a documented stored procedure and very hard to find on the SQL books online or any other technet documentation.
So in order to find out more on this undocumented stored procedure you could use it as:
--In SQL Server 2005
EXEC xp_readerrorlog returns the columns such as:
LogDate ProcessInfo Text
--In SQL Server 2000
EXEC xp_readerrorlog returns the columns such as
ERRORLOG ContinuationRow
So the users must be more careful when they try to collate the results to a table or to any other data source for the change of columns.