DSXchange

I've recently pivoted 16 columns, there really shouldn't be a limit like that. Perhaps there is a data issue in the 8th column? You should probably involve your official support provider, see if perhaps that is a known issue with that stage.

Category is not available via the API AFAIK, so you'll need to query the repository directly from a job or from the command line for that. See if this post helps or search for DS_JOBS here.

That's not a simple problem to solve properly, hence the suggestion to leverage something else that already does that rather than roll your own solution. You could also do an exact search here for "daylight savings" and see what kind of answers other people got when they had a similar requ...

Yes, what you need to do is not run around finding other posts you think are similar and adding replies to them, rather you should start a new post and explain in detail your version of the problem.

Without asking why one would update the client without updating the server as well, you'd need to let us know what errors you are seeing before anyone could really help. What kind of 'aborts'?

So... you have to bounce the database to solve that or that is just something that works? If so, that would indicate a bigger problem to me.

Your example doesn't match your "i.e." written description.

Does "read data into" mean you are writing to a file? Or simply trying to read it?

Why? If there was no other option then that would be a 'work around', sure, but the Delimiter String property should solve this easily.

Never tried, but it seems to me you'd need to either create the file without a header row and include those header values as the first record you write. That or create a file with just that header record as a template, stash it somewhere, copy it 'before job' to your target destination and then set ...

However, that's pretty specific to 8.x, it's it much simpler for earlier versions? Isn't is just 31538 assuming you haven't changed the default port?

:wink: I would wager it's the trailing semi-colon after the LOGTO that's causing it to fail, it doesn't need one, only 'sql' does. I'm afraid I don't know what the proper separator would be and have only done this in a 'here document' style before: ./bin/uvsh<<EOF LOGTO <Project> SELECT XXXXXX EOF A...

Have you actually tried it yet? You have to escape quotes but I don't think you do for slashes. Try it and let us know. And it simply being 'a path' has no bearing on if it should be defined at the project level or not.

True, dat.

In other words, no, there's no built-in function or stage to do this.