SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


ETL Performance Auditing - Part 1: Introduction to ETL Auditing


ETL Performance Auditing - Part 1: Introduction to ETL Auditing

Author
Message
Frank Banin
Frank Banin
SSC-Enthusiastic
SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)

Group: General Forum Members
Points: 146 Visits: 443
Comments posted to this topic are about the item ETL Performance Auditing - Part 1: Introduction to ETL Auditing

Frank Banin
BI and Advanced Analytics Professional.
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)SSC Guru (211K reputation)

Group: General Forum Members
Points: 211227 Visits: 41977
From the Article
The problem is there are over 300 individual child SSIS packages that ...

...{snip}...

For bigger ETL setups with many of packages and tasks, you might need a system that loops through all your packages to obtain this information. For instance you can loop through the .dtsx files with XML or use C# or VB and the SISS object Model to achieve this objective, a topic I will leave for another discussion.



Good article but I'm really hoping that "another discussion" will be one of the two other parts of this series because something that does the above is really going to be important to someone who has "over 300 individual child SSIS packages".

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
knausk
knausk
SSC-Enthusiastic
SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)

Group: General Forum Members
Points: 119 Visits: 138
You say, "By the the end of this Part you should have enabled logging using the SQL Server log Provider, and also gathered the Names and IDs of your packages and tasks."

You do not provide in this first article how to use and set the suggested logging modes for Pre, Post, etc nor do you explain using SQL Server log Provider. Nor do you clearly explain where the Package ID tables would be nor how to find them. I suspect you are assuming that the Packages in use are stored in a database and not on the file system, but I cannot tell from your article.

Perhaps I missed the above descriptions in your article, and did you say which version of SSIS are you using as the basis of this article?

Thanks,

Kevin
Frank Banin
Frank Banin
SSC-Enthusiastic
SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)SSC-Enthusiastic (146 reputation)

Group: General Forum Members
Points: 146 Visits: 443
To Jeff Moden point, I will discuss how to obtain package information for cases where people may have a lot of Packages. The reason I wanted to discuss the approach I employ separately is because I use the SSIS object model and C# which in itself require some explanations, I just did not want to take the focus away from what I was trying to achieve with this series.

Kevin to your concern:
In this article "Serving Warm SSIS Errors" on SQL Server Central you can check out the “Enabling SSIS logging with SQL Server log Provider” section for details on how to setup the suggested logging mode. After you’ve enabled logging it does not matter where you deploy your packages. As for the Package ID tables as you see later all you need to be able to join the it to the SSIS logging table into which you enabled your logging.

Frank Banin
BI and Advanced Analytics Professional.
Misha_SQL
Misha_SQL
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1640 Visits: 1010
A very promising beginning. I have been employing the exact approach you mentioned: having individual audit tasks attached to the tasks in the package, but, as you rightfully pointed out, this gets complicated very quickly as complexity of the packages increases. I look forward to learning how to do this more efficiently.



crisnupra
crisnupra
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 17
Very interesting indeed! I have high hopes for the next in the series.
Will be nice to know the version of SSIS or if its equal in all the versions.
Looking forward to read the next part
herladygeekedness
herladygeekedness
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1320 Visits: 813
This series comes at a great time for me as I am currently "between cubes" and in more of a refinement stage (ok, Cleanup, but also making tweaks as needed). We have some auditing in place, but only for our custom components while some of what we need to know is how long other components are taking.

Can't wait!!
rvphx
rvphx
SSC-Addicted
SSC-Addicted (480 reputation)SSC-Addicted (480 reputation)SSC-Addicted (480 reputation)SSC-Addicted (480 reputation)SSC-Addicted (480 reputation)SSC-Addicted (480 reputation)SSC-Addicted (480 reputation)SSC-Addicted (480 reputation)

Group: General Forum Members
Points: 480 Visits: 296
I liked your article. I found something similar on Pragmatic works website. Just posting here as an added material :-) The link is http://pragmaticworks.com/Products/Business-Intelligence/BIxPress/ssis-logging-auditing-monitoring.aspx.

The article talks about 2 types of the most implemented methods of logging. Then, it gives preview of the tool (not free) which would help in logging multiple packages and different attributes of the packages.
I am posting here just FYI.
aaa121
aaa121
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1281 Visits: 783
I think one important thing to note is that you would typically set up a template package with all of your variables and package configs all set up. By copying and pasting this package you are able to quickly build up your ETL.

However, when using this method in conjuction with the SourceID attribute as mentioned you will need to explicitly generate a new SourceID for each package you copy and paste based on the template. Otherwise, all packages will have the same SourceIDs.
aaa121
aaa121
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1281 Visits: 783
I believe using the pre and post execute event handlers to call SPs in order to write to a auditing table is the most efficient and and less invasive method of auditing, so I would be interested to see if this is covered in subsequent parts.
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