Over the next few days we are going to start the migration to a new forum
application. I'm going to start with high post count and active users. You may
receive an invitation to the new forums. It's not spam. It's just me trying to
seed the user base. My goal is to open it up over the weekend.
Once we open the site we'll block registrations here. We should be open
shortly on the new site.
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
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.
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)
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.