DSXchange

In other words, exactly what has already been posted.

Welcome aboard. I don't believe that functionality is supported and I don't recall ever seeing any previous posts on the subject. Unless someone here has some direct experience with this, it would probably be best if you took this up with your official support provider and then post back here what y...

Perhaps there's a way to do this in 8.x but earlier versions did not support those "includes" and I had to combine the xsd files manually to get one it liked with everything in it.

It's an unspoken rule and common courtesy to start your own post when you have an issue. That way we know your version of the product, your operating system, you can mark it Resolved when your questions have been answered and you can post the gory details of your problem rather coming into a similar...

It's an unspoken rule and common courtesy to start your own post when you have an issue. That way we know your version of the product, your operating system, you can mark it Resolved when your questions have been answered and you can post the gory details of your problem rather coming into a similar...

When you start your own post. Not here.

...or properly quoting what / whom you are responding to. :wink: I'm not really sure what there is not to get. When you have a 'Windows only' database like SQL Server then (to me, anyway) I take that for granted that's one of the inherent differences in the platforms. You have an Enterprise stage th...

You need to start your own post rather than hi-jacking one that's over two years old.

Ah... now you're in the right place.

He means an uncommited data change made outside of DataStage was affecting the Data Viewer.

When I am specifying is not null... the error is too many arguments to function isnotnull That function takes one argument, the 'expression' to evaluate for null-ness. It would help stop all the guessing if you posted your actual constraint code as requested, that or just let us know you got it all...

Sreeni, who the heck are you talking to? Did you mean to quote me?

It's not their post.

Advice that you answer the question. That and double-check file level permissions in general.

Yah... as long as you always process a single year you can get away with that sql. Better though to code it so it always works regardless of the span of years... perhaps with an IN list using the concatenated values:
Something like that would be safe.

Yes, a stop / regen / restart but like I said, I don't recall all of the ramifications of making that change so you might want to hold off until more smarter people wander into the thread.