I assume you'll be using x64 - I'd suggest x32 would be a poor choice. I'd suggest as much memory as possible to a degree this wil be important...

not sure I can fully answer your question as I'm going through a similar review on a new sql 2008 cluster. I never allow builtin admins a login so that...

It'd take a small book to answer that fully. Have a read in BOL or buy the excellent "inside sql .... " books. There is always locking by default in...

can't help with std edition as I only use enterprise. on-line rebuilds may be tricky if the index is large and a volatile table - it's possible your index may...

single column indexes rarely have the desired effect. You'll need an index to cover the three columns in the where clause as a first step.

make the first column the most...

I'm not sure it's the role that has changed so much - more people having the job title DBA who clearly are not. Whilst the breadth of SQL Server...

files usually get used in a round robin way - it used to be that if you didn't create your files all at once then the extra files were ignored....

nah - shouldn't be the case. Been runing 16 cores for ages without issues. Get the performance dashboard and find out what queries are using cpu - or use process...

by my maths it's 1 million rows total.

Add a where clause to your query and index the where - you'll find it goes quicker.

If the filtering is being done in...

on a x64 system you can run without a page file. If you have a page file then windows will use it no matter how much resource you have available...

you are not leaving enough memory for the o/s and other processes, esp with all those cores. I'd suggest you set max memory to no more than 40GB, ideally about...

you can't directly map cpu% ( e.g. from perfmon ) to a specific sql query very easily.

try this

--This query will list the top 50 queries which used the most CPU...

actually I probably didn't explain myself very well .. I'd expect this type of behavior and without "seeing" the code running in front of me it's hard to make a...

well as the number of possible rows can vary according to the parameter the query would likely vary quite a bit, I have an example which generates three different...

without wishing to be too unkind, if you're asking the question you're the wrong person for the job.

I suggest you might get hold of the SQL Server 2000 performance tuning...