on 12-25-2014 4:12 PM
What I have to do when some job was taking 1 hour to execute but now taking 15 hours. How can I solve this problem?
As mentioned in this chain, the reasons can be numerous.
Some usual causes are
1. If there is a join in the dataflow check the join condition as there might be cartisian issue in cases which might cause the issue
2. Check the BODS Job server infrastructure setup. If the volume of data processed a lot higher than the original volume when it was taking 1 hour to execute, then you might need to upgrade the infrastructure. RAM/CPU or the combination of both can be upgraded
3. Check the indexing set up on the source and target tables. Specifically if the target table has a clustered index introduced, then it will take a lot of time to load as it will cluster after each commit.
The causes and remedies are endless.......
Raghu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Is there any calculation using the absolute time and elapsed time to check the time taken to read 1000 rows in a particular query.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I had a similar issue where job executes for longer time.Could you please suggest in the monitor long how can we know that a particular query in the data flow is taking longer time to process.What makes the difference of the execution time and elapsed time.
Many thanks in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sabat,
As Dirk mentioned, check your BODS Logs and try to find which data flow is taking longer to complete. There might be a possibility of index fragmentation of your fact tables(if there are any). There might be other reasons also so I am not asking to check the indexes directly.
Regards
Arun Sasi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There might be thousands of reasons. Try to narrrow down your problem using the monitor log output. Then proceed from there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.