Answer Posted / prams

1. Staged the data coming from ODBC/OCI/DB2UDB stages
or any database on the server using Hash/Sequential files
for optimum performance also for data recovery in case job
aborts.
2. Tuned the OCI stage for 'Array Size' and 'Rows per
Transaction' numerical values for faster inserts, updates
and selects.
3. Tuned the 'Project Tunables' in Administrator for
better performance.
4. Used sorted data for Aggregator.
5. Sorted the data as much as possible in DB and
reduced the use of DS-Sort for better performance of jobs
6. Removed the data not used from the source as early
as possible in the job.
7. Worked with DB-admin to create appropriate Indexes
on tables for better performance of DS queries
8. Converted some of the complex joins/business in DS
to Stored Procedures on DS for faster execution of the
jobs.
9. If an input file has an excessive number of rows
and can be split-up then use standard logic to run jobs in
parallel.
10. Before writing a routine or a transform, make sure
that there is not the functionality required in one of the
standard routines supplied in the sdk or ds utilities
categories.
Constraints are generally CPU intensive and take a
significant amount of time to process. This may be the case
if the constraint calls routines or external macros but if
it is inline code then the overhead will be minimal.
11. Try to have the constraints in the 'Selection'
criteria of the jobs itself. This will eliminate the
unnecessary records even getting in before joins are made.
12. Tuning should occur on a job-by-job basis.
13. Use the power of DBMS.
14. Try not to use a sort stage when you can use an
ORDER BY clause in the database.
15. Using a constraint to filter a record set is much
slower than performing a SELECT … WHERE….
16. Make every attempt to use the bulk loader for your
particular database. Bulk loaders are generally faster than
using ODBC or OLE.

AGGREGATOR default datatype

1461

---

In a batch if a job fails in between and you want to restart the batch from that particular job and not from the scratch then what will you do?

1039

---

What are the types of containers?

1237

---

what is the use of skid in reporting?

2381

---

what is ds administrator used for?

1173

---

How the ipc stage work?

1130

---

how to add a new records into source?

2000

---

Differentiate between Join, Merge and Lookup stage?

1094

---

Can you explain how could anyone drop the index before loading the data in target in datastage?

1504

---

What are the benefits of datastage?

1238

---

Hi guys, Please design a job for dis requirement with derivation(solution). my source table like dis. emp_no qualification 1 a 1 c 2 a 3 c 3 b To loaded to target like dis emp_no qualification 1 b 2 b 2 c 3 a my requirement is every employer have three qualifications i.e a,b and c. what qualification missed in source table that will be move to target systems. Hope u got it the requirement. Right Thanks.

2903

---

in oracle target stage when we use load option and when we use upsert option?

2285

---

How a source file is populated?

1066

---

If you want to use a same piece of code in different jobs, how will you achieve this?

1276

---

What is usage analysis in datastage?

1309

---