DSXchange

What do I do to get the sequence numbers normally?Do I need to change the block size?

I have a job that runs on 2 nodes.I created the statefile through the surrogate key generator stage create option. I tried to generate the sequence numbers for 107 source records. The numbers were generated as 1 - 53 on node1 1001-1054 on node2 I was expecting that the sequence numbers would be from...

NULL means unknown value and empty means there is no value.A text file can have empty but it cannot have NULLs.if a field is empty or possible to be empty then select the option Null field value=''
and make the possible columns to NULL yes

We cannot handle that warning since we will need to handle on test and production environments which is not accepted by our architects. Hence use Enterprise stage.

It is Nvarchar which I am reading it as timestamp microseconds

ray.wurlod wrote:You can change from fatal to warning in the Connector stage itself, for size mismatch and data type mismatch. They are two separate properties. ...

The problem is we should not have warnings in the jobs.I understand in this situation I must use enterprise stage.

I am using a column EFF_DT timestamp ,microseconds length 27, and scale 7.In SQL Server it is defined as DATETIME2(7).When i ran the job i found the warning below and we should not have a single warning in our jobs as per rules.Please suggest a solution to eliminate this "Schema reconciliation ...

ray.wurlod wrote:At what point is this conversion taking place and are you expecting it to be performed implicitly or are you using an explicit conversion function? ...

I am not converting that timestamp to varchar or nvarchar at all.I am using that column as timestamp as it is in the lookup.

If you are on a version earlier than 8.5 it matters hugely to the Transformer stage - all functions in the Transformer stage other than the null-handling functions are intolerant of null. ... I am confused, as I have been thinking that tranformer checks the field for nulls only on the output link o...

I am reading a timestamp (microseconds) column from an SQL server table and using it as akey in the lookup stage following ODBC Enterprise stage.The job is aborting with an error "No default type conversion from type "timestamp[microseconds]" to type "ustring[max=32]". But n...

ray.wurlod wrote:Defined as not nullable on the reference input to the Lookup stage? ...

Yes Ray,but I wonder how does it matter to transformer..??

I have a lookup stage and I am pulling a flag that has value 'Y', from the reference and checking for NULLs for that field in the constraint of the transformer following lookup. I am using IsNull(Flag) in the constraint.I am getting the error "Null Handling done on not nullable field" but ...

Use the first and second columns in sort as sorting keys in descending order and generate the sequence numbers until the value in the key col1(1000) is changed.That can be achieved using stage variables in the transformer

Thanks Ray for your reply.Partition occurs only on input link but in this scenario what parition would same partition invoke? Since I am not a premium member ,I could understand from your reply that 1 file per partition at the sequential file stage and the same is applied to copy stage but what abou...

This is not an interview question and is just for my understanding. A sequential file stage is executed in parallel(file pattern) and there is a data link to copy stage and then to dataset.The copy stage by default uses same partition.As per the defintion of same parition it has to apply the preceed...