Regarding your slow downs...

When the server goes slow, check the sys.dm_os_waiting_tasks DMV, see if queries are waiting and, if so, what it is that they are waiting for.

You may...

Read committed is the default isolation level for SQL Server. There's no need to set it explicitly

If a query uses read committed and tries to read a row that's being...

284MB for the plan cache on a server with 16 GB is nothing. I really wouldn't worry.

What are your server's max and min memory settings? Anything else on the server?

The...

Did you install the SQL 2005 database engine, or just the workstation tools?

If you have 2005 and SQL 2000 on one machine, then 2005 is most likely installed as a...

IMHO, update usage isn't worth running often. The CheckDB is done by the integrity check as well as this piece of home-brewed code.

Dunno about missing checkpoint, but if there's an open transaction then the log records can't be discarded until the transaction has completed.

Can you post the SQL queries, the table structure and any indexes on those tables? Also, if you have the deadlock graph that will be very useful (Obtain deadlock graph...

I can answer that when you tell me how much memory's on the server.

What version of SQL 2005? (What does SELECT @@version return?)

To give you an idea, one of my...

Those IO stats don't look too bad. 99.6% of all reads are done from memory not from disk. There's virtually no swapping occurring. Not really what I would expect if...

If you run that in Query analyser with the execution plan enabled, what...

Can you post one...

SQL Noob (3/27/2008)

---

Michael Earl (3/27/2008)

---

You cannot - if you were able to kill a rollback, it would leave your database in an inconsistent state. If you stop and start...

How much memory do you have? What service pack of SQL are you running? 32 bit or 64 bit?

If you run the following, what's taking the most memory?

select [Name], SUM(single_pages_kb...

The one thing I noticed is the date comparisons. You should rather do comparisons (with between if necessary) of the dates as datetimes rather than converting the dates to strings...

Nothing I posted was SQL 2005 specific.

For the counters, use performance monitor. They're not within profiler.

Check the server's max and min memory settings. Check to see if AWE is...