The only discounts I've heard of are volume licensing. http://www.microsoft.com/sql/howtobuy/editionspricing.mspx

Neither of those options works for me. When I select 'Delete', I don't get to choose a version to delete. The package is deleted. I don't even...

You're right. I haven't found a GUI option for deleting DTS package versions. All versions are stored in msdb.dbo.sysdtspackages so you can find older versions with T-SQL, something...

It depends on how packages are run in the jobs. If the DTSRUN command is unencrypted, you can query msdb.dbo.sysjobsteps to find the name of the package run. ...

You can monitor with Profiler. See "Event Classes" in BooksOnLine for lists of events that can be monitored.

Data Transformation Services is called Integration Services in SQL 2005 so look for "Integration Services Project" in BIDS.

SSIS is the the tool to use for importing data into...

I can see "Start without Debugging" on the Debug menu but I can't find a way to add an icon for it.

I've been using this query:

select recovery_model_desc from sys.databases where name = 'master'

The sys.databases view is in every database.

I guess you could post your statement in the "Scripts" section. See...

If you read the articles suggested by Anirban Paul, you'll understand that you can't eliminate the use of transaction logs in SQL Server. You should use the simple recovery...

I've moved objects between databases by either scripting them in Enterprise Manager (including foreign keys) and running the scripts in the destination database or by using the Copy SQL Server...

I agree with Jay. While checkpoints don't actually "pause" the package execution, they allow you to restart it from the point where an error occured without having to rerun...

The Execute SQL task runs T-SQL commands such as you might run in a query window connected to a database. The Execute Process task runs an executable Windows program...

Well, what doesn't work? Do you get any error messages, anything in the job history or the package log? More information will get you more help.:)

Genius?:blush: I just had the same experience before you did, did the necessary digging, and wanted to pass it on. Thanks for the compliment, though!

Good advice from oraculum and a good article reference from Ellis. Check out the articles here for more advice on moving to SQL 2005: http://www.microsoft.com/sql/solutions/upgrade/default.mspx