Skip to main content

An easier way to work with the SQL Server Error Log

There are three main ways to access the SQL Error Log: via the SSMS GUI, via the system stored procedure sp_readerrorlog or the extended stored procedure xp_readerrorlog. The code below I have close to hand in a Snippet and I probably use it every day. It copies the contents of the SQL error log and optionally the SQL Agent error log to a temporary table. Once there you query it for specific information. This can be also be done by using parameters 3 and 4 of sp_readerrorlog but for me this is a little more flexible.

 /*
sp_readerrorlog can take 4 optional parameters, they are:
    1. The number of the error log file you want to read: 0 = current, 1 = Archive #1, 2 = Archive #2, etc...
    2. Log file type: 1 or NULL = error log, 2 = SQL Agent log
    3. Search string 1: String one you want to search for
    4. Search string 2: String two you want to search for to further refine the results
*/
----------------
-- Current SQL Error log
---------------
IF EXISTS (SELECT 1 FROM tempdb..sysobjects WHERE id=OBJECT_ID('tempdb..#ErrorLog'))
    DROP TABLE #ErrorLog

CREATE TABLE #ErrorLog (
       logdate DATETIME
       ,processinfo VARCHAR(200)
       ,info VARCHAR(8000)
       )
GO

INSERT INTO #ErrorLog
EXEC sp_readerrorlog 0
       ,1
GO

CREATE CLUSTERED INDEX ix_date ON #ErrorLog (logdate)
GO
   
-- Show the last 10,000 errors within the last 24 hours
SELECT TOP 10000
    logdate
    ,processinfo
    ,info
FROM #ErrorLog
WHERE logdate > DATEADD(HOUR, - 24, GETDATE())
ORDER BY 1 DESC

-----------------
-- Current SQL Agent log
-----------------
IF EXISTS (SELECT 1 FROM tempdb..sysobjects WHERE id=OBJECT_ID('tempdb..#ErrorLogAgent'))
    DROP TABLE #ErrorLogAgent

CREATE TABLE #ErrorLogAgent (
       logdate DATETIME
       ,processinfo VARCHAR(200)
       ,info VARCHAR(8000)
       )
GO

INSERT INTO #ErrorLogAgent
EXEC sp_readerrorlog 0
       ,2
GO

CREATE CLUSTERED INDEX ix_date ON #ErrorLogAgent (logdate)
GO

-- Show the last 10,000 errors within the last 24 hours
SELECT TOP 10000
    logdate
    ,processinfo
    ,info
FROM #ErrorLogAgent
WHERE logdate > DATEADD(HOUR, - 24, GETDATE())
ORDER BY 1 DESC



Comments

Popular posts from this blog

How to move the Microsoft Assessment and Planning Toolkit (MAP) database to a different drive

The Microsoft Assessment and Planning Toolkit (MAP) is a very useful tool for scanning your network to find instances of SQL Server plus all manner of detailed information about the installed product, OS and hardware it sits on.


<Click image to enbiggen>
There is an issue with it the database it uses to store the data it collects, however. Assuming you don't have an instance called MAPS on your server, the product will install using LocalDB (a cut down version of SQL Server Express) and puts the databases on your C: drive. If you then scan a large network you could easily expand the database to 10GB which may cause issues on a server when that drive is often one of the smallest. However, there is a simple solution: connect to LocalDB using Management Studio, detach the databases, move to a different drive, set permissions on the new location if required and reattach the database. How do you connect to LocalDB? Here you go:

Connect to (localdb)\MAPTOOLKIT


The databases I move…

Generate scripts to attach multiple databases

There is a handy little "by product", if you like, when running queries which means you can quickly generate scripts to do different things. Below is an example of generating multiple "attach" commands that you can copy from the results pane into the main SSMS window for execution. I have found this very handy in the past:


SELECT 'CREATE DATABASE ['+name+'] ON ( FILENAME = N''F:\MSSQL\Data\'+name+'.mdf'' ), ( FILENAME = N''E:\MSSQL\Log\'+name+'_log.ldf'' )  FOR ATTACH GO ' FROMmaster.dbo.sysdatabases WHEREnamenotin('master','msdb','model','tempdb')
ORDERBYname

The Purge SQL Agent Job for MDW takes a long time to complete

I use the dbWarden alerts to inform me if a SQL job is taking longer to complete than normal and I got one this morning:
I noticed by looking at the history this purge job was gradually taking longer and longer to complete each day since I installed it again (see mylast post on this):
RunDate RunTime Duration ExecutionStatus JobName 04/10/2013 02:00:01 00:00:45 Succeded mdw_purge_data_[MDW] 05/10/2013 02:00:00 00:13:27 Succeded mdw_purge_data_[MDW] 06/10/2013 02:00:00 00:17:03 Succeded mdw_purge_data_[MDW] 07/10/2013 02:00:01