DSXchange

It is my understanding that MetaStage has a compare tool or report. You could also do it in Reporting Assistant. HAWK has an awesome tools for comparing anything.

Do an exact search for MonitorSeq or monitor job. There are several posts on this topic already.

Export the job and compare the 2 DSX files.

The split command has a funny syntax. It can split files by blocks, char or lines if I remember correctly. It names the files funny as well. The file names by default end up like fileaa, fileab, fileac. You can control the names a little bit but once again it is difficult to understand the syntax. O...

By the way I would backup develment every night. I would backup production once a week.

We usually backup at about 2 in the morning.

Do a search for DataStageBackup.bat. This has been covered a lot. This is a script I downloaded from ADN which is no longer available. I have modifed it slightly. It is available on my tips page.

I just clicked on EtlStats.zip and it asks open or save to download the file. Maybe your site has this blocked. Your link does not work because there is a comma on the end of the URL.

There is a job called MonitorSeq in EtlStats which you could modify to to send you an email if a job runs long. Rght now it gets row counts and emails the log of all jobs that fail in a sequence. Instead of a wrapper this would need to start at the same time or right after you start the job you want...

Start with one group like dstage. Put all developers including dsadm in this one group.

Wow it only took 4 months to respond to this post.

Why not use create table?

By the way the stage types are not very useful either. Does CODBCInput actually help you. The Input means it is output to an ODBC table.

Good luck because I don't think it has been posted. It is very complex to tie the ends together especially if there is no transform in between. You need to know a lot about the repository tables. I don't think there is any API call to get this.

I agree with Ray volume testing is important. Somethings break when you put more pressure on them. I always try to run the ETL from end to end, meaining every job. A full run or simulation of a production run is very important to successful implementation.

I would look at the 2 designs and see what is in common. If you truly need to merge dimensions then you may need to use QualityStage with some address matching. You need the cleanse and standardize first.

I would pick a subject area where both are strong.