- start sql-profiler to capture a sample load and examine it for table and or index scans.

- do you have db-maintenance-jobs in place ? to reduce fragmentation

- for the data-part the is no difference for 32 or 64-bit OS / SQLServer

- however if you are using the CLR, I guess it would be nice to avoid...

- I wouldn't advise a trigger for this purpose ! (start job) because if the start job fails, your transaction fails !

- I woudn't advise a trigger for this purpose...

this could be your test-script ....

print '00 Creating dbo.test';

go

create table dbo.Test (col1 int not null )

go

print '01 inserting rows into dbo.test';

go

insert into test values(1);

go

print '02 Selecting from unqualified table test';

go

select...

I guess that's what the "true" parameter is for in

use exec sp_changedbowner 'sa', true.

You can use sp_changeobjectowner @objname = 'oldowner.object' , @newowner =  'newowner'

making this #é&() mistakes, you can immagine the rest of my day

Still early on the day

SELECT BS.database_name

, BMF.physical_device_name

, BMF.device_type   

FROM msdb.dbo.backupset BS

INNER JOIN  msdb.dbo.backupfile BF

ON BF.backup_set_id = BS.backup_set_id

INNER JOIN msdb.dbo.backupmediafamily BMF

on BMF.media_set_id = BS.backup_set_id...

SELECT BS.database_name

, BF.physical_name  

FROM msdb.dbo.backupset BS

INNER JOIN  msdb.dbo.backupfile BF

ON BF.backup_set_id = BS.backup_set_id

WHERE BS.database_name = 'MyDB'

- If you're using a "sqlserver maintenance plan", it will optimize _all_ objects of the selected databases.

- verify that they don't drop and recreate their tablesat runtime ! because then...

- your sqlserver-serviceaccount or your sqlagent's (if you're using a job) need read-auth for the .bak-file

- you as sql-user ... you need to be at least db-creator or database-owner...

This is one of the enoying things where they use actual "work"-tables in stead of #-temp-tables.

So the create them on the fly, use them and drop the at the end...

use exec sp_changedbowner 'sa', true.

Keep in mind this is one of the flaws of EM. You'll have to disconnect an reconnect to see the correct results.

If you want to restore using EM, you'll need to have the backup-file(s) at the server itself.

If your bak-files are on a remote location, you can use e.g. QA and...

check http://www.databasejournal.com/scripts/article.php/1496451

to apply the rename of your windows server in your sqlserver instance.

According to my biztalk-admin changing the biztalksettings to connect to the new servername should be a peice...

- Oracle does not have locking, it has versioning ! Different concept.

- SQL2005 Snapshot isolation level mimics this behaviour.

maybe these art. clarify a bit :

http://www.databasejournal.com/features/mssql/article.php/3560451

http://msdn2.microsoft.com/en-us/library/ms130975.aspx

http://msdn2.microsoft.com/en-us/library/ms189050.aspx