hmm that KB relates to a fileserver, not a sql server. batch processes are difficult to debug and your situation may be down to waiting threads - I'd look...

No you should not alter your indexes for that reason. Generally the selectivity of the first column defines whether the optimiser will use the index. as all your start with...

I don't have that problem. Are your installs out of the box and are you a sysadmin?

in sql 2005 sp_updatestats will only update stats which need updating, unlike sql 2000 so the impact is far less. I update stats twice a day on my prod server,...

I'm going to ask what I normally ask - do you have problems with waits and schedulers and are you monitoring them so that you see this problem, or did...

sql 2005 automatically assigns workers calculated as per cpu/core. If you're talking 256 worker threads this sounds very much like sql 2000 as by default the worker count is set...

the point about config and tuning is that you can't do it without stats and trending data that allows you to see exactly what your database is doing. multiple files...

sorry got pulled away and forgot your original Q's. cpu is bad, check your page life expectancy. the one thing which is hard to trim is cpu. I'd probably suggest...

I'd suggest you purchase, very quickly, an inside sql book - the 2005 ones tended to spawn so in a sense the inside 2000 is better as all the info...

you'd just do so much better to go 64 bit. I'd allow at least 4Gb for the o/s.

if your server is new hardware then you will not need the /pae...

it's worth seeking out any high io queries, fixing them ( if they exist ) is a much better solution!

Mind it depends upon database size and so on too -...

I do much as you say, http://sqlblogcasts.com/blogs/grumpyolddba/default.aspx and select trending for details,

I have changed code and such for 2005 and there's some stuff on my web site too ...

well I think the official ms figure is 300 although I prefer a higher value. If the page life goes to zero then you're flushing the cache and that is...

that's really the wrong set of data and question. Why do you think you don't have enough memory?

I'd suggest you start with page life expectancy - this will give a...

just a point but 70million rows isn't that big!

You say you don't have the ability to use the tuning advisor - so what? you can still generate estimated query plans...