Re: Auditing SP Execute.
From: Jasper Smith (jasper_smith9_at_hotmail.com)
Date: 02/23/05
- Next message: Steve Troxell: "Re: Auditing SP Execute."
- Previous message: Ender Wiggins: "Re: MBSA 1.2 and slammer"
- In reply to: Pranay Pandya: "Auditing SP Execute."
- Next in thread: Andrew J. Kelly: "Re: Auditing SP Execute."
- Reply: Andrew J. Kelly: "Re: Auditing SP Execute."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 23 Feb 2005 22:06:53 -0000
As long as the users only have execute permissions on the proc i.e. they
can't change it, then just add some code at the start of the proc to log to
a table passing getdate() and suser_sname() to capture the time and user
executing the proc. This assumes that the app doesn't use a single service
account (in which case you won't be able to get the user name without
modifying the app to stuff it into context_info)
-- HTH Jasper Smith (SQL Server MVP) http://www.sqldbatips.com I support PASS - the definitive, global community for SQL Server professionals - http://www.sqlpass.org "Pranay Pandya" <ppandya@gmail.com> wrote in message news:1109178725.456740.135850@z14g2000cwz.googlegroups.com... > To meet audit requirements, I have to maintain an audit log of when a > particular sp was execute and by whom. I am not willing to use the c2 > option for just one stored procedure. There are 2 users who can run > the stored procedure from enterprise manager or query analyser (others > run it from an app). Any suggetions? > Thank You, > -pranay >
- Next message: Steve Troxell: "Re: Auditing SP Execute."
- Previous message: Ender Wiggins: "Re: MBSA 1.2 and slammer"
- In reply to: Pranay Pandya: "Auditing SP Execute."
- Next in thread: Andrew J. Kelly: "Re: Auditing SP Execute."
- Reply: Andrew J. Kelly: "Re: Auditing SP Execute."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|