Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Auditing DTS Packages Expand / Collapse
Author
Message
Posted Sunday, October 5, 2003 12:00 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, January 18, 2013 11:03 AM
Points: 55, Visits: 60
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/hji/auditingdtspackages.asp


Post #16963
Posted Monday, October 6, 2003 10:11 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Saturday, December 20, 2014 3:11 PM
Points: 31,368, Visits: 15,837
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
Post #82186
Posted Monday, October 6, 2003 10:47 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Tuesday, November 5, 2013 9:05 AM
Points: 976, Visits: 59
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
Post #82187
Posted Monday, October 6, 2003 11:10 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, January 18, 2013 11:03 AM
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



Post #82188
Posted Saturday, March 26, 2011 4:12 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Sunday, February 26, 2012 11:02 PM
Points: 1, Visits: 46
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
Post #1084500
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse