RE: [SA-list] SQL server via Windows Authentcation

[Carter, Phillip]

Title: RE: [SA-list] SQL server via Windows Authentcation

But that's what I'd like to do.

 

We have SA running as a service on it's own box using a domain account. Why can't SA just not provide the username and password.

 

I do this in SQL-DMO all the time. You just provide a Server name, set LoginSecure = True then connect.

 

At the moment if I leave out the username and password I get the message,

"Unsuccessfull connection Microsoft SQL-DMO (ODBC SQLState: 28000) Error 18456: [Microsoft][ODBC SQL Server Driver] [SQLServer]Login failed for user ' '."

 

Which looks like a) it passes through a space for the login and b) actually connects via ODBC.

 

Thanks
Phillip Carter
Ph: +61 3 9235 1691

 

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx
Sent: Friday, 18 June 2004 6:54 AM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] SQL server via Windows Authentcation

The sql client will pass the credentials of the currently logged-on user to the sql server, that's what the client libs do, and we have no control over this.

 

Dirk.

 

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carter, Phillip
Sent: Thursday, June 17, 2004 10:23 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [SA-list] SQL server via Windows Authentcation

So why can't the credentials of the currently logged on user (or service account) be used by the SQL Client?

From there it would be a no-brainer to grant that login limited read-only access in SQL Server.

Thanks
Phillip Carter
Ph: +61 3 9235 1691

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Dirk Bulinckx
Sent: Friday, 18 June 2004 4:16 AM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] SQL server via Windows Authentcation

This can't be supported for the simple reason that the SQL client is NOT accepting a username/password for NT authentication, it will only use the username/password of the currently logged on user.  This is a limit of the SQL client not of Servers Alive.

Dirk.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED]
Sent: Thursday, June 17, 2004 12:53 PM
To: [EMAIL PROTECTED]
Subject: [SA-list] SQL server via Windows Authentcation

Hi List,

I'm trying to check availability of a SQL-server database thru Salive 4.1 .

This works fine when using SQL-authentication (i.e. using the SA-account).
However, we also have SQL-databases that use only Windows Authentication (i.e. with domain/userid), testing these databases fail.

Am I correct to conclude that Windows Authentication is not (yet) supported ?

Thanks in Advance
Leon

--------------

[This E-mail scanned for viruses by Declude Virus]

To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message:
   unsubscribe SAlive

IMPORTANT DISCLAIMER - THIS MAY AFFECT YOUR LEGAL RIGHTS: Because this document has been prepared without consideration of any specific clients investment objectives, financial situation or needs, a Bell Potter Securities Limited investment adviser should be consulted before any investment decision is made. While this document is based on the information from sources which are considered reliable, Bell Potter Securities Limited, its directors, employees and consultants do not represent, warrant or guarantee, expressly or impliedly, that the information contained in this document is complete or accurate. Nor does Bell Potter Securities Limited accept any responsibility to inform you of any matter that subsequently comes to its notice, which may affect any of the information contained in this document.

This document is a private communication to clients and is not intended for public circulation or for the use of any third party, without the prior approval of Bell Potter Securities. Disclosure of Interest: Bell Potter Securities Limited receives commission from dealing in securities and its authorised representatives, or introducers of business, may directly share in this commission. Bell Potter Securities and its associates may hold shares in the companies recommended. Bell Potter Securities Limited ABN 25 006 390 772 AFS Licence No. 243480

IMPORTANT DISCLAIMER - THIS MAY AFFECT YOUR LEGAL RIGHTS: Because this document has been prepared without consideration of any specific clients investment objectives, financial situation or needs, a Bell Potter Securities Limited investment adviser should be consulted before any investment decision is made. While this document is based on the information from sources which are considered reliable, Bell Potter Securities Limited, its directors, employees and consultants do not represent, warrant or guarantee, expressly or impliedly, that the information contained in this document is complete or accurate. Nor does Bell Potter Securities Limited accept any responsibility to inform you of any matter that subsequently comes to its notice, which may affect any of the information contained in this document.

This document is a private communication to clients and is not intended for public circulation or for the use of any third party, without the prior approval of Bell Potter Securities. Disclosure of Interest: Bell Potter Securities Limited receives commission from dealing in securities and its authorised representatives, or introducers of business, may directly share in this commission. Bell Potter Securities and its associates may hold shares in the companies recommended. Bell Potter Securities Limited ABN 25 006 390 772 AFS Licence No. 243480