DSXchange

sun rays wrote:

chulett wrote:You might want to try using the LETTERS transform that is available under the Built-in/String category. Handles the syntax for you.

LETTERS Transform would stip off the numeric characters too.

True. Missed the 'numeric' part of the 'alpha numeric' question... doh!

You might want to try using the LETTERS transform that is available under the Built-in/String category. Handles the syntax for you.

Post your query.

As noted, a perfectly acceptable and very cool approach. I've used it to generate calendar data, gobs of test data and sometimes (with a constraint of @FALSE) to clear a hashed file lookup that is also written to in the same job before the main input stream starts. I believe that I first saw it in a...

abby wrote:The mandatory column here does allow a Null value as per the table definition.

Then it's not mandatory.

Not in a PX job itself without inclusion of the dreaded BASIC Transformer, but we're talking in a Sequence job which is a form of Server job. So the answer is yes.

You are replacing null values in the file with the word "null"? You should be replacing it with the system variable @NULL instead, if I'm understanding your problem.

Looks like this is a Client command and may only work if the Server is running on the same machine. I'll have to experiment a little more with this from the office tomorrow. Too many other fish to fry tonight.

Windows as in on the client or a Windows Server install only?

When I said "Use two links", I was being facitious and hoping to provoke a reason for the "I don't want to split my DS into separate operations" comment. You can use a customized sql to handle your insert/update statement. Next time, instead of simply rolling your eyes and making a generic statement...

I know it's a trial and all, so a couple of questions.

1) Can the big green button be made a little... less big?

2) Once one becomes a Premium Member, shouldn't the button basically go away when that member is logged on and reading the forums?

Thanks.

I found what is locking out the Rows Per Transaction field - it's when I select localuv in the Data Source Name field, otherwise I can change it. Since this table is hosted 'in the Project' I thought that was the way to go with it... what am I missing?

So, with all this in mind, still think it worthwhile to change the Transaction Isolation in the UV stage?

Must be a new feature in 7.5.1A. And you can delete a post as long as there is no reply to it, so could have deleted the duplicate post. It's a checkbox at the bottom when editing to 'Delete this post' when submitting the 'edit'.

Click 'Continue Trial' under the freakishly large green button. see, your last post looks like this: I think we need some clarification from the Editor; I don't think that all of my posts are going to be invisible to those who haven't got a premium membership - if that were the case I'd have to revi...