SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2012 Forums
 Analysis Server and Reporting Services (2012)
 error on areport
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

a.elagouz
Starting Member

Egypt
3 Posts

Posted - 07/20/2014 :  08:22:35  Show Profile  Reply with Quote
have aproblem on my ssrs report i make it on aserver and the database is on another server when i run the report it just load ad give me message (execution failed for shared data set dataset1) and ( transaction (process id 62) was deadlocked) what should i do to solve this problem
please help me

tkizer
Almighty SQL Goddess

USA
37466 Posts

Posted - 07/20/2014 :  19:19:55  Show Profile  Visit tkizer's Homepage  Reply with Quote
Troubleshooting deadlocks involves finding the other query in the deadlock and seeing what can be done to fix it, such as refactoring code, changing indexes, modifying the table design, etc. Google "troubleshooting deadlocks" for more info. This is a widely discussed topic and is not a problem with your report, but rather a query/design issue.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

a.elagouz
Starting Member

Egypt
3 Posts

Posted - 07/21/2014 :  08:04:32  Show Profile  Reply with Quote
thank u tkizer but my problem not on the sql server management studio it is happend when i make ssrs report and use any stoured procedure when i run it is just load and message (execution failed for shared data set dataset1) and ( transaction (process id 62) was deadlocked)
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
37466 Posts

Posted - 07/21/2014 :  10:28:34  Show Profile  Visit tkizer's Homepage  Reply with Quote
My post is still valid. The issue is with the query/table design/etc. You will need to google "troubleshooting deadlocks" and go through those topics. It is not a small topic. The first part is figuring out the other query involved in the deadlock. You can do that by adding a trace flag so that the data is captured in the Error Log, though it's challenging to read.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

a.elagouz
Starting Member

Egypt
3 Posts

Posted - 07/22/2014 :  02:48:05  Show Profile  Reply with Quote
Ok tatra do u have any suggestion trust web sit for this issue
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
37466 Posts

Posted - 07/22/2014 :  12:46:56  Show Profile  Visit tkizer's Homepage  Reply with Quote
https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=brentozar%20troubleshooting%20deadlocks

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.08 seconds. Powered By: Snitz Forums 2000