<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQLServerCentral.com
»
Editorials
»
The Auditing Poll
11 posts, Page 1 of 2
1
2
»»
The Auditing Poll
Rate Topic
Display Mode
Topic Options
Author
Message
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Thursday, January 10, 2013 11:19 PM
SSC-Dedicated
Group: Administrators
Last Login: Today @ 12:49 PM
Points: 31,432,
Visits: 13,742
Comments posted to this topic are about the item
The Auditing Poll
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #1405772
David.Poole
David.Poole
Posted Friday, January 11, 2013 1:39 AM
SSCrazy
Group: General Forum Members
Last Login: 2 days ago @ 9:35 AM
Points: 2,749,
Visits: 1,407
Given that audit logs are not read frequently I feel we need to consider where the appropriate place is to store audit logs.
Clearly they need to be secure so they cannot be tampered with but that does not necessarily mean they should incur the cost of storing them in a database?
Given that they are huge some form of compressed storage will be required.
LinkedIn Profile
Post #1405816
call.copse
call.copse
Posted Friday, January 11, 2013 3:00 AM
Ten Centuries
Group: General Forum Members
Last Login: Today @ 4:44 AM
Points: 1,087,
Visits: 692
My current shop typically audits primary entity changes with creation and mod dates and users by default. We may apply further auditing but only where there is some particular requirement e.g. price changes. We don't automatically catalogue everything. Our standard reporting solution has record the SQL used for each report which can be helpful.
In general I've found it easiest to stick to using a trigger to record audit details externally to the audited table (obviously this depends, I would not do this for a bulk import table say). I'd certainly consider SQL audit facilities but not quite got there yet.
Post #1405846
Gary Varga
Gary Varga
Posted Friday, January 11, 2013 3:57 AM
Hall of Fame
Group: General Forum Members
Last Login: Today @ 9:14 AM
Points: 3,540,
Visits: 1,128
As a solution architect I am continually told that auditing is essential.
As a software developer I am continually told that auditing is too low a priority to implement and it will be added when required (when working in non-regulated areas).
It is an area of work, like testing and logging, whose value is only realised when it's benefits are required and by then it is too late.
Makes me cross. Grrrrrr.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
Post #1405870
phegedusich
phegedusich
Posted Friday, January 11, 2013 5:54 AM
SSC Rookie
Group: General Forum Members
Last Login: Friday, May 17, 2013 9:20 AM
Points: 37,
Visits: 290
In the environments I support, auditing is required by regulation. I have rudimentary tracking enabled via trigger on a subset of sensitive fields. Additionally, I use the default trace for troubleshooting.
Audit's the only way to explain what happened, when, and who did it. I try to include it in every new system I design. And yes, there's pushback about its importance and priority when it comes to development, but I'm in a business area that demands it.
Post #1405950
-=JLK=-
-=JLK=-
Posted Friday, January 11, 2013 6:46 AM
Old Hand
Group: General Forum Members
Last Login: Tuesday, January 22, 2013 6:39 AM
Points: 367,
Visits: 297
We audit all user editable data. I use a trigger to simply add a complete copy of the record being inserted/updated/deleted to a duplicate (non-indexed), table. I have extra columns in each audit table to track date and user information. Pretty basic but it is surprising how often the audit tables are queried to determine who did what when. Fortunately we don't have to track who accesses/views the data just the changes. We keep the data for 12 months and a nightly job cleans out old audit data. The benefit for me is the speed and simplicity, I get complete detail with little effort, the downside is the space and when you have to analyse it, that is a manual process as you have to compare each column row by row to see what was actually changed, but so far that hasn't been to arduous.
Post #1405977
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Friday, January 11, 2013 8:47 AM
SSC-Dedicated
Group: Administrators
Last Login: Today @ 12:49 PM
Points: 31,432,
Visits: 13,742
David.Poole (1/11/2013)
Given that audit logs are not read frequently I feel we need to consider where the appropriate place is to store audit logs.
Clearly they need to be secure so they cannot be tampered with but that does not necessarily mean they should incur the cost of storing them in a database?
Given that they are huge some form of compressed storage will be required.
Agree, though in the short term dropping them in another filegroup/database makes some sense. However an archive plan to move them regularly to a text export of some sort, makes sense.
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #1406098
Dave Schutz
Dave Schutz
Posted Friday, January 11, 2013 8:56 AM
SSCommitted
Group: General Forum Members
Last Login: Wednesday, April 17, 2013 12:02 PM
Points: 1,631,
Visits: 566
We use built-in SQL Audit to check for login attempts and unauthorized changes to the system.
Post #1406107
Steve Jones - SSC Editor
Steve Jones - SSC Editor
Posted Friday, January 11, 2013 8:58 AM
SSC-Dedicated
Group: Administrators
Last Login: Today @ 12:49 PM
Points: 31,432,
Visits: 13,742
Dave Schutz (1/11/2013)
We use built-in SQL Audit to check for login attempts and unauthorized changes to the system.
Server and DB specs? How's that working out? Want to write about it for me
Follow me on Twitter:
@way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
Post #1406110
BP-111
BP-111
Posted Friday, January 11, 2013 9:58 AM
SSC Journeyman
Group: General Forum Members
Last Login: Thursday, May 16, 2013 3:34 PM
Points: 82,
Visits: 394
I work in a public company that adhere to SOX regulation and we basically need to track unauthorized direct database changes. What this means is all transactions from sysadmin, dbo and whoever has write access in the database must be audited. I used server side trace originally to audit it. We migrated to use built in SQL Audit when we upgrade server to SQL 2008. However SQL Audit has limitation that it generates audit for all sysadmin users in database level including service account and sa. The database level filter doesn't work for sysadmin. So I decided to use Idera SQL Compliance Manager. It is nice tool with different filtering capability and nice GUI plus SSRS reports. We have to keep the audit data for 7 years so I use RedGate Storage Compress on those databases to keep them to reasonable size. All these turn out to work quite well.
Post #1406153
« Prev Topic
|
Next Topic »
11 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
