Two completely different things.

A database snapshot is used to get a point in time view of a database for things like end of month reporting.

A snapshot backup uses VSS to backup...

Switching from ODBC to OLEDB (especially if you are using Access as a front end) would be a good start to increase performance.  SQL 2005 treats ODBC as a legacy...

Check the date entries in Oracle for invalid SQL Server dates.  I think Oralce uses a 10 bit and SQL Server uses 8 bit, so you could have dates that...

A few things to check:

If you have a firewall between the developer and the sql server:

open a port for SSIS on the firewall (3882 and an additional port for the...

You need to pay attention to the difference between cursors and variables.  Answer B was "Release the resources from a cursor", so it is correct.  The answer would not have been...

Definitely use the table with a stored procedure to avoid injection attacks.

Profiler is running by default.  Turn of the trace and profiler and the processor time should return to normal.

The "migrated" DTS packages are simply placed into a SSIS wrapper that can run DTS packages - kind of a translator.  We have moved our DTS packages over using the...

This is because it switches out of READ UNCOMMITTED about halfway through. Use sp_who2 in query analyzer instead. If you're interested in locking/blocking check out http://www.sommarskog.se/sqlutil/aba_lockinfo.html for a good stored...

You still need to add the ID to the proper dts role on the msdb database.

The SSIS Import wizard in 2005 is only for tables and views.  Why don't you just migrate your 2000 DTS to 2005 and use the exisiting package?

The real question is if you have heavy I/O why in the world would you create a snapshot in the first place.  The copy-on-write would probably put you over the...

It looks like your codepages are different between the Oralce and SQL servers.  Make sure the codepages match to get the correct data.  If you can't change the codepage on...

Don't use the native client - use the sql server OLEDB provider instead.  Also make sure you have SP1 and the post SP1 rollups for SQL 2005.  I think it shows...

Right-click the package in management studio and choose export.  Change from SQL Server to File and then save the package.  You can then open the package using File - Open...