DSXchange

I know I can type them manually... or copy/paste from notepad or the likes... but in the Enterprise stage I don't have to, so I would just be nice if the Connector stage allowed it too....

I would like the ability to concatenate parameters in the table name field. Right now a new parameter overwrites the existing one automatically in the Connector stage (at least in v. 8.1).

Are you running the 4 instances simultane and writing to a single (the same) sequential file?

As mentioned by Kryt0n...

Make sure you have indices on your sql sever table otherwise you will get deadlocks...

You must have more in the job than: exec_commd-->user_variable-->parallel job ...since you use the output "StartLoop.$Counter". I think the loop separator is set comma as default som if you pass your query statement though the loop it will cut the query where it encounters the first comma ...

As far as I remember, then you will actually have to exit your session and log-on again for the image to be reflected correctly on the canvas.

Hi -

There are two things that have caused this error for me in a sparse lookup using a ODBC Connector stage:

1. Having unbounded string columns in the input stream
2. Having timestamps in the input stream

Use the Surrogate key generator to read the state file. Set the option "View state file" = yes

If you have managed to convert your input string correct to a ds date type (yyyy-mm-dd) then you should be able to insert this into a sql server date column.
Could you please poste an example of the input string for the transform?

...and what is happening within the shared container?

Please describe the job design of the generic job....

Opposite the ls you do on the Unix box, then you are actually defining two parameters to perform the list on in the XC stage in DS. ls sec* (on the current directory) and ls /bis_data/input/ You need to have you command from DS to look like this: ls /bis_data/input/sec* In the command box write: ls ...

And that would be...modulus or?

If you want to know if your job is re-partitioning then you can dump the score into the log - or check the row counts on each partition in the monitor. The key you used for the hash partition in the previous job - is that the same key you need to use for your join in the current job? If yes, then yo...

lets just assume that you are running on a 2-node config file and you have a key based partition on the "join" column. lets that you'll have the key 100, 300, 400 and 500 running on one node/partition and the key 200 on the second node... in this case the group numbers generated based on t...