DSXchange

You could use a database input stage and a lookup stage to join the table to itself - but you would be reading the 10 crores of data in twice. The user-defined SQL in a database input stage lets you join the table on the database engine and bring the data to your ETL server just once. It performs a ...

I think you should wait for QualityStage 8 before you redesign any of your jobs for parallel processing. QualityStage 8 and run your QualityStage 7 jobs as legacy jobs or you can keep QualityStage 7 server running. QualityStage 7 parallel jobs may need some rework to run under version 8 .

This looks like a transformer error and not a Siebel PACK error. If you create a job with the Siebel PACK writing the data directly to a Sequential file stage do you still get an error? It looks like you have derivation code in your Transformer that is aborting your job.

DataStage has the generate report function, MetaStage has publish to browser, the new Metadata Server has a browser based reporting tool. You can see more options in the FAQ or my post Navigating your project through the documentation Bermuda Triangle.

They can co-exist on the same server. You can use the client switcher on your desktop. The tricky part is segregating files and jobs. There can be some confusing if both projects are trying to read or write the same datasets. There will also be a database repository and WebSphere Application Server ...

Your existing DataStage and QualityStage jobs will run without any modifications on both a DataStage EE 7.x and 8.x implementation. On 7.x the full server environment runs alongside the parallel environment. So you only need to convert server jobs to parallel jobs if you want them to take advantage ...

You need to look at the help file and the PDF for the complex flat file stage. The trick is defining the file - you need to impart a Cobol copybook definition of the file. You may need to make some minor adjustments to the file for DataStage to recognise it as some copybooks do not conform strictly ...

It is a bit of a chore going back through all those previous versions. There are a few release notes to get through including the point releases and you can't really compare DataStage 5.2 to EE since they are radically different products. If you are preparing for a job interview the correct answer i...

You just need to make sure whoever installs it enters both the server and enterprise authorization codes. I've seen installs where they only enter the Enterprise code and this will prevent server jobs from being installed.

I dislike any transformations in the SQL select statement as they are mostly invisible to metadata reporting and can be hard to document and maintain. I would argue both the 50 case statement and 50 IF statement are both flawed. You should be looking at creating some type of business rule mapping ta...

10 Million records a month. You could use DataStage if you wanted to process this in under an hour but SSIS should be able to churn through this in a month. You should find that SSIS can load it and SQL Server can store it but the challenge is how much of that data you need to make available to user...

I haven't thrown in the towel, if you retire and I keep posting at my current rate for another 40 years I can overtake you.

Or that it didn't reject all the rows due to metadata mismatch. You got a reject link on that sequential file stage?

Since this is a parallel job make sure you have sorted and partitioned by your Name field so that matching rows are adjacent to each other and on the same node in the Transformer.

The DataStage Designer is not that different. QualityStage is fully integration so it has a complete GUI overhaul. Have a look at www.squidoo.com/datastage8 for links to DataStage 8 information or search this forum for DataStage 8 threads.