IMHO, last wait type is not nearly so useful as trending all waittypes over time. Search microsoft.com for a word document on SQL Server 2005 Waits and Queues.

That would be nice, but a significant departure from what I got just a few months ago which was late 4th quarter. They weren't going to really start working...

1) You can use WMI scripting to easily access perf mon counters, IIRC.

2) The undocumented (search online for information) dbcc memorystatus offers a wealth of information about sql memory usage/allocations.

This is another example of...

Guru (7/14/2008)

---

Hi I have used SQL server 2005 enterprises edition, windows server 2003, RAM size 3GB, hard disk Sata400GB my database size upto 150GB this sufficient for my hardware...

1) They are AMAZINGLY fast for reads (like 3 orders of magnitude faster seek times).

2) They are AMAZINGLY expensive, although...

Perhaps the max memory setting for sql server was changed AFTER the server had been running? I have seen sql server quite reticent to release memory back to the...

Looks like it may be old ADOc code maybe? In any case, I would look for a complete rewrite to avoid row-by-row processing if at all possible. Indexing...

I still don't understand why you think range scans would be "screwed up" if you have a million integer identity values from 1000000 to 1999999. Actually I am not...

g.brennan (7/10/2008)

---

A question for the experts...

Does using an identity column as a surrogate key result in an imbalanced index?

e.g. 1001,1002,1003,1004 {...} appears to give poor selectivity,

so if you reverse...

Look for 2 word documents from microsoft: sql 2005 troubleshooting performance problems and sql 2005 performance tuning waits and queues

Also, I really found a lot of good stuff in "SQL...

Note that page life expectancy went from low double digits to almost 6000. Isn't it simply amazing that the fact that RAM access is about 4 orders of magnitude...

1) prior to doing a windows file defrag it is strongly recommended to shut down sql server.

2) I sure would want to do a DBCC CHECKDB after all that work...

Did you read the link I posted earlier in the thread before recommending this action? The link doesn't go into the details about why...

http://www.karaszi.com/SQLServer/info_dont_shrink.asp

Massive fragmentation is the usual result of a shrink operation. Then as the database grows back up it causes more internal AND external fragmentation. Index maintenance isn't effective,...