I do agree with Jeff, but an acquaintance of mine does have a book that could be useful, SQL Server 2008 Accelerated by Rob Walters.

You should be able to just give the user execute privileges to the procedure(s).

Not without a third party log reading tool.

Why not run a server side trace and capture the transactions being run. Then you can figure out the bad actor.

Every system is different, but I personally wouldn't sweat fragmentation until it at least got as high as 20% and probably I wouldn't do a rebuild until I saw fragmentation...

krypto69 (1/30/2009)

---

I have a table that is 16 columns wide, and has 1000 (random, unique) inserts per second.

They run ad-hoc queries, that are taking too long to return. Here's...

Nir Netivi (1/31/2009)

---

We have a call center web application (ColdFusion) connected to a SQL 2005 server. As our call center gradually grows we are getting more and more deadlocks.

We...

John (1/30/2009)

---

Thanks for the reply, but it's not quite what I'm asking. If you add an ORDER BY clause and look at the execution plan, you will see there...

Usually it's best when you have a new question to...

Whoop!!!!

[holding up a lighter]

Nah,...

It looks largely pretty good. There are several key lookups and the four index scans at the top. For example one of the key lookups is against Customer_Canvasser and it's...

You could upgrade to 2008 which has compression built in.

The other option that comes to mind is to compress them using, something, pkzip?, and then store them as a binary....

Beware the wrath of the Fetts!

Then, whatever it's doing, it's plodding along. You can kill it, but you might be waiting for a while for the rollback to clear.

Usually save it as a .sqlplan file and then zip it up and post it.