> in SQL profiler, we see some activity from ClientProcessID = 980
> (malicious commands) , how do I figure out what is causing this
> security breach.
That's Windows process id at the host from which the commands are
originating from. So you need to find that machine first, and then
find process 980 on that box.

Signature
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
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
amit@desiboy.com - 31 May 2008 21:18 GMT
I don't see a column for WindowsProcessID ? Would it give a computer
name ?
Erland Sommarskog - 31 May 2008 21:58 GMT
> I don't see a column for WindowsProcessID ? Would it give a computer
> name ?
ClientProcessID is the the Windows Process ID. The trace could also have
a hostname.
Rather than looking in the trace, you can look in sysprocesses for
the hostprocessid.
Beware that the hostname can be forged by the application though. You
can find the IP address of the host in sys.dm_exec_connections if
you are on sQL 2005.

Signature
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
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