DTS - how to backup and restore the DTS script?

I recently started to use DTS to do some of my database maintenance works. May I ask how do I backup those DTS scripts and how do I import them back?

I can find the "Save As..." function and it allowed me to save the script to bas or dts file. But I cant seem to find any function for me to restore that saved file to the SQL Server.

Please help.I got this from a Microsoft support Webcast, "It really depends on where you're storing your DTS package. If the package is stored as a file, if you store it on MSDB, backing up to MSDB would take care of it." The second link is from Darren Green SQL Server MVP. Hope this helps.

http://support.microsoft.com/?scid=http://support.microsoft.com%2Fservicedesks%2Fwebcasts%2Fen%2Fwc120500%2Fwct120500.asp

http://www.sqldts.com/default.aspx?242

Kind regards,
Gift Peddie|||You can import a dts package by right clicking on data transformation services on left side of the screen. Then you click on the option 'Open package'. In the next screen you can select the package.|||

Hi,

That's OK that we can open the package and work on it and will save the package. BUT when we save the package it's not saving in the SQL server its saving in the same file,

So i want that How to get that file in my sql server so that i will not open and work on the file again and again. If i'll got this package in the sql server then i'll not need to open this DTS file again and agian. So how to do this.

the basic i want to ask abt DTS is.. HOW TO BACKUP DTS AND HOW TO RESTORE DTS.?

dtexec Return Success BUT Not Run!

I've created a Maintenance Plan in Microsoft SQL Server Management Studio (Sql Server 2005 SP2 + Windows Updates) and currently trying to execute it via the dtexec command line program.

The problem is that it reports that it executed the Maintenance Plan but it never actually executes the Plan. The data isn't updated and the CPU and hard drive I/O reports nothing happening.

I've checked the argument lists but I don't think I've missed anything...?

On the Sql Machine itself, I run the command line as follows:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\V2Admin>cd \
C:\>dtexec /SQL "\Maintenance Plans\GPI Update" /Server V2SQL\VC2 /User sa /Pass
word XxXxXxX
Microsoft (R) SQL Server Execute Package Utility
Version 9.00.3042.00 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

Started: 11:29:43 AM
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 11:29:43 AM
Finished: 11:29:44 AM
Elapsed: 0.375 seconds

C:\>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>I don't understand why you are running using DTEXEC, have you tried to schedule the package that is created using SSIS?|||We are running DTExec as we want chain together and run other processes outside as Sql Server as well, but want to use the History tracker of Sql Server's Maintenance Plans.

The Sql Server Maintenance Plan tasks are kept with Sql Server and the external processes are kept with their relevant tools.

We need to run both together which is why we need to call DtExec.

At the worst case scenario, we can simply run SqlCmd and execute the desired functionality, but that is asking for problems as there would then be two locations to maintain the Maintenance Tasks Sub-Plans.

Not a smart move in any operations manual!
|||

Schedule a maintenance plan and look at the arguments to dtexec in the agent job step. You will find that the subplan that contains your job steps is enabled from that command line. If you just run a maintenance plan without so enabling the subplans, all are disabled, and nothing runs, as you have confirmed in your scenario.

jkh