Deadlocked message on OLAP Server application log | SQL Server Performance Forums
SQL Server Performance Forum – Threads Archive
Deadlocked message on OLAP Server application logI see the following dead locked message on our OLAP Application log.PROD: OLAP Service EventLog IS CRITICAL – Application [error] [mssqlserverolapservice #117]: Unexpected fatal error occurred. Attempting to restart server. – 11/10/07 13:13:27â€â€œPROD: OLAP Service EventLog IS CRITICAL – Application [error] [mssqlserverolapservice #124]: Relational data provider reported error: [Transaction (Process ID 74) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.:40001] . – 11/10/07 13:02:07â€
I was wondering, is there a way, i know, what SQL Query was process – 74 was running at the time of dead lock? Is there a way i could avoid this error?
Appreciated some input.
Please check it through the trace window.
Generating a deadlock http://www.microsoft.com/winme/0509/25037/SQL-01_Demo8-2.asx
Demo 8-3 Analyzing deadlock using SQL Profiler http://www.microsoft.com/winme/0509/25037/SQL-01_Demo8-3.asx http://www.sql-server-performance.com/tips/deadlocks_p1.aspx & http://www.sql-server-performance.com/articles/per/deadlock_sql_2005_p1.aspx should get you the tips to avoid this deadlock.
My current version is AS – 2000. I dont think, i neither have the option of running profiler to capture the deadlocks nor see, what queries are been executed.
Is there any other way to see, why my server is getting into deadlocks?
If you not able to run profiler then it sounds like tools problem, try to run it from server itself – http://searchsqlserver.techtarget.com/tip/0,289483,sid87_gci1255793,00.html fyi.
Thanks for the answer.
Unfortunately i can not run SQL 2005 profiler against 2000 AS Server. It’s not supported. Looks like SQL 2000 AS is very limited when it comes to monitoring. haven’t found anything which can be used to either capture queries running against AS Server nor came across with any way to figure out, who’s running what against a 2000 AS Server.