DSXchange

I guess I would interested first in knowing why the job failed? It is simple to reset and rerun the job, but if there is a problem of some sort, then it may just fail again. Is that a concern?

I have an issue where my source databases can have all kinds of high ASCII characters (general from cut and paste operations) and since I use a src --> text file --> target, I end up with all kinds of problems. I borrowed a routine from some of the great minds here and then modified it to interpret ...

I am experimenting with the RDBMS Stage docs that supposedly teach you to handle it. I will post my results.

Bummer...

I tried your solution and it won't work for me, primarily because I don't have the OLEDB Stage available as we are running on AIX Unix. If I am wrong, please feel free to set me straight.

Thanks!

Hey Rod! Did you ever come to a resolution to this problem? I am having similar issues with regards to a straight pull involving novelists as well. Right now I am using SQL Server 2000 and DTS to move the data, but we keep getting hit by a bug that affects binary data being passed over a linked serv...

I can relate. That is known as the 'addition of undocumented features.'

Don't you know that is a good thing!

There is evidently another step that has to be done as well. I don't know if you did it, but here are the instructions as plucked from an email chain between our DataStage admins: Go to project properties, general tab, click on environment, click on user defined, right click uner details, add new ce...

As far as I know, SQL Server does not have that capability except with regards to internal encrypting of SP, view and job definitions.

If you don't require a high level of security, you could always put together a ROT13 (or some variation) pretty easily in DataStage.

As far as I know, SQL Server does not have that capability except with regards to internal encrypting of SP, view and job definitions.

If you don't require a high level of security, you could always put together a ROT13 (or some variation) pretty easily in DataStage.

Odd as this may seem, I am almost in agreement with Dinesh and the consultant. IBM has told us that the Development Client tools should not be run with less than 3 GB of RAM available. It is also quite apparent from our experience thus far with V8, that the Dev box needs to be very beefy due to the ...

Hi Bryceson,

The Administrator from our company said he was going to post it up somewhere, but I haven't seen it either. I know there is more going on yet though, because the problem still is not fixed.

Update of my migration progress: Having been pounding on V8's bug with multi-instanced jobs and log autopurge for a couple of weeks now, here is what we have learned at my company thus far: 1. There is a bug in V8 that appears when you have multi-instanced jobs and autopurge turned on for the logs. ...

Having been pounding on the issue of multi-instanced jobs and V8 for a couple of weeks now, here is what we have learned at my company thus far: 1. There is a bug in V8 that appears when you have multi-instanced jobs and autopurge turned on for the logs. They have issued a couple of patches and twea...

Do you have any quarantees that your datatypes between columns and data are always going to be consistent (treatable as varchar)? Even if this is true, I see you having great difficulty doing this with a metadata based tool like DataStage. You could possibly consider kicking the information you want...

Looking at your input, this does not seem like a data transformation as much as setting an upper limit with an assumed 1 as the starting point. As Craig pointed out, is there more to it? What are your business requirements?