That's just an example on how many "ifs" have to happen in order to start considering a 10% fill factor

have a look at OPENXML ... BUT you must use a TEXT variable not a varchar(8000)

I think that it requires service restart

I don't know what to do. There is more about it, management, political, etc.

Fire the Boss

Did you noticed how many "ANDS" you wrote in one sentence ?

This is really funny .....

if this is SQL Server 2000 you should apply latest service pack.

I have not found an easy way out of that one

Sorry for the bad news.

My first attempt would be to run SQLIO or SQLIOSim on both to verify throuput of the drives... I have had controllers "surprises" many times.

Secondly you mention "RAID5" vs "RAID10"...

I believe you have an architectural Issue. Connection pooling is a must and if you don't use it you will hit a bottleneck.

You must ensure that all is being pooled....

Very Tricky but doable (in some cases)

---=====================================

--- sp_helpdb returs two resultsets

---====================================

create table #t1 (

namenvarchar(24) null,

db_sizenvarchar(13) null,

ownernvarchar(24) null,

dbidsmallint null,

createdchar(11) null,

statusvarchar(340) null,

compatibility_leveltinyint null)

insert into...

Ooops sorry. I didn't followed the link

I see you have a "NOT FOR REPLICATION" parameter setup on the identity column. So I am guessing this came from on a "subscriber" database. Anyway You can run

DBCC CHECKIDENT...

You should grow your files "manually" at an appropriate time, never using autogrow (which should only be there as a fail safe feature)

You need to monitor how "full" are...