September 23, 2014 at 9:07 am
I encounter deadlock issues almost every half an hour. Some user gets blocked by somebody. I don't have to kill the session because when user try to resubmit the query, it gets resolved on its own. Is there a way to prevent this deadlock issue?
"He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]
September 23, 2014 at 9:20 am
You have to specific with terminology here. A deadlock is a specific type of blocking that cannot be resolved without canceling/abending at least one task. Blocking can eventually clear itself up.
Are you seeing deadlocks or just blocking?
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
September 23, 2014 at 11:26 am
You need to figure out what is blocking the command. You can use the system_health session in SQL Server 2008 to pull the deadlock XML[/url].
From there you have to determine what process is causing the deadlock and adjust for it. If your users are executing actual T-SQL frequently they should build their queries to workaround or detect for deadlock errors.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply