Metrics to diagnose ETL Jobs load performance in Informatica

Hi,

I am managing an ETL team now and I learnt that it took informatica 27 Hours to load 85 Million rows. In my opinion this is unacceptable.

What metrics (and from what tool or repository of informatica) I can get more diagnostic information about

1. The source database is slow
2. The target database is slow
3. Missing indexes issues
4. Transforms taking time
5. Staging database is slow
6. Job was queued in the system ( so the actual time can be 5 hour but for 22 hours it was in a queue)

Anything else you might think of. My point is simple I want the team to look for all kinds of optimization opportunities to speed up this job or work with the vendor to get this fixed

thanks
-anshu
anshumaEngineeringAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

aikimarkCommented:
Contact Informatica immediately.

In such cases, I usually advise my clients to isolate the problems.  For instance, just for the extract phase, I would ask...
* is the source database busy when you want to run the extract?
* is the extract job (network) 'close' to the source database server?
* what is the speed and capacity of the network path from the source database to the extract job?
* is the extract job running on a busy server?
* is the extract job running on a resource constrained server?
* is the extract job using local storage for its temp/working files?
* what is the fastest possible extract of data from the source, independent of the Informatica software?

All of these questions are independent of the configuration and properties your team has assigned to the ETL job, which should be double-checked.  I've seen cases, in other system utilities, where an option was selected to minimize system resource use.  The trade-off was slow run times.

In another shop, the vendor's tape management system used the first character of the job name to index the job's data in the utility's internal linked-list data structure.  Since the production job names began with "P", there was a very uneven distribution of data and all activities (insert, search, update, delete) took a very loooong.  Rather than replacing the tape management system, the jobs were renamed.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sdstuberCommented:
You should be able to look in the workflow monitor logs and see which steps are taking a long time.

Then determine what the corresponding SQL statements are and give those to your dba team to investigate.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Enterprise Software

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.