DSXchange

The important part is to be consistent. Create a standard and stick to it.

They should all be informational. Like target table as part of the job name. Extract, Load or Trans as part of the name. Maybe Hash as part of a job which builds a hashed file. I prefer stage names as DSN or database or schema names. Link names make more sense when they have the table or file name a...

This is the SQL you can run at TCL. You will have to limit it to the link type of BASIC. You will need to figure that out for yourself. SELECT DS_JOBOBJECTS.OLETYPE as LinkType, DS_JOBS.NAME as JobName, DS_JOBOBJECTS.NAME as LinkName, DS_JOBS.CATEGORY as Category FROM DS_JOBOBJECTS, DS_JOBS WHERE OB...

Parameter Navigator will allow you to change one parameter's default value in all jobs.

I would also look in the Adminstrator to see if buffering and how large your cache size is.

This has been answered before but if jobs are all related to one subject then one project is fine. A smaller project has a faster refresh in Director. It is easier to backup. It is difficult to run jobs from one project ot another. If you can isolate jobs so that you never need to run them then mult...

Post your script.

That is not that much. PX binaries must be a lot larger than server jobs.

I agree with Ken. Do a category at a time.

Hacking is the only way to get these strutures. The API is the only approved way to read these strutures. Very few APIs update these strutures.

How many jobs are you backing up?

should be:

I assume you are talking about a Oracle seqeunce number. There are lots of posts where the insert statement was modified to create the surrogate key using a sequence number. Do a search. I would try exact search on ".nextval".

Please edit your post and put code tags around the routine so it will be indented. At first glance it looks like the loop never gets to 'Starting' or ID = 0 so it continues forever.

It is simple. When you type in the hashed file name in the stage. Below it asks for a path or an account name. Choose Account Name and put in the project name.

If you use a path in both projects then it is even easier. The job can be exported from one project and imported into the other project.

You can refresh a hashed file in another project without running a job in that project. The hashed file has a path or account option below the name. Use the project name for the account and you can update the hash file directly. You could also use the full path to the hashed file.