Do you know the selectivity of the various fields? If some are more selective, i.e., a query will return very few rows, then these are great candidates for the first...

If the drive structure is the same, restore master and msdb after you've installed QSL on the new machine. If not, you need to backup all your DTS packages manually....

prerelease: http://www.sqlservercentral.com/columnists/WFillis/analternativexmlsolution.asp

dtsrun will execute procedures. You will need to redistribute some DLLs for this.

Should be in the cube poroperties or definition.

I'd dig into the data. If it's returning things you don't expect, I usually look for data problems.

Above is a great explanation.

Data Compare from Red Gate. Cheap, easy and works well.

http://www.red-gate.com/SQL_Data_Compare.htm

Are you bulk inserting? If not, you can get teh value first and then include it in the insert statement.

Server side traces use less resources, but you have to worry about file or table contention on the disks. You can always transfer the data to a remote server on...

Since they log OR the data are required to restore, I don't worry about this. dbcc will check this.

Haven't seen anything like that.

If you move the clustered index to another filegroup, it moves the table.

Yep, forgot about that one. Definitely be sure you script everything out in case you forget somthing and need to find out what it was. Permission is the main one...

No way to do it now, no plans, but we'll consider it.