2010-10-29
03:49 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Best Practice for Implementing Microsoft SQL Scripts
When configuring MS SQL logging to enVision how many of you are installing the SQL scripts with all the trace flags on by default?
If you've commented out some of these flags, which ones are they and how did you decide?
1 Reply
2010-12-01
11:40 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
ya... the default trace script is way to overpowering in most cases... you will want to tune that down to a specific data set you are attempting to gather. Most of the time I belive MS114 (Don't quote me on that) is the heavy hitter.
it depends, but you want to look at the insert, update, delete, user perm modification actions. Typically if it's not HIPAA related or super sensitive data, you can comment out or filter out the select statements. It just depends on the reason for the logging.
