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


Auditing DTS Packages


Auditing DTS Packages

Author
Message
Haidong Ji
Haidong Ji
Valued Member
Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)

Group: General Forum Members
Points: 55 Visits: 60
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/hji/auditingdtspackages.asp



Steve Jones
Steve Jones
SSC-Dedicated
SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)SSC-Dedicated (36K reputation)

Group: Administrators
Points: 36022 Visits: 18732
Very nice and an interesting idea for auditing packages. One question: Any issues with a trigger in msdb for patches/service packs? Not sure I like the idea of changing the system tables, but this is fairly minimal.

I'm still more of a fan of NT auth for connections and auditing as well as having a separate owner pwd for people working on a package, but this is something I'll have to think about.

Steve Jones
sjones@sqlservercentral.com
http://www.sqlservercentral.com/columnists/sjones
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
www.dkranch.net

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
Robert W Marda
Robert W Marda
SSC Eights!
SSC Eights! (984 reputation)SSC Eights! (984 reputation)SSC Eights! (984 reputation)SSC Eights! (984 reputation)SSC Eights! (984 reputation)SSC Eights! (984 reputation)SSC Eights! (984 reputation)SSC Eights! (984 reputation)

Group: General Forum Members
Points: 984 Visits: 82
Nice article. I was surprised SQL Server let me place the trigger on that system table. It blocks it for other tables unless you modify the table first.

Keep in mind that any user with access to the DTS packages can delete the various versions and thus destroy a record of what changed.

Its nice to know someone else has databases on each server for DBA use. Ours are referred to as SAResources.

Robert W. Marda
SQL Programmer
bigdough.com
The world’s leading capital markets contact database and software platform.



Robert W. Marda
SQL Programmer
Ipreo

Haidong Ji
Haidong Ji
Valued Member
Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)Valued Member (55 reputation)

Group: General Forum Members
Points: 55 Visits: 60
Thanks guys for the compliment.

As to trigger in system databases for patches/service packs, it's hard to tell. I think it also depends on each individual patch/SP. Some patches/SPs might modify a table structure. When that happens, this trigger might get lost. I guess it's always a good idea to check after each patch/SP is installed.

As to the deletion of a package, yes, a separate trigger has to be created to audit deletion of DTS packages.

Thanks.

Haidong



Tim Bensehil
Tim Bensehil
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 76
This is a great article on DTS Auditing indeed.
I was just wondering if you could use the same approach to audit the actual execution of all DTS packages instead of capturing the changes made to them. That is logging the execution of all DTS packages using a trigger on the systable? What sys tablee/fields can be used?
This will greatly help DBA/Developer finding out which DTS packages are bieng called/used.

I would greatly appreciate your input on this

Thank you

Tim
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