For specific hotfix, you have to call PSS to get it.

You can search sqlserver.exe on Microsoft KB articls regularly to find out the hotfixes with build number.

Run Restore command, you can also move the files to other drives.

It depends. Most of hotfixes are for server but some of them are for client tools, for example, 8.00.819. Read corresponding KB before you apply it.

Any errors in errorlog?

Go to maintenance plan --> properties --> reporting tab --> enable "write report to a text file directory" and run the job again, go back to review...

Your original database server has one CPU only and queries will not be run in parallelism. Now you have new server with 2 CPUs, the query execution may be diifferent...

Try SQL Server security tools scan.

http://support.microsoft.com/default.aspx?scid=kb;en-us;813944&Product=sql2k

The errors in the errorlog.

http://support.microsoft.com/default.aspx?scid=kb;en-us;328197&Product=sql2k

In 7.0, The Severity level for same error is 18.

It has to be full recovery mode if you want to rollback evrything.

USE DatabaseName

GO

SET XACT_ABORT ON

go -- I added GO here and The setting of SET XACT_ABORT is set at execute...

The highest I have is 8.00.844. You are right these fixes are for specific purpose. If you don't face the particular problem, don't apply it. MS03-031 (8.00.818) is the latest...

Should be server\instance

"Is there a way that MSSQL can compress a backup while it is dumping it or after it dumps?"

No at all.

Try http://www.dbassociatesit.com/products.asp?prod=1

I believe you choosed "copy table and views from source database". instaed, you should use "Copy objects and data between SQL Server databases".

The view must be updatable. In order to make the view updatable, The view has to be created with INSTEAD OF Triggers and trigger will slow the performance in general. You also...