Why we use parameters instead of hard code in datastage.
Answers were Sorted based on User's Feedback
Answer / hanug
We use parameters to reuse the job multiple times by
passing different values to the job parameters.
| Is This Answer Correct ? | 8 Yes | 0 No |
Answer / nish
hard coding is a very bad practice.
You will face troubles once you deploy to production environment and need to make changes.
Instead if you parameteris and just make the change in original it will automatically update.
This is similar to your ATM card and pin. even if you change/update your pin the card will work.
If pin is hardcoded to the card and you need to change pin, then you need to get a new card everytime you want to change pin.
Does that make sense?
| Is This Answer Correct ? | 2 Yes | 0 No |
How can we perform 2nd time extraction of client database without accepting the data which is already loaded in first time extraction?
Differentiate between Join, Merge and Lookup stage?
30 jobs are running in unix.i want to find out my job.how to do this?Give me command?
What is Ad-Hoc access? What is the difference between Managed Query and Ad-Hoc access?
1.When did 8.1 parallel came into existence? 2.What is the difference between 7.5 and 8.1?
What is process model?
cust id,cust quty like 1,101;1,102;1,103 i want output like cust id,cust quty 1 101,102,103 in oracle please write a query in oracle
Hi All, Could you please let me know whether Datastage server and px supports oredb? OREDB:It's a Oracle Retail Embedded Database.Previousely It was called as Acumate data base. It's a multidimensional database. Please help me on this issue ASAP. Thanks in advance Ashok
Please tell me What is difference between 8.0 and 8.1
How to LOG 'unmatched Master' records and 'Reject Updates' in log files using MERGE stage?
How rejected rows are managed in datastage?
WHAT are unix quentios in datastage