this updated code that i posted previously does not raise any errors. it cannot get teh definition on drop procedure, but it does get creation and changes.

[font="Courier New"]

CREATE TABLE [dbo].[DDLEventLog](

        [EventDate]...

I looked in the registry on my machine, and I think this is where you want to go to delete old servers you no longer connect to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSocketNetLib\LastConnect

mine has a list...

the problem is, some domain users may come in with more rights than you want to give them....a domain user might also be a domain admin, so giving a group...

because this question looks a lot like what a homework assignment would require so that you get used to querying and displaying data, you'll need to show us what you...

look at the sysobjects table.

there is a column there called "xtype". you could count(*) from sysobjects where xtype='U' for example, to get all user tables. V for views, you can...

SQL Server, or any relational database system for that matter, doesn't put data in any specific order unless you tell it to.

the primary key of a table is used...

From BOL:

DDL triggers fire only after the DDL statements that trigger them are run. DDL triggers cannot be used as INSTEAD OF triggers.

So I think if you simply do CREATE...

I took one of the examples I'd gotten here and modified it to get teh sp_helptext of the procedure being affected.

my audit trigger is called AFTER the CREATE/ALTER DROP event...so...

triggers have their purpose...i think the bad rap triggers get come from people trying to do stuff that should never occur in side a trigger anyway.

I've seen requests on opening...

the info is stored in the registry.

open regedit and search for one of the servers you know you want to eliminate. you can see which ones exist from there.

on my...

first it's not too late. It is never too late to fix an issue and make something better.

it is very easy to fix, you just have to break out of...

Excellent! glad we could help!

yeah, i don't know if it can be resolved...SP1 doesn't prevent a a bad execution from being built....SQL2005 still parameter sniffs, right?

yep same issue as the post here:http://www.sqlservercentral.com/Forums/Topic649831-8-1.aspx

i put a decent explanation and fixes there.

I think the issue you are hitting is called "parameter sniffing"; when the code is compiled into a procedure, the compiler makes a best guess on the parameters when it...