DSXchange

Thats why, now, i think it would be best to get two temporary tables set up and use the sql to get done with the first three conditions mentioned in the other post. And for the last condition, just a reference lookup with the hashed file. Two jobs at max.

I think it would be best to load the data into two temp tables to run "Real" sql on them.
I believe vsi wants to accomplish this. And that is pretty heavy sql. And if the number of records are large then it will really eat up lot of your time. As Ken mentioned, go with the temp table approach.

Do you have execute permission on the stored procedure?

How many columns are you pulling in the odbc stage?
What if you access the table via OCI stage? do you still get that kind of problem?

Are you able to do a simple select from sql server using that odbc connection?
Also, if you read about using stored procedures via odbc stage, it only allows IN and INOUT parameters. What type of parameters does your stored procedure take.?

Error executing View Data command: ##E TFCC 000003 11:15:40(222) <APT_CombinedOperatorController,0> U_TRUNCATED_CHAR_FOUND encountered. I have experienced this problem when I have had bad data in my data set file or flat file. Try loading less number of columns, and see if the error still persists.

Welcome aboard
What database are you accessing?
Are you getting this error message with only this job? Or is it in all the jobs in which you are using an odbc stage and trying to view the data ?
Look at this post and read Ray's comment on "Internal error (81021)"

bryan wrote:echo
string"\n" > filename

Are you putting it in the command stage exactly like that
Enclose it in double quotes. THe entire command.[/code]

, you said "while compiling".
THen yes, look at the constraint. Maybe the variable is hidden somewhere there.

In that particular job you must be calling a custom routine which must be using that variable and was never initialized/used. Just initialize it and you will be fine.

how exactly are you using the echo command?
Can you tell us whats the syntax you are using there ?

I have no idea why ;1 is concatenated with the name
About the type cast, do you have any sql type as BIGINT ?
If there is, change it in datastage to numeric. BIGINT doesnt work with datastage. It gives type cast error. I got that before.

When you say its successfull as in no warning message in Datastage what so ever, even the time part was not truncated. How can that be.
Plus you cannot change the length, your DBA can. But be ready to have a very good reason to get the length changed.

Its due to the constraints of the OP with respect to DS version, OS that a work arounds are provided.
Atleast if the OP was on unix, life would have become so much easier
I would say Craig has a very valid point. Just upgrade.

It depends. Look at the length and precision of datetime in sql server. If it is 23 that means it will accept timestamp as input. If it is 10 then it will not as it will only accept date part. In sql server there is no data type "date". For both date and timestamp, usually datetime is used. The leng...