as long as your client tools have sp2 applied there are some custom reports which may help you http://www.grumpyolddba.co.uk/monitoring/Creating%20Custom%20Reports%20for%20the%20DBA.htm

don't you have another server to use?

I've found the DTA will fail around 50% of the time I use it. I've never given it much thought and my general view is that you can extract the...

I'd probably say it depends! a 2000 db in either mode is still going to be the same database - it's not as if the convert chnages the sql. I've...

a basic profiler will tell you this, include cpu cycles, reads, writes and duration - just look for what does the big numbers, it'll all be linked - usually it's...

I think you'll find these were removed from SQL 2005.

Your option is to write your own proc in the clr to do whatever this proc call did.

you could use litespeed ( or redgate's product ) this gives smaller files plus quicker backups and restores - may help where bandwidth is restricted.

faster arrays will also...

allough this is a sql 2000 script it works in sql 2005 too and gives a more readable output of locks - you'd have to suspend your query by using...

if your proc call is not the same case as your proc def then you'll get a cache miss event. What's more worrying is that in a highly concurrent environment...

you didn't mention what raid you're using - if it's 5 or 6 then write performance is rubbish!

I wrote this post which shows the basic calcs involved. It needs a rewrite but am waiting to configure some arrays for actual testing.

http://sqlblogcasts.com/blogs/grumpyolddba/archive/2007/01/26/how-fast-is-a-disk.aspx

one final point, and I don't want to sound holier than you, but you should have planned all the hardware and structures way way back before you got to the...

oh as to filegroups etc. I've seen too many poor implementations of filegroups ; you MUST understand your data usage to make effective use of filegroups. Make sure you do...

to be honest it's far too general a question to answer. I've actually found that etl / DW prcesses are most affected by spindle and array count. Just to explain,...

I've seen the proc cache much bigger in x32 sql2005 - I posted some rdl files you can use to look at buffer and proc cache http://www.grumpyolddba.co.uk/monitoring/Creating%20Custom%20Reports%20for%20the%20DBA.htm

You'll still struggle...