May 31, 2012 at 12:07 am
Comments posted to this topic are about the item What, when and who? Auditing 101 - Part 3
-Roy
May 31, 2012 at 5:13 am
You have a typo in your code: "WriteToApllicationLog" 😉
May 31, 2012 at 5:49 am
Very nice feature and article, this will full fill so many cases but for some real auditing this needs to be get more matured.
I have two informations to share here, one is good and the other one is bad.
first the good one.
SQLCat has build some code to collect audited data, which can be modified as per need.
http://sqlcat.codeplex.com/wikipage?title=sqlauditcentral&referringTitle=Home
secondly the bad thing.
We have some limitations of seeing parameterized value, sometimes (in my case most of the time) SQL audit is unable to capture the actual value, which was passes using variable to stored procedure or sql query.
Bye.
May 31, 2012 at 6:00 am
Can you please also make an article how to take the sql audit logs to a sql table using ssis/whichever way is easier?
Thanks.
May 31, 2012 at 7:04 am
bmcateer (5/31/2012)
You have a typo in your code: "WriteToApllicationLog" 😉
Thx for pointing it out. 🙂 Next time I will be more careful. 🙂
-Roy
May 31, 2012 at 7:06 am
Hi Computrion, Thx for links. Yes, I noticed that the SQL Audit does not catch all the values.
-Roy
May 31, 2012 at 7:08 am
Beginner2008, Thx. You gave me an idea for the next article. I will try to do one regarding capturing the auditing data and writing it to a Table.
-Roy
May 31, 2012 at 11:58 am
UPDATE [dbo].[tbProducts] set [ProductCost] = @1 WHERE [ProductID]=@2
For my test using 2008 R2 I actually got the values used in the update statement and not variables. I got:
update dbo.tbProducts Set ProductCost = 2750 where ProductID = 1
Is this a 2008 vs R2 thing?
Cheers
May 31, 2012 at 1:22 pm
Yes it is. The behavior changes even for different level of Service packs unfortunately.
-Roy
May 31, 2012 at 1:31 pm
Noted. Thanks for the article.
Cheers
May 31, 2012 at 1:51 pm
Hi,
Very nice article.
So am i right in saying this form of auditing only answers the "when" and not the "who", I saw session Id but unless your constantly recording whose using the session Id that doesn't tell you anything?
May 31, 2012 at 2:57 pm
Who is also shown. If you look at the first http://www.sqlservercentral.com/Images/14239.jpg
you will session_server_principal_name which will show the user name
-Roy
December 19, 2014 at 7:17 am
This doesn't work for Standard edition of SQL Server.
Igor Micev,My blog: www.igormicev.com
December 19, 2014 at 7:26 am
That is true.. In SQL Server 2008 only EE and Datacenter supported this feature.
But in SQL 2012 Server level auditing is available in all editions. Only Database level auditing is limited to Enterprise, Developer, and Evaluation editions.
-Roy
December 19, 2014 at 10:59 am
Also, who audits the auditor? My company requires an audit tool that can't be altered by the sysadmin. So it's Guardium for now.
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply