Reading SQL Error log typically we do by going through the Management then SQL Server error log and open respective one . But it is little difficult to trace it out only the particular information out of the bunch of records if you activated all kind of log info. So alternatively it could be done using SSMS by executing extended system procedures.
xp_readerrorlog returns the latest error log
xp_readerrorlog 1 returns the latest archived error log
xp_readerrorlog 2 returns the previous archived error log
.......... and so on.
You can try inserting the log records into temp table then filter only the information that you might required to analyze the issue. I hope this would help and save the time instead of checking complete error log manually.
xp_readerrorlog returns the latest error log
xp_readerrorlog 1 returns the latest archived error log
xp_readerrorlog 2 returns the previous archived error log
.......... and so on.
You can try inserting the log records into temp table then filter only the information that you might required to analyze the issue. I hope this would help and save the time instead of checking complete error log manually.
