Hello all,
Is there a log of all connection attempts made to a SQL server?
The server I have is on Windows 2k.
Thanks,
David
--
David Williams
Georgia Institute of Technology, Atlanta Georgia, 30332
Email: dw149@prism.gatech.edu
Looks like SQL Profiler will do the job. Anybody have
experience in using it to see connection attempts?
David
David Williams
> Hello all,
> Is there a log of all connection attempts made to a SQL server?
> The server I have is on Windows 2k.
> Thanks,
> David
> --
> David Williams
> Georgia Institute of Technology, Atlanta Georgia, 30332
> Email: dw149@prism.gatech.edu
--
David Williams
Georgia Institute of Technology, Atlanta Georgia, 30332
Email: dw149@prism.gatech.edu
Here are a couple resources (SQL Server 2000 specific):
http://www.sqlservercentral.com/articles/Administering/audit ingwithsqlprofiler/1461/
http://www.microsoft.com/technet/security/prodtech/sqlserver /sql2kaud.mspx
Using server side traces is a good way for production environments:
http://vyaskn.tripod.com/server_side_tracing_in_sql_server.h tm
http://www.dbazine.com/sql/sql-articles/larsen6
This one is SQL Server 2005 specific:
http://blogs.msdn.com/sqlprogrammability/archive/2006/08/16/ 703079.aspx
HTH,
Plamen Ratchev
http://www.SQLStudio.com
This looks great.
Thanks for the help.
David
Plamen Ratchev
> Here are a couple resources (SQL Server 2000 specific):
> http://www.sqlservercentral.com/articles/Administering/audit ingwithsqlprofiler/1461/
> http://www.microsoft.com/technet/security/prodtech/sqlserver /sql2kaud.mspx
> Using server side traces is a good way for production environments:
> http://vyaskn.tripod.com/server_side_tracing_in_sql_server.h tm
> http://www.dbazine.com/sql/sql-articles/larsen6
> This one is SQL Server 2005 specific:
> http://blogs.msdn.com/sqlprogrammability/archive/2006/08/16/ 703079.aspx
> HTH,
> Plamen Ratchev
> http://www.SQLStudio.com
--
David Williams
Georgia Institute of Technology, Atlanta Georgia, 30332
Email: dw149@prism.gatech.edu
David Williams (dw149@acmex.gatech.edu) writes:
> Looks like SQL Profiler will do the job. Anybody have
> experience in using it to see connection attempts?
You can use Profiler to track login and failed login attempts. However,
if the attempt to connection fails because you cannot reach SQL Server,
Profiler will not track anyhing. Quite obviously.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downlo ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books .mspx
Good point. I'm going set up a Microsoft Network Monitor on the
connection and see what traffic ( if any ) is coming across towards the
server.
That should help me a little.
David
Erland Sommarskog
> David Williams (dw149@acmex.gatech.edu) writes:
> > Looks like SQL Profiler will do the job. Anybody have
> > experience in using it to see connection attempts?
>
> You can use Profiler to track login and failed login attempts. However,
> if the attempt to connection fails because you cannot reach SQL Server,
> Profiler will not track anyhing. Quite obviously.
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downlo ads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books .mspx
--
David Williams
Georgia Institute of Technology, Atlanta Georgia, 30332
Email: dw149@prism.gatech.edu