Please start any new threads on our new 
    site at https://forums.sqlteam.com.  We've got lots of great SQL Server
    experts to answer whatever question you can come up with.
    
        | 
                
                    | 
                            
                                | Author | Topic |  
                                    | a.elagouzStarting Member
 
 
                                        3 Posts | 
                                            
                                            |  Posted - 2014-07-20 : 08:22:35 
 |  
                                            | 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 problemplease help me |  |  
                                    | tkizerAlmighty SQL Goddess
 
 
                                    38200 Posts | 
                                        
                                          |  Posted - 2014-07-20 : 19:19:55 
 |  
                                          | 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 KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |  
                                          |  |  |  
                                    | a.elagouzStarting Member
 
 
                                    3 Posts | 
                                        
                                          |  Posted - 2014-07-21 : 08:04:32 
 |  
                                          | 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) |  
                                          |  |  |  
                                    | tkizerAlmighty SQL Goddess
 
 
                                    38200 Posts | 
                                        
                                          |  Posted - 2014-07-21 : 10:28:34 
 |  
                                          | 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 KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |  
                                          |  |  |  
                                    | a.elagouzStarting Member
 
 
                                    3 Posts | 
                                        
                                          |  Posted - 2014-07-22 : 02:48:05 
 |  
                                          | Ok tatra do u have any suggestion trust web sit for this issue |  
                                          |  |  |  
                                    | tkizerAlmighty SQL Goddess
 
 
                                    38200 Posts | 
                                        
                                          |  Posted - 2014-07-22 : 12:46:56 
 |  
                                          | https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=brentozar%20troubleshooting%20deadlocksTara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |  
                                          |  |  |  
                                |  |  |  |