DSXchange

We use a naming convention that the column name is the key. So CustomerID becomes the key for CustomerDim. We reseed these values right before we use them. I provided this job in EtlStats. It is called ETL_Reseed_SDKSequences. If you do a search on "reseed" then you will find other posts about this ...

Your key to the hashed file is 1? What was your key in the job you described?

How are you updating the hashed file?

Yes you can use environment variables as parameter values. There are several other best practices like having a ini file or a text file which is read with all the parameter values like pSourceDsn=MyDsn pSourceUser=EtlUser pSourcePwd=MyPassword Do a search on DSParams to see how parameters are can be...

If you read and write to the same hashed file then there is a possibility you can process the same record more than once. Records are stored randomly in a hashed file so you can read a record and write it back to somewhere deeper into the file. This is especially true if read with one record id and ...

There is no first record in a hashed file. It is stored randomly. You can get a list of the item ids with a select list.



This will get you close.

You cannot do it directly. You have to write it somewhere in the job so the sequence can read it using UtilityHashLookup or a similar routine. The surrogate key routine is a similar concept. Some process needs to put the first value in SDKSequences hashed file. Each call to the routine adds one to t...

I would start with

ps -ef | grep phantom

Now the problem is what project do these jobs belong to.

That is all you need. In UNIX the uv.rc script starts and stops at bootup. It maybe called ds.rc now. Not sure.

Mark

Welcome to the dark side. I see you are posting now. Great. Have fun.

It was okay. I needed to know. Just don't want to encourage others to post private messages to the top posters. It is a little overwhelming sometimes.

Yes. If you choose selective restore then you can pick either one. I think.

If you import all then they are imported in the order in the DSX. The appended one will go last therefore it will import both but the last one will overwrite the first one.

You could script it with dsjob. dsjob -report is what you need. There is a script I posted which loops through all jobs in one project to get the bmp images provided by %Designer% /H=%Host% /U=%User% /P=%Password% /SaveAsBmp=%BackupDir%%DsxDate%\%%i.bmp %Project% %%i >> %LogFileName% The script is c...

Most of the jobs which extract from DS_JOBS or DS_JOBOBJECTS have dictionary otems that may need to be created. They should be included in the zip file but if you cannot find them then post a question. I think these jobs are very useful.