That was the first thing I did. I managed to fix it by dropping and readding the XP that was failing. Now I get

This database is not...

If you are trying to track ad hoc code in you application, you are going to need to track batch started and ended. That will let you see the...

Ugh. SQL Code hard coded in the application? Do they never learn. A solution I have used in the past, which is kind of bulky, but it...

Are you dealing with stored procedures or ad hoc queries?

In you SQL Trace, enable RPC: Starting, SP:Starting, or SP:StatementStarting and you will see where they began. If you add the :Ending columns, you will see that they did...

I thought of that as well since create statment contain passwords. And that does make perfect sense. Alter Login statements also do not record a TSQL statement, but...

This is ths EventData() XML for the create login event

<EVENT_INSTANCE>

<EventType>CREATE_LOGIN</EventType>

<PostTime>2010-06-08T06:28:54.510</PostTime>

<SPID>198</SPID>

<ServerName>CP-ITS-SQL64D02\SQLDEV02</ServerName>

<LoginName>SAIC-US-WEST\x_stevicd</LoginName>

<ObjectName>test12345</ObjectName>

<ObjectType>LOGIN</ObjectType>

<DefaultLanguage>us_english</DefaultLanguage>

<DefaultDatabase>master</DefaultDatabase>

<LoginType>SQL...

No, you don't, becuase it doesn't exist. If you grab the XML code that is shot out by eventdata(), you will see there no SQL code harvested for the...

This is the code I have been using. It has been working fairly well...

/****** Object: DdlTrigger [ddl_server_Changes] Script Date: 05/24/2010 15:48:15 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER...