In execute sql task you have to use backup command...

BACKUP DATABASE <DB NAME> TO DISK = '\\SERVERNAME\D$\DBNAME.BAK'

In another execute sql task use restore command check BOL for syntax

RESTORE DATABASE <db...

Not yet....

Top 10 Reasons to Install Windows Server 2003 SP2

http://www.microsoft.com/technet/windowsserver/sp2/top-reasons.mspx

It all depends on $$$...

Those who can spend more they use Raid 0+1(10) for data and log files...

Read the following thread...

http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=16995

There is no easy way to do this...

Read the following article to get the solution....

http://www.sqlservercentral.com/columnists/pibison/alteringacolumnonareplicatedtable.asp

I think Only option will be ALTER TABLE command for each table..

Check the following blog...

http://blogs.msdn.com/sql_protocols/archive/2005/09/28/474698.aspx

I don' t know much about CR but lowest leve of ISOLATION leve in SQL is READ UNCOMMITTED where default is READ COMMITTED...

You may need to set the connection for...

Read BOL topic "Reducing the Production Server Tuning Load "

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

Tuning a large workload can create significant overhead on the server that is being tuned. The overhead results...

Thanks for the tip

You can run the sql profiler to see what is happening behind the scenes when copy database wizard runs...

But if I am not mistaken, copy database wizard detach the database...

Declare @Dt_DateAndTime Varchar(30), @dbname sysname, @file sysname

select @Dt_DateAndTime = convert(char(8), getdate(), 112)+''+ Replace(convert(char(12), getdate(), 14),':','')

select @dbname = 'master'

select @file = 'c:\'+@dbname+'_'+@Dt_DateAndTime

select @file

backup database @dbname to disk =  @file

with...

Create a dts package with two EXECUTE SQL task.. one should run the backup on the source server and second should run the restore on destination server...

Note: Database Backup file...

You can download Books Online from the following link but not tools...

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

I believe SQL server Management Studio Express is different than the regular one...

You can't set TRUNCATE LOG ON CHK POINT through EM in 2000 and the same way in 2005....but it is included in recovery model as Jeff mentioned...

Where as you can...

Reason could be big transactions... check it out if you have any large sinle transaction...

ex: If you have table with 10 mil rows and running delete against it instead of...