I use login authentication for all my DTS and job. But
recently my jobs have failed because the domain that
authenticates these logins are having trouble and that is
out of my control. So, I'm thinking about changing the
loging for the packages and jobs to a sql server login.
Here is the questions: What is the down side, if any, of
using the sql loging vs. windows authentication login when
executing DTS jobs?

In article <07f701c33fef$18bb2f40$a001280a (AT) phx (DOT) gbl>, Helena Silva
<silvah (AT) wellsfargo (DOT) com> writes
Good security practices dictate that you change your passwords. This
means you have to change all the connections in you packages, unless you
use some kind or parameterisation or abstraction to store the username
and password elsewhere.

If you have the opportunity to use NT auth I would recommend it. It
seems to be the MS preferred method, and it generally a lot less hassle.
Try and fix the domain issues if I where you.

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