Re: ODBC Connection security
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Thu, 07 Feb 2008 14:57:18 -0800
SFB EIM (sfbeim@xxxxxxxxxxx) writes:
I have a need to find out when any ODBC connection is made to a certain
SQL Server.
I assume any/all ODBC connections will have to use TCP port 1433 - since
SQL uses only TCP 1433 in this server's case.
Well, a local connection would typically use shared memory.
Is there any SQL method to detect a new ODBC connection and perhaps send a
notification or else log it to some SQL log file?
I need to pick up the remote client's IP address for immediate
notification to Management.
If you are on SQL 2005 SP2, you can set up a login trigger. You can
get the client API from sys.dm_exec_sessions.client_interface_name if you
really only want to report ODBC connections, but ignore OLE DB or .Net.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Follow-Ups:
- Re: ODBC Connection security
- From: SFB EIM
- Re: ODBC Connection security
- Prev by Date: Re: Cross-database execution permissions with certificates and sch
- Next by Date: Re: file system permissions and cross-database certificates?
- Previous by thread: SQL Server 2005--Access is Denied
- Next by thread: Re: ODBC Connection security
- Index(es):
Relevant Pages
|
|