February 15, 2012 at 9:10 am
Hello,
I'm on SQL Server 2005 Workgroup Edition.
Our application is being troubled by deadlocks and I'm trying to find out what is causing it.
I've set trace on
DCBB TRACEON(1222,-1)
and run a test in an unrelated database to cause a deadlock.
However nothing seems to be written to C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\
DBCC TRACESTATUS(1222) confirms it is on.
is this because it's Workgroup Edition as it works fine on our Developer Edition?
As always, any help is appreciated.
Giles
February 15, 2012 at 9:21 am
So there's nothing in the error log? Are you looking at the right instance (if you have multiple instances)?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 15, 2012 at 9:34 am
Actually that's a very good point, it appears there is SQL Express on the server too and that was the log location for that.
The server I'm interested in the default instance though and
C:\Program Files (x86)\Microsoft SQL Server\MSSQL\LOG doesn't have any files in it.
I've scoured the rest of the server for other LOG folders under SQL and although I have found it in numerous places (i.e. C:\Program Files (x86)\Microsoft SQL Server\MSSQL.4\MSSQL\LOG) I can't find a log file written to today.
I'm starting to think I need a new pair or glasses/job.
Giles
February 15, 2012 at 9:43 am
Found it.
D:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\LOG
I should have looked in the SQL Server properties, General tab and the Root Directory sooner.
Thanks anyway
Giles
February 15, 2012 at 9:49 am
Easiest way to find the location of the error log file is to open the log from Management Studio (object explorer. Management -> SQL Server Logs)and check right at the beginning of the file
Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\Log\ERRORLOG'.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply