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 ->...

nr 2.

You can use the inner join. The results for invoice,lineitem will be null if no matching customer is found.

Thanks again, it worked out.

Script:

DECLARE @Tablename nvarchar(128)

DECLARE @UserName nvarchar(128)

DECLARE @ConcatName nvarchar(128)

DECLARE @DatabaseName nvarchar(128)

CREATE TABLE #Databases

(

Databasenaam nvarchar(128)

)

CREATE TABLE #temp2(

 rec_id  int IDENTITY (1, 1),

 username varchar(128),

 table_name varchar(128),

 nbr_of_rows int,

 data_space decimal(15,2),

 index_space decimal(15,2),

 total_size decimal(15,2),

 percent_of_db decimal(15,12),

 db_size  decimal(15,2),

 dbname...

Thanks for the suggestion, I'll try that one out.

The second one could be faster because the server can check its statistics more quickly.

I would suggest using inner join instead of Title T, TitleSearch TS             

Select ...

from title T inner...

Can you log on as the user on the database using enterprisemanager, queryanalyzer? The securityid of the user in the database might be different than the one in the master-database

Beware that RAID 5 is slower for writing. Consider RAID 1+0 instead.

Have you tried

execute master.dbo.xp_cmdshell 'c:\project.exe'?

Have you checked http://support.microsoft.com/kb/839279?

The tables must have some unique index/primary key,  which will act as row-identifier, to perform a distributed transaction (like inserting in another server)

If one of the servers runs on Windows...

Both tables have a primary key?