DSXchange

Hi Stephan and all I naively assumed that specifying the primary key columns for a UV table meant that there would be an index on these key columns. When data volumes increased I noticed the performance deteriorated. Using the command line interface to examine the UV table I noticed no index so I cr...

Two points on this. Firstly, Paul Young (my colleague) is well aware of the points raised so far about license. (We followed previous threads on this topic most caerfully) When Paul's code runs as job control there is no warning in the job log but when run as a function there is (regardless of the p...

Hi when creating and using uv tables for use in lookups you specify which columns form the key. Please be aware that this does not mean that an index is created on those columns and if there are many rows in the uv table then performance will suffer. It is possible to create an index on the uv table...

Hello Ray we see both DSD.RUN and DSD.StageRun and lots of processes. Yes jobs and processes are reported as finished in Monitor. We are now capturing dsd,lockd log file but nothing is reported apart from normal start. We have changed interval for dsdlockd to 300. Still it seems that defunct process...

We have 2 instances of a datastage job running simultaneously on a Sun Solaris server running Datstage 6.01. There are never more than 2 jobs running. When one job ends it starts another one running provided there are no more than 2 jobs running. All these jobs finish with no errors or warnings and ...

Ray thanks for pointing out that UV tables don't have indexes unless they are manually created. I had assumed (incorrectly) that checking columns to specify the key when the UV table is created by a Datastage job would put an index on these columns. As the data volume grew the performance dropped (p...

Hello Jan yes. Use the following but make sure that the first column is marked as a key on the column definitions tab and use the following in column descriptions field AND NOTE THE USE THE DOUBLE SLASH in the second column description: /InvoiceRow/RowIdentifier/#PCDATA /InvoiceRow//RowFreeText/#PCD...

assuming your flat csv file input is read into two fields put the following in the description fields of the XML writer stage and you should get what you want: /InvoiceRow/RowIdentifier/#PCDATA /InvoiceRow/RowIdentifier/RowFreeText/#PCDATA in the following output I have replaed the less than and gre...