does your script include inline functions as calculations in the sql ?

If so I've seen this type of activity caused by functions. Why it does this on high performance systems...

if you get it right partitioned views work really well. You can create hierachies of partitioned views for searching without any problems.

What I did find with partitioned views is that...

I'll follow the microsoft recoemmendations - but I'd suggest a mdac update on the server to be worthwhile - miss matched mdac versions across clients always used to give me...

if you share stuff performance is rubbish. My experiences with vmware show it's ok in dev but absolutely not good for production.

To prove it's a disk issue monitor the i/o...

I'd suggest a read of Inside sql server 2000.

I hate maintenence plans, sysmaint.exe etc. with a passion!!!

Yup try issuing a sp_updatestats in a job step. Given a choice I always use the native dbcc / sp's in...

http://www.compman.co.uk/scripts/browse.asp?ref=450145

there have been a number articles on this site concerning this subject - information can be extracted from the sysperfinfo table.

you can get this info from sysprocesses if you're trying to get point in time figures - failing that if it's sql users then a count of syslogins. If you've...

I trust the password is not embedded in the proc?

Your question indicates a lack of some understanding of sql server but I assume the proc calls isql, osql, dtsrun or...

The most aggressive shrink is done by this command

dbcc shrinkfile(file_number) e.g. dbcc shrinkfile(2)

I'd make sure you're applied a manual checkpoint and maybe a dbcc updateusage(0) first.

the time to actually shrink...

how are you updating stats?

sp_updatestats or update statistics ?

( if you're using a maint plan I suggest you code the commands in tsql )

Be aware that technically update stats needs...

I recommend the purchase of this book

http://www.compman.co.uk/scripts/browse.asp?ref=450145

sorry - should have also added that it's not a good idea to mess with system tables and such - can open a can of worms, you should be aware...

as far as I remember from doing a similar execise ( many years ago ) the column has distinct rights for sysadmin/securityadmin only. Therefore you must alter the column permissions...

I'd suggest you add some more disks, running a sql server on one disk will not be good, it doesn't matter how much data cache you have if the disk...