SQL 2005 Profiler
- From: "Jonathan Chong" <j0nathon@xxxxxxxxxxx>
- Date: Tue, 29 Apr 2008 15:25:48 +0800
I found below entries in Event Viewer's Application Log and System Log which
worries me as I know for sure that
there is no one login to SQL and use profiler on that time. There are only
two of us have the access to the SQL server and it is firewalled to only
allow office's IP to SQL 2005 server (on Windows 2003 server).
Application Log:
7:24:39 Login failed for user 'sa'. [CLIENT: <local machine>]
7:29:03 SQL Trace ID 2 was started by login "sa".
7:30:56 SQL Trace stopped. Trace ID = '2'. Login Name = 'sa'.
7:46:07 SQL Trace ID 2 was started by login "sa".
7:46:35 SQL Trace stopped. Trace ID = '2'. Login Name = 'sa'.
7:49:03 SQL Trace ID 2 was started by login "sa".
7:49:12 SQL Trace stopped. Trace ID = '2'. Login Name = 'sa'.
7:49:31 SQL Trace ID 2 was started by login "sa".
7:49:46 SQL Trace stopped. Trace ID = '2'. Login Name = 'sa'.
System Log:
7:12:20 Driver Microsoft Office Document Image Writer Driver required for
printer Microsoft Office Document Image Writer is unknown. Contact the
administrator to install the driver before you log in again.
7:12:21 Driver Microsoft XPS Document Writer required for printer Microsoft
XPS Document Writer is unknown. Contact the administrator to install the
driver before you log in again.
7:45:01 Driver Microsoft Office Document Image Writer Driver required for
printer Microsoft Office Document Image Writer is unknown. Contact the
administrator to install the driver before you log in again.
7:45:02 Driver Microsoft XPS Document Writer required for printer Microsoft
XPS Document Writer is unknown. Contact the administrator to install the
driver before you log in again.
7:59:13 Driver Microsoft Office Document Image Writer Driver required for
printer Microsoft Office Document Image Writer is unknown. Contact the
administrator to install the driver before you log in again.
Since both of us are not in office and for sure neither one of us that uses
profiler as shown in the log. My question is: Is there any possibility that
the logs is triggered by SQL itself besides human?
If it is an intruder works, where can I look for more traces leave behind by
intruder?
Jon
.
- Follow-Ups:
- Re: SQL 2005 Profiler
- From: Dan Guzman
- Re: SQL 2005 Profiler
- Prev by Date: RE: SQL2005 non-administrator Service Account
- Next by Date: Re: SQL 2005 Profiler
- Previous by thread: SQL2005 non-administrator Service Account
- Next by thread: Re: SQL 2005 Profiler
- Index(es):
Relevant Pages
|
|