Have you tried starting sql server from the command line

with the

-dmaster_data_file_path

-lmaster_log_file_path

-eerror_log_path

parameters ?

example :

sqlserver.exe -dC:\MyNewDBLocation\master.mdf -lC:\MyNewLogLocation\master.ldf -eC:\MyNewErrorLocation\ERRORLOG

Since L & E seems to be unavailable (see event viewer)

Part 1: inserting in a new table

Insert into newtable

(Application)

select ApplicationX from tableY

where ApplicationX is not null /*blank checking

and application1''

and not exists

(select * from newtable where application=ApplicationX ) /*dupe checking*/

repeat...

Have you checked the event logs?

off topic change

FROM vw_Referrals_Grouped

to FROM dbo.vw_Referrals_Grouped vw_Referrals_Grouped

to prevent recompiles

Having the IIS seperated will indeed lessen the contention.

Is there another candidated for the clustered index? Datetime and 10 ints seems to be large. Exchanging for a non-clustered index?

Any possibility...

Also try to match the datatypes for index usage. If active_flag is a bit-field use active_flag = convert(bit,1)

You could try to replace the not in   to not exists . With in it has to fetch all records before comparing, with exists it can cease fetching if one...

Most likely splitted. Why sql server would move 10gb tables as a whole because the mdf suddenly got full.

Perhaps you could pass the subheader as a parameter as well.

Is this like

Questionnaire

Header

Header_level2

Header_level3...

?

a wild guess, do both tables have a primary key or unique index?

Any reason why you wouldn't use 10k or 15k rpm drives instead of 7200 rpm's except the cost?

Try using (not) exists instead of (not) in. The exists halts when it finds one record, in requires finding them all before comparision.

Have a look at

http://www.sql-server-performance.com/sql_server_log_shipping.asp

to setup logshipping.

Replication is supported in the standard edition. Log shipping can also been done by manual implementation.

The only reason so far I would like to upgrade to enterprise is it can...

Perhaps the vendor knows if the systemadministrator rights are required ( or only db_owner rights).

You could also explain this huge risk to the management side.

(Someone changing the password ->...