using DTSRUN to execute a package, had some truncate table statements in an
sql steps. Truncate reserved for dbo use. The user executing the package is
not the dbo nor alias, so it should fail. But in once specific recreatable
instance, is does not fail.

If I run the package from my machine, even though I am specificying the /U
and /P switches, it runs fine (it should bomb out since the user specified
is not dbo), but is apparently using an implied trusted connection for some
pieces of the package. If I run it from a machine where the logged on user
is not in the admin group the behavior is as excpeted.

In article <#S88m4cuDHA.2168 (AT) TK2MSFTNGP10 (DOT) phx.gbl>, Jeff Block
<jblock (AT) REMOVETHECAPSANDINVALIDfirstlook (DOT) biz.invalid> writes
When you use the /U and /P DTSRUN switches this is specifying the
credentials used to connect to SQL Server to load the package only.
This does not effect the connections or tasks inside of the package, so
if the connection uses integrated security the connection mad during the
package execution is still made using the credentials of the logged on
user running the DTSRUN program.

Does this explain the behaviour?

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org