Peter, I think so. I just checked. I do *not* see a password stored in my registry when I try to switch authentication to SQL Server authentication. IF you can switch to NT authentication (which I'm guessing you can't, but...), then the authentication is handled behind the scenes...
Regards, Jeff > > Hi, > > Follow-up. So is the error I get 'working as designed'? In other words is > SQL authentication without explicit user and password parameters in the > connect() not supported? > > If not, I would like it to since hard-coding the user/password in > my script > or as part of the environment are not solutions I like. > > Pete > > -----Original Message----- > From: Levine, Peter W > Sent: Thursday, September 05, 2002 1:58 PM > To: 'Jeff Urlwin' > Subject: RE: why do I need to supply user & password > > > Hi, > > I'm using SQL server authentication not NT authentication. If I levae out > user and password I get this error: > > > ERROR: [OpenLink][ODBC][SQL Server]Login failed for user '(null)'. Reason: > Not associated with a trusted SQL Server connection. (18452) > (SQL-S1000)(DBD: db_login/SQLConnect err=-1) > > Pete > > -----Original Message----- > From: Jeff Urlwin [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 05, 2002 1:49 PM > To: Levine, Peter W; [EMAIL PROTECTED] > Subject: RE: why do I need to supply user & password > > > > > > > > > Hi, > > > > Why do I need to supply user name and password with > DBI->connect() if I am > > using DBD:ODBC? This information is already supplied in the DSN? > > > > my $DSN="dbi:ODBC:sqlserver_dsn"; > > my $DBI_USER="Why do I need this?" > > my $DBI_PASS="Why do I need this?" > > > > $dbh=DBI->connect($DSN,$DBI_USER,$DBI_PASS); > > Err -- you don't -- I don't think -- at least I don't need to, > here. But my > SQL Server is configured for NT authentication. what happens > when you just > $dbh=DBI->connect($DSN);? > > Jeff > > >
