in general terms the only thing I can see user owned objects are good for is setting complex permission questions in the mcdba tests!!  Ownership becomes more important in sql...

Yes I should have included Kimberly in that list, better still if she or Kalen are running any courses/seminars get booked on to them double quick.

 The extended procs still have access on 2000, it's on 2005 the security has been tightened on, as I say you can alter the permissions in surface config.

Don't create multiple filegroups on the same disk/array unless you require a read only filegroup, you'll probably degrade performance.Multiple files are different however.

Check out BOL, msdn, technet and the article...

If the result set is more than a few rows chances are you'll get index scans rather than seeks - this is why such questions about tuning queries are difficult...

Bookmark is better than a scan, however:-

• I suggest you search sql server central for articles on indexing
• Read BOL
• Check out Technet and msdn
• Buy the inside sql books - 2000 is in...

• I don't use it for rebuilding indexes or stats.
• I view extract worst performing for optimisation
• I view table growth/ useage of text columns and will look at indexes and sizes on...

I actually think that the situation arises far further back in education. I'm not a great lover of the ( english ) eduction system, an obsession with statistics has lowered...

I blogged the diffs in raid performance  ( see my earlier post ) ,

http://sqlblogcasts.com/blogs/grumpyolddba/

 largest scssi disks currently are 300gb so for 1 TB you'd need 8 disks in raid...

Going back to your original post - do you have a problem with the cpu usage ?

as I said you must always qualify objects ..

when you create a proc you should define as:-

create proc dbo.myproc

as

then when you script you get ownership - as I said before,...

I don't have such a table/database to hand to test on but I just ran a dbcc on the largest table in my test db on a single socket dual...

I don't know how many cpu's you have but why shouldn't the cpu spike ?  If you have one cpu I might expect this. That's why dbreindex should be considered...

I'd also look into what caused the growth anyway - maybe the job needs to be batched or include checkpoints. I also beg to disagree about default location of tempdb...

beat your users hard around the head until they learn to always qualify an object, it's best practice anyway, so teach them < grin > If only I could remotely...