Skip to main content

SQL Server Error Log... Some tweaks good to know....

Lots of time we hear about many issues related to SQL Log. I find this is surely one of the area where we depend most but pays least attentions. So today I thought to discuss couple of very simple situations which probably will help us to work with SQL Error log…

One very interesting situation is to know where exactly SQL Log resides. We know we can refer it from SQL Server Management Console/Any third party tool but what if SQL Server is not online and we need to read log by going to their physical location? More interestingly, what if we need to instruct SQL Server to write a log to a different location?
Also another situation I see that many people believe that SQL Server will always store 6 recent most error log only. Actually by default SQL Server stores 6 most recent error logs and you can change this number anywhere from 2 to 99 if you want to customize it.
Default path (where error logs are stored) and number of most recent error log files to be store before recycling is actually defined while we install SQL Server. So we should change these values when ever we need to customize the server. Hopefully this small posts gives us enough clue to perform couple of vital customizations related to SQL Server Logs.
Now here is the direct solutions for the theories I mentioned here… :)

Click here to know the SQL error log location
Click here to change the SQL error log/SQL Agent log path
Click here to change the number SQL Error log files archived before they are recycled


Popular posts from this blog

How to kill a negative SPID (like SPID -2) in SQL Server?

Rarely this scenario will arise when most likely you see this negative SPID (most likely SPID -2) is blocking other transaction causing issues. If you try to kill it using normal KILL command, it will fail reporting below error: Msg 6101, Level 16, State 1, Line 1 Process ID <SPID Number> is not a valid process ID. Choose a number between 1 and 2048 This is because of an orphaned distributed transaction ID.  Please follow below steps to kill it: Step 1: -- Find the UOW Number select req_transactionUOW from master..syslockinfo where req_spid = <SPID Number> --  <SPID Number>  is -2 most likely. Step 2: -- Copy the UOW number from Step one KILL ‘<UOW Number>’ This will kill the negative SPID resolving the issue.  However please note following points: 1. For SPID -2, you may find multiple UOW numbers. Please start killing them one by one. Typically killing first UOW will resolve the issues. (ie. will kill all UOW and release

DMV/TSQL to find out basic hardware information of the SQL Server including when SQL Server started.

Please use below code: However, please be advised that it can not tell correct information around virtualization.  For example, it will show Hypervisor even if SQL runs on a physical OS where Hyper-V is on. So use this query only when you do not have sufficient access on underlying Windows Operating system to get these information directly. -- Basic hardware information for SQL Server (sys.dm_os_sys_info) /* This query is courtesy of All credits goes to original author. */ SELECT cpu_count AS [Logical CPU Count] , scheduler_count , hyperthread_ratio AS [Hyperthread Ratio] , cpu_count / hyperthread_ratio AS [Physical CPU Count] , physical_memory_kb / 1024 AS [Physical Memory (MB)] , committed_kb / 1024 AS [Committed Memory (MB)] , committed_target_kb / 1024 AS [Committed Target Memory (MB)] , max_workers_count AS [Max Workers Count] , affinity_type_desc AS [Affinity Type] , sqlserver_start_time AS [

‘Trace Skipped Records’ – What is this and how to resolve it while using SQL Server Profiles?

In some very rare case, you may experience a very weired message in profiler’s output as ‘Trace Skipped Records’ while you trace something on SQL Server. Screenshot of similer situation is as below: This is not an error but it comes by design of SQL Server (I believe so). When you are using SQL profiler and return data is too big to fit in the GUI (for me, it is an enormous xml), SQL Server simply prints this message and proceed to next step. Mostlikely this is to save server’s memory and performance. Although not suggested and guranteed, you can try to run a server side trace and dump data in a file which should capture all the data. However, it is strongly not recommended to run a trace on your production server from server side. Microsoft will probally document this limitation in future. More details may be found at