I have a job that kicks off a stored procedure. The proc in turn kicks off 25
DTS packages with scripts like

execute master.dbo.xp_cmdshell 'dtsrun /Smtcntsql02 /NNavision_TT_Vendor /E'

for a while, we were using the /U and /P switches with the sa account and
password. The packages still run OK with the /E switch for integrated
security, but a trace on the server shows that the connection is being made
with in the context of the sa account. We are trying to eliminate all
references to sa in DTS. Why would it still use sa even though the /E is
specified?

I suspect that the job still runs BECAUSE it runs under sa. I bet once I get
it to run under integrated security, it will fail. but that's OK. I can fix
that.

Any suggestions would help.

Thanks

Todd C

How are the connections in the dts packages configured? If the connection is
set up to authenticate with the sa user, then executing the package with /u +
/p, or /e will not override the connection settings.

"Todd C" wrote:

Ah, missed that one. Thanks.
Yes, all the connections in the DTS packages themselves are using database
level security.

"Matt" wrote:

Hello Todd,

The /E switch to the DTSRun command is simply saying that to retrieve the
package from the server you want to use Windows Authentication. It has nothing
to do with what the connections inside the retrieved package use.

Allan