DSXchange

For MS-SQL Server, ODBC is the preferred method...what else are you looking for?

Not sure why ODBC would be a problem, but if you want another method, and you have 8.1 with FP1, check out the entry in my blog below for creating Shared Tables manually, using a .csv file.

Ernie

Keep searching..... Ultimately you are on the right track...they are very similar, but there are slightly different settings for these depending on your release and your platform....

Ernie

Now that you have "enabled" your Job you have to construct an ISD application that "deploys" it as an Operation that is part of a Service. Too much to discuss here, but you need to look for, and then spend time learning, the Information Server Console. This is a separate icon and...

Change the model of your execution..... retrieve only high level keys....then based on a selection from there, drill down further....then drill further...create 3 or 4 different REST services that are built for drilling down, so that none of them ever return a huge number of rows. Also consider redu...

Sounds like a very creative technique.....alternatives would be a dummy table or flat file....where someone would say "why do we have this dummy table in production?" .... I like it....it's completely self controlled and carries all of it's "data" with it..... I say "go for ...

You will have to force that relationship somehow, with counters or other such things (is there a key in common between them) and then sort it appropriately. You may need to build your own artificial keys along the way. Tell us more about the upstream data and how you are deriving it. This is not a W...

It's possible it's a volume issue, or it could also be a particular data item issue... (binary zeros or other strange characters have been known to blow up the SOAP processing)..... On another note, SOAP is probably not a good vehicle for returning a large quantity of rows. Try to qualify them in so...

Hard to say.....it's a fairly generic error. Here are some things to try: Did the Job abort? Is there anything in the DS Director log? Are you passing any Job Parameters? [is there any input message for this service?]....if so, they would need to be passed via url when using REST. Get a copy of SOAP...

It certainly could be the release, but there are other issues to consider also. Tell us more about the Job. What is the source and what is the target? ...and exactly what Stages are you using for the source and target? If you are getting "no data found," it could be likely that it isn't fi...

Exactly what release are you using?

Yeah..that one's a tough call. Hard to say...too many layers along the way.... Have you tried the DB2 API Stage under the exact same circumstances? Perhaps it reacts differently.

Ernie

Just guessing, but since this is Server, but here's a suggesetion that might work "IF" the -911 is something that can be detected on an "input" action (update, insert, or custom SQL from an input link). Use Ray's design suggestions above in a bogus first stage and link.....Create...

: ) that was genuinely funny.

let's please put ths thread out of its misery and end it.

After the operational metadata is imported, run Advanced Services so that it can become associated with the particular job and other metadata assets.

Ernie