I don't think there is any other easy way than using dts/ssis/bcp...

You can configure SSIS/DTS to process parallel threads to improve the peformance...

Based on the error you have blocking issue going on...

did you check if there is any blocking happening during this?

How to monitor blocking in SQL Server 2005 and in SQL...

Chere if there are any open transactions...Did you do any reindexe or index defrag against this db?

Did you try shrinking it using DBCC SHRINKFILE command? If not try it...

Check the...

It can be different reason to use two data files...

1. performance

2. disk space

etc...

Yes, you can merge then...

If the files are on two different file groups then move the data and...

How to monitor blocking in SQL Server 2005 and in SQL Server 2000

http://support.microsoft.com/kb/271509

Check the following...

http://msdn.microsoft.com/en-us/library/aa933149(SQL.80).aspx

http://technet.microsoft.com/en-us/library/ms143432.aspx

You can't restore any database including system if the sql is not running...

You need to start the sql in single user mode restore master...

make you installed the same as before...

Before SP2 cleanup task was not working properly but there is a cleanup task befor SP2 also...

You can use dbo.xp_delete_file procedure to old files...

https://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=718788&SiteID=17

Instead of using SSMS...use Query window to attach the db...

If you have already deleted the log .ldf file then you try with

ATTACH_REBUILD_LOG option...check BOL for syntax...

CREATE DATABASE ...

ATTACH_REBUILD_LOG

I...

yes I believe...

http://www.microsoft.com/technet/prodtechnol/sql/2005/msde2sqlexpress.mspx

SQL Agent should not lock the files, if it is locked then your backup job is still running...

Did you try closing the open files instead of restarting the sql server?...

You can't move using detach/attache method...read the following article and follow the directions...

Msdb can be moved using restore method and make sure sql agent is offline when you restore msdb...

How...

As long as it gets replicated to ServerB...

For disconnected servers...it is advisable to use merge replication...

It applies to all Standard edition too but in your case you have many instances...

How you want to take the advantage of /3GB AND how do you want to configure...

You can use Merge replication too...

http://www.sqlmag.com/Article/ArticleID/50532/sql_server_50532.html