Auditing a "drop procedure"
-
Some one could help me with one way in order to know what store procedure or table was dropped in the last month?
-
If you don't have auditing in place you need a log reader. That assuming that you have log backups going that far in the past.
In 2005, you can use the ddl triggers to audit such information.
-
Another option, if you have backups going back far enough, is to restore a backup of when you know all the objects were present. But restore it to a different location. Then use any of the multitude of comparison tools out there to compare the restored database versus the current. That'll tell you what's missing. However, if you want to know who did it, you're going to have to have the log files (or backups) and a log reader, just as Remi indicated.
K. Brian Kelley
@kbriankelley -
Lol, feels strange to see that everyone knows my name... even if I changed my nick a few years back
. -
Well, the reason I remember your name is probably an unusual one. I used to read the X-Men comics a lot as I was growing up. My favorite X-Man was Gambit (real name was the same but spelled Remy in the comics, though). So there you go.
K. Brian Kelley
@kbriankelley -
No need to have a reason Brian. I'm just not used to that fact that's all there is to it
... especially when someone with 10 posts seems to know it like we were old buddies .
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply