doobya (2/3/2009)

---

SQL 2005 has xml deadlock report in profilerwhich will track deadlock down to tables and stored procedure statementsI think your solution does not solve the deadlock - just makes...

sureshot (2/3/2009)

---

Great article on investigating the deadlock. Just a note that if you're running SQL 2005/2008, the trace flag 1222 (http://msdn.microsoft.com/en-us/library/ms178104.aspx) provides a lot more information so you don't...

rsteeves (2/3/2009)

---

Thanks, guys. I have a maintenance plan to rebuild indexes once a month, but I see that I should chnage it a weekly process. We are running in about...

PaulB (2/3/2009)

---

:w00t: mmhhh... I wasn't avoiding -elluding?- the issue and I think my proposed solution is spot...

Keep in mind that a few years back SQL Injection wasn't a main stream subject, and most DBA's that I know and consult with have been in place for 3-5...

PaulB elludes to this but doesn't actually make the point clear. Check if the tables have a Clustered Index on them. If they don't, then your unused space...

GilaMonster (2/3/2009)

---

Not necessarily. There's a person on another SQL...

There is actually more than just that link:

http://blogs.msdn.com/bartd/archive/tags/SQL+Deadlocks/default.aspx

Bart Duncan has a bunch of them and the above reference is on another article I put in, but I guess I missed...

Sorry bout that Jack. I am sure that you could add to the basics that are covered by this article though. I tried to follow KISS for this...

A good reference for how bad this stuff can be is Niel Carpenter's blog. He is a member of the Security response team at MS and has a few...

Check if the Auto-Close property for the database is set to True in the Database Properties. I have seen this kind of error in the past where Auto-Close was...

Does it really matter for the context of the question posed in this thread?

Your aversion to CLR takes every thread in this forum completely off topic and clutters...

Not that your personal...

Based on External_Access and a Serializer assembly, it would most likely be a webservice call, which are becoming more and more normal place.

Another way to go about it for all Errors and not just errors generated by jobs in SQL Agent can be found on my Automating Common DBA Tasks Series:

http://code.msdn.microsoft.com/SQLExamples/Wiki/View.aspx?title=AutomatedDBA&referringTitle=Home