DSXchange

For the record, some of my favorite posts are Vincent's. I think his blogs are great too. I like to read them over once and a while just to see how he explained something. Ken, your long answers leave nothing undone. Your documentation is first class as well. Don't forget Michael Hester or Andy Sorr...

I do have an example of where I broke this rule. We had a customer which rented movies. They had an application which purchased these movies based on a statistical model of previous purchases for all their stores. We built a datamart which reported on these purchases. They wanted a real-time version...

I agree. It is not about quantity though. Back to the post. Your ETL should be clean, easy to follow, in the words of Ray and Arnd write it so the next developer can understand what you built. Hiding ETL in triggers and stored procedures on the insert or updates of targets is not easy to follow. I d...

I have to agree with Ken here. Trigger is a trick. It is not solid ETL. I hate to follow developers which ETL lies outside of DataStage in stored procedures, triggers, shell scripts or whatever. I think indexes are very valid to improve performance especially in staging tables. Not a problem there. ...

Ken Bland posted the code to set all of the purge settings for all jobs. This code is to clear mutiple instances on a single job.

If you look in the log file they do not store job name. They create place holders for it with %s and I think %1 and %2. I think that is so that you can rename the job easily.

On the source SQL. It should be an option. Read help on the choices. You will understand why.

That is correct. You need to put a full path on the dsx to put it somewhere other than the current directory.

One day only on the less colorful logo. Okay?

SET DSImportCmd=C:\Progra~1\Ascential\DataStage7.5.1\dsimport.exe for /F "tokens=1" %%i in (%DsxList%) do ( ECHO Importing %%i to Project: %Project% on Host: %Host% echo %DSImportCmd% /H=%Host% /U=%User% /P=%Password% %Project% %ProjectDir%\%%i >> %LogFileName% %DSImportCmd% /...

Here is the second one.





This does a whole project backup.

Might need this line.

Aim to please. for /F "tokens=1" %%i in (%JobList%) do ( ECHO Exporting %%i to Project: %Project% on Host: %Host% echo "%DSExportCmd% /H=%Host% /U=%User% /P=%Password% /JOB=%%i %Project% %%i.dsx" >> %LogFileName% %DSExportCmd% /H=%Host% /U=%User% /P=%Password% /JOB=%%...

I think doing this in one job is fine.

You got to be kidding.

Happy?