In both cases you would have to run a security audit trace with SQL profiler. Don't do it from your production server. Run the trace from a client PC because profiler is a resource pig.
- Paul
- If at first you don't succeed, find out if the loser gets anything.
It's difficult if not impossible to figure it out after the fact. You might try:
1. look at the security logs (Computer Management>System Tools>Event Viewer>Security) and see who was logged in during the timeframe the package was deleted.
2. get a 'log reader' program and see if you can read the transaction log for the timeframe.
-SQLBill
The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.