dts from command line

if a user runs a dts package from a command line say something like this
C:\>dtsrun /s ServerName /u username /p P1l0t /n DTS_Package
using that /p password switch is the passwork example above P1l0t saved off
somewhere in a log file?
same question for if the command fails.
thanksNo...it won't report or log the password that was used.
-Sue
On Tue, 11 Oct 2005 15:05:05 -0700, "jason"
<jason@.discussions.microsoft.com> wrote:

>if a user runs a dts package from a command line say something like this
>C:\>dtsrun /s ServerName /u username /p P1l0t /n DTS_Package
>using that /p password switch is the passwork example above P1l0t saved off
>somewhere in a log file?
>same question for if the command fails.
>thanks|||thanks sue
"Sue Hoegemeier" wrote:

> No...it won't report or log the password that was used.
> -Sue
> On Tue, 11 Oct 2005 15:05:05 -0700, "jason"
> <jason@.discussions.microsoft.com> wrote:
>
>

DTRUN command

Hi.
I have a sql job that is failing, while looking why the job failed, In the
preperty Step- tab /command windows: has DTSRun /~ this long address
following .
I just started this gig and I'm not sure what is being called. how can I
found out what procedure or process this job was calling by looking at the
address?
Thanks in advance.Correction: the command is DTSRUN
"ITDUDE27" wrote:
> Hi.
> I have a sql job that is failing, while looking why the job failed, In the
> preperty Step- tab /command windows: has DTSRun /~ this long address
> following .
> I just started this gig and I'm not sure what is being called. how can I
> found out what procedure or process this job was calling by looking at the
> address?
> Thanks in advance.|||The DTS package scheduling wizard encrypts DTSRUN parameters. You can see
the package name retrieved from msdb by using SQL Profiler while DTSRUN is
executed. There are also cracks for the DTSRUN parameters you can find on
the web.
IMHO, it's better to code DTSRUN parameters in clear text unless you have a
reason to do otherwise.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:E8CB6912-5819-4F0F-A81E-5C770AA163FD@.microsoft.com...
> Hi.
> I have a sql job that is failing, while looking why the job failed, In
> the
> preperty Step- tab /command windows: has DTSRun /~ this long address
> following .
> I just started this gig and I'm not sure what is being called. how can I
> found out what procedure or process this job was calling by looking at the
> address?
> Thanks in advance.

DTRUN command

Hi.
I have a sql job that is failing, while looking why the job failed, In the
preperty Step- tab /command windows: has DTSRun /~ this long address
following .
I just started this gig and I'm not sure what is being called. how can I
found out what procedure or process this job was calling by looking at the
address?
Thanks in advance.The DTS package scheduling wizard encrypts DTSRUN parameters. You can see
the package name retrieved from msdb by using SQL Profiler while DTSRUN is
executed. There are also cracks for the DTSRUN parameters you can find on
the web.
IMHO, it's better to code DTSRUN parameters in clear text unless you have a
reason to do otherwise.
Hope this helps.
Dan Guzman
SQL Server MVP
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:E8CB6912-5819-4F0F-A81E-5C770AA163FD@.microsoft.com...
> Hi.
> I have a sql job that is failing, while looking why the job failed, In
> the
> preperty Step- tab /command windows: has DTSRun /~ this long address
> following .
> I just started this gig and I'm not sure what is being called. how can I
> found out what procedure or process this job was calling by looking at the
> address?
> Thanks in advance.

dtexec?

i am using dtexec in command prompt

it always prompt the path is not valid and error is 0x80070057

below is what i input

dtexec /dts c:\ssis\***\***.dtsx

what's wrong? thanks

dtexec /f "C:\ssis\**.dtsx" can working

so sorry

|||

try this, it should generate a log for you so you can view detailed errors:

dtexec /f "C:\SSIS\YourPackage.dtsx">>C:\SSIS\YourPackage.LOG

DTExec: The package execution returned SUCCESS but had warnings

hi!

i am trying to execute through command line the following:\

dtexecui /SQL "\ArchiveMain" /SERVER "SE413695\AASQL2005" /WARNASERROR /MAXCONCURRENT " -1 " /CHECKPOINTING OFF

I am actaully creating an archiving package.

1. All it does is get some data from the Table.

2. creating directory and set usedirectoryifexist = true

shows some warning when i run that directory already exists cos i don't want to create new one i want to use the existing one.

3. actual archiving to get call to another package for archiving - warning while running the package that parent variable is missing

The pacakge seems to run while i execute it thorugh command prompt but i get this message

DTExec: The package execution returned DTSER_SUCCESS (0) but had warnings, with
warnings being treated as errors!

Thanks,

Jas

Your description in line 2 indicates you are creating and setting the directory, is that correct? I see the set command but I don't see the create command. If you are using both a create and set command you should remove the create command because the directory already exists, and then try running it.

You could also include some sort of "if not exist then create" command for your directory in case it was accidentally deleted somehow, then it would be recreated before being set.

DTExec Can this thing run in the background?

I have a DTS Package that I am running from a command line via .bat file. Does anyone know if there is a command to have the command window minimized or running in the background? I used the /Rep N command but that still leaves the window open until the package has executed.

Thanks!

Try the start command it may have some options that are useful for you.

If using a bath file, then you cannot get away from having a command console session open, that is the nature of what you are doing, unlress you use a separate user session, such as you would get with a service.

|||

Thank you! The Start helped at least minimize the window! Thanks again!

DTEXEC /SET

Hello,

I have a command line as following, with DTEXEC to launch the execution of a package and to set a value (13335) of an user variable called CIB (string type):

dtexec /f c:\temp\PackageInsert.dtsx
/set \Package\DataFlowTask.Variables[Utilisateur::CIB].Properties[Value];13335

But I have got an error message saying that the object is not known in the package. My variable does exist in the variable window of the dataflow part.
Thank you for telling me what to set so that the variable can be set by the command line.

Regards,
Marie-Thrèse

I suspect the problem is the path in the set statement, check that the variable is scoped to the data flow task and notthe package for example. To help find the correct path, use the configurations wizard to set the variable value property, and just copy the path you get in there.

|||

Thank you so much for your advice. How should I do to use the configurations wizard, in order to get the correct path ?

|||

Marie-Thrèse wrote:

Thank you so much for your advice. How should I do to use the configurations wizard, in order to get the correct path ?

Every time you set up a configuration you have to tell it which object property you are talking about. On the last screen of the wizard the property paths are displayed.

-Jamie

|||

Thanks a lot Jamie for your advice

DTEXEC /CONFIGFILE Option

I have the following command which uses the /CONFIGFILE option:

master.dbo.xp_cmdshell 'dtexec /DTS "\File System\Packages\MyPackages\MyPackage" /SERVER "MYSERVER" /CONFIGFILE "C:\Program Files\Microsoft SQL Server\90\DTS\Packages\MyPackages\customersite.dtsconfig" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING V '

When the package runs, one of the first things it reports is that the configuration file, 'customersite.dtsconfig' cannot be found:

...

Description: The package is attempting to configure from the XML file "CustomerSite.dtsConfig".

...

Description: The configuration file "CustomerSite.dtsConfig" cannot be found. Check the directory and file name.

...

Description: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed.

The package hapilly executes (and, somehow does grab the appropriate values from config (in this case, it is the SQL Login passwords).

Can anyone provide some insight into this or is this a bug that should be ignored?

I strongly suggest that you use SQL Server Agent stored proceedures instead of xp_cmdshell.

It's easier and more secure.