Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


The Auditing Poll


The Auditing Poll

Author
Message
Steve Jones
Steve Jones
SSC-Forever
SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)

Group: Administrators
Points: 42706 Visits: 18877
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
My Blog: www.voiceofthedba.com
David.Poole
David.Poole
SSCarpal Tunnel
SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)

Group: General Forum Members
Points: 4638 Visits: 3187
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

Newbie on www.simple-talk.com
call.copse
call.copse
Hall of Fame
Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)Hall of Fame (3.1K reputation)

Group: General Forum Members
Points: 3076 Visits: 1884
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.
Gary Varga
Gary Varga
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10860 Visits: 6366
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!!!
phegedusich
phegedusich
SSC-Enthusiastic
SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)SSC-Enthusiastic (106 reputation)

Group: General Forum Members
Points: 106 Visits: 531
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.
-=JLK=-
-=JLK=-
Old Hand
Old Hand (395 reputation)Old Hand (395 reputation)Old Hand (395 reputation)Old Hand (395 reputation)Old Hand (395 reputation)Old Hand (395 reputation)Old Hand (395 reputation)Old Hand (395 reputation)

Group: General Forum Members
Points: 395 Visits: 303
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.
Steve Jones
Steve Jones
SSC-Forever
SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)

Group: Administrators
Points: 42706 Visits: 18877
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
My Blog: www.voiceofthedba.com
Dave Schutz
Dave Schutz
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2020 Visits: 609
We use built-in SQL Audit to check for login attempts and unauthorized changes to the system.
Steve Jones
Steve Jones
SSC-Forever
SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)SSC-Forever (42K reputation)

Group: Administrators
Points: 42706 Visits: 18877
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
My Blog: www.voiceofthedba.com
BP-111
BP-111
SSC Journeyman
SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)

Group: General Forum Members
Points: 82 Visits: 453
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search