Why we use parameters instead of hard code in datastage.
- 2 Answers
- 6405 Views
- IBM, I also Faced
- E-Mail Answers
Answer Posted / 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 |
Post New Answer View All Answers
Define Data Stage?
What are the areas of application?
Can you explain how could anyone drop the index before loading the data in target in datastage?
1)How will u implement SCD2 by using surrogate key. 2)What are the disadvantages with surrogate key. 3)How will you handle nulls in your project for the varchar, integer data types. 4)Can I use two fact tables in star schema. 5)3 jobs are running on the 2 nodes after I added one more node so can I compile those jobs to run on three nodes.
What are the types of jobs we have in datastage?
How to implement complex jobs in data stage?
What is the use of datastage designer?
On which Dimension Table you implemented SCD Type in your Project
What is the difference between an operational datastage and a data warehouse?
How complex jobs are implemented in datstage to improve performance?
What are stage variables?
Where the datastage stored his repository?
What is a merge?
Could anyone give brief explanation bout datastage admin
What all are the different way to run a job?
