Hi Anthony and thanks for your answer, The problem is when you use a SQL connexion with SA you only check the SQL connectivity to the SQL Server and not to a database you want. The SQL connexion doesn't need to have read permissions on the database to run witch SA ODBC Check. I didn't try this free add-ons so I don't you if it checks the server connectivity or the database connectivity : SQL Server 2005/2008 check Test if a SQL Server database is up-and-running. This COM check is still in BETA v1.1.0.0 - 16-JUN-2009 This COM checks uses the .NET Framework 3.5 (installer will download/install if needed) This external COM check will only work with Servers Alive v4.1 or more recent. Thansk. Patrice. ----- Original Message ----- From: Laatz, Anthony (mailto:ala...@acanow.com) To: Servers Alive Discussion List (mailto:salive@woodstone.nu) Sent: Wednesday, January 13, 2010 3:50 PM Subject: RE: [SA-list] SQL Connection Configuration with COM ODBC Check.
I understand the wanting to use NT authentication, but I personally found it best to create a Servers Alive user account on the SQL server with read permissions to check the databases. If you are dead set on using NT Authentication, make sure the user account you are authenticating with has administrative rights to the server/computer that is running the SQL server. Thank you, Anthony Laatz Network Administrator Answer Center America From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of Dirk Bulinckx Sent: Wednesday, January 13, 2010 07:46 To: Servers Alive Discussion List Subject: Re: [SA-list] SQL Connection Configuration with COM ODBC Check. Probably this means that the DSN as such is NOT using the credentials that are within the DSN. Could you try setting "bad" credentials within the DSN and then test the DSN as such? dirk ----- Original Message ----- From: PatriceH (mailto:phermi...@gecip.fr) To: Servers Alive Discussion List (mailto:salive@woodstone.nu) Sent: Wednesday, January 13, 2010 1:10 PM Subject: Re: [SA-list] SQL Connection Configuration with COM ODBC Check. My server is connected (NT authentication) as UserA and my DSN has the same user UserA. If you mean the identity of SA service, the answer is no. The SA service is running with "localsystem" account as identity. Thanks. Patrice. ----- Original Message ----- From: Dirk Bulinckx (mailto:d...@woodstone.nu) To: Servers Alive Discussion List (mailto:salive@woodstone.nu) Sent: Wednesday, January 13, 2010 12:25 PM Subject: RE: [SA-list] SQL Connection Configuration with COM ODBC Check. and are you testing the dsn as the same user that is running SA? dirk From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of PatriceH Sent: Wednesday, January 13, 2010 11:35 AM To: Servers Alive Discussion List Subject: Re: [SA-list] SQL Connection Configuration with COM ODBC Check. yes. ----- Original Message ----- From: Dirk Bulinckx (mailto:d...@woodstone.nu) To: Servers Alive Discussion List (mailto:salive@woodstone.nu) Sent: Wednesday, January 13, 2010 11:15 AM Subject: RE: [SA-list] SQL Connection Configuration with COM ODBC Check. and does the DSN itself work? From: Servers Alive Discussion List [mailto:sal...@woodstone.nu] On Behalf Of PatriceH Sent: Wednesday, January 13, 2010 11:01 AM To: Servers Alive Discussion List Subject: [SA-list] SQL Connection Configuration with COM ODBC Check. Hi, I've a problem to check the sql connectivity to my SQL Server 2005 database. I have created a DSN entry in ODBC and use the COM ODBC (with ODBC Query check) in SA. I would like to use a login (NT authentication) instead of a SQL Server authentication and it doesn't work. I gave the datareader right to my db to my login with no success. In my ODBC setings in SA, I've tried mydomaine\myusername or myusern...@mydomain (mailto:myusern...@mydomain) with no success. Do you have any idea ? Thanks. Patrice. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
