The way you have it set up now, with two connections for source and destination, I would expect two imports to run in parallel.  As Jeremy said, if you have...

It looks like the package failed on DTSStep_DTSDataPumpTask_1, but there is really no way to know what caused it to fail until it happens again and you can examine the package...

Running parallel is the default unless you change the precedence of a task with Workflow. 

Greg

If the step names still match the task names, you can query sysdtssteplog looking for stepname like '%DTSExecutePackageTask%'.  This only works for packages that have been run. 

You might also...

David,

See my reply in this thread: http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=359&messageid=372463#bm377484

It includes a script for changing default schema to dbo.  This is the only way I've found to deal with the automatic naming...

Are you using DTS to import from Access?  If so, then yes, you do need a task for each table.

Greg

David,

You can't restore directly from a transaction log file, only from a backup of a transaction log file.  Your original plan listed making a Tlog backup to restore on the...

Steph,

Enable package logging in all your packages to get more accurate info about package failure. 

To enable logging, open the package in DTS Designer, select package properties, and the Logging...

Quote: We have to manually edit both the "Database Schema Names" (1 at a time) and the SQL LOGINS (1 at a time) and on the properties for each, change...

Table variables are automatically cleaned up at the end of the stored procedure that creates them so you're better off using real tables and dropping them when you're done using...

I think Enterprise Manager ran ALTER PROCEDURE in the background when you modified a procedure.  SSMS just makes it more obvious.

Greg

I'm with Adrian.  There isn't an easy way to do that.  Here are a thread and a script that I've referenced before that might help:

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=308151

http://www.sqlservercentral.com/scripts/viewscript.asp?scriptid=1613

Greg

Regarding scripting logins, sp_help_revlogin will script both SQL Server logins and Windows logins.  You can get it here: http://support.microsoft.com/kb/246133/en-us

Greg

I agree with Sugesh.  All the SQL 2000 to SQL 2005 migrations we've done so far have been done by scripting logins, jobs, and linked servers  and running the script...

At minimum, a user must own the job to be run and must have EXEC permission for sp_startjob in msdb.

Greg