Re: DSNless SQL Authentication to SQL2000 database - defaulting to Integrated login

#1

Meh (meganhudson (AT) today (DOT) com.au) writes:

Quote:

I'm using a DSNless connection in a perl script (using the DBD::ODBC
package) to connect to a SQL Server 2000 database. I'm using SQL
Authentication, however whenever the connection goes through, it is
actually ignoring the uid and pwd being sent and instead trying to use
NT Authentication. I have tried adding Trusted_Connection=no to the
connection string, but this makes no difference.
The SQL Server I am connecting to is set to SQL and Windows
authentication, and I can't use NT authentication to connect. In all
documentation I've read, it implies that the presence of the
parameters uid and pwd will force it to use SQL Authentication, but
this is not the case.

Any ideas as to why this might be happening?

Seems like you should double-check how the server is set up, so that
it really accepts SQL authentication. Another possibility is that there
is some name conflict, so you are not talking to the server you think you
are talking too. Can you login with username/password to the server from
Query Analyzer or OSQL from the same machine that you are using the Perl
script?

--
Erland Sommarskog, SQL Server MVP, sommar (AT) algonet (DOT) se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: DSNless SQL Authentication to SQL2000 database - defaulting to Integrated login

microsoft.public.sqlserver.clients microsoft.public.sqlserver.clients

Re: DSNless SQL Authentication to SQL2000 database - defaulting to Integrated login - 06-28-2003 , 05:13 PM