We’re testing DS 4.8 in order to upgrade to this version from 4.1.
Today I was testing a data extraction from Sybase ASE to a file and observed that the varchar columns in the flat file has the trailing spaces trimmed, when in 4.1 the column has the extra spaces like the source table.
Beside the discussion regarding if the behaviour is now correct or not, we want to know if anybody knows about a change in the default behaviour for varchar data with extra blanks, not just in the extract or load, but also in the comparison, for instance in lookups.
However, usually we wait for at least the first Patch level of SP before trying to test it. Anyway, since we’re having extraordinary delays with the new HW for the STAGING server, there is a fair chance that we can use SP9 instead of SP8.
Said that, do you see the behaviour reported changed in any version?
But you do have a point there. In the new installation, we do encourage to use the actual production DSconfig but we (I) missed the key file, so the new installation was made with a “default” config file. I don’t remember tweaking the file on this topics but since the DSConfig came from the 15.2 version, certainly is possible.
Anyway, the DB team is rolling back the new Sybase client and installing the previous one. If the Ds behavior remains I’ll check the DSConfig.
BTW, do you where to look in order to narrow the search a bit.
I usually to a search of the entire file, looking for keywords. The problem is that often the factory defaults are in the file. It has to be added to the file to over-ride the default.
Seriously, if you’re knee deep in the smelly stuff, opening a ticket with SAP should be your number 1 point of action.
That annual maintenance fee is not only there to allow you to download any new version of SAP Data Services but also allows you to ruin someone’s day at SAP with your newly found bug - nor not. Just be prepared for the usual “is it plugged in?” “did you actually turn the appliance on?” questions and answer game but once you get beyond that, you will typically get some solid answers. At least that has been my experience with SAP support though your mileage may vary.
So, we opened a case and then the expected outcome, days and days of post and answer to try to clarify the issue, discard “proposed solutions”, get config information that is pointless, etc.
The thing is DS changed some behavior between 4.1 and 4.2 regarding trailing blanks and other stuff, taking note of the source DB configuration (in 4.1 I understood that was only depended in the DB brand and model, not specific tweaks of each instance). Anyway, support wasn’t able to provide us with a clear statement in any doc that refer to this. They only give a KBA (hidden to the public) mentioning this changes but in Information Steward (We’re told that is assumed that those behaviors are the same of DS (???) ).
So, since this took too long, we are closing the case and going on with an in deep check of all of our DFs where we extract varchar columns from Sybase ASE.
Your experience explains why some of my clients are giving up on SAP support. Their thinking is why bother with SAP when the client gets more useful answers out of their consultants. Sure, we can’t fix SAP code, but then again, neither can SAP.
(BOB member since 2006-02-02)
(BOB member since 2007-01-10)
(BOB member since 2007-09-12)
(BOB member since 2007-09-12)
(BOB member since 2006-02-02)
Just be prepared for the usual “is it plugged in?” “did you actually turn the appliance on?” questions and answer game but once you get beyond that, you will typically get some solid answers. At least that has been my experience with SAP support though your mileage may vary.
(BOB member since 2007-01-10)