DSXchange

Ok... imported now but is it working for you? While the "S" and the "-" are equivalents, the "V" and the "." are not.

Swapped out the quote tags for code tags. And from what I recall, the decimal point in those picture clauses means it's not an implied decimal (V) but rather an explicit one there in the data so it's not something you should change. From other posts here, I think the leading minus sign might need to...

59 columns... but still.

And just to be anal, being in a "Data Warehouse environment" really isn't a consideration here. Regardless of environment, if the restrictions that RCP put on your processing don't rule it out you can certainly use it for data movement.

You may have achieved this using transformer looping but what did you actually achieve? Not the desired end result. As already noted, it's a horizon pivot of columns to rows.

No, this is just a horizontal pivot. I don't see any need off the top of my head for transformer looping and there are other posts here that discuss how to pivot 'column headings' along with their associated data. Create 59 new columns in the transformer with whatever values you need for each "...

Sorry but that doesn't answer the question. What format is it expecting? Spell it out for us like YYYY-MM-DD HH... etc etc.

Your "without much transformation" statement is worrisome. If you had said "without any transformations" then I would agree that RCP would be the way to go.

No way for me to check, seem to recall a summary at the end of the log entries which would have all that.

That's a different question... check in the job's log for that run.

I'm sure they're perfectly well aware of how to kill it, should they desire to do so. This conversation is more about the why of it, as in why it doesn't end on its own rather than needing to be killed.

December7, any luck with researching this? Any help from support?

1. Yes.
2. DSGetLinkInfo() with the DSJ.LINKROWCOUNT InfoType.

Both show the number of insert requests made.

Note that we're not discussing the data type here but rather a property called data element. It's in the documentation and has been discussed in the forums here, for example in this post.

And then as noted, setting the Data Element to XML tells it that it is already XML and to leave it alone as it passed through.

Not possible with ODBC as far as I know. Since you are on a Windows server, you should have some 'extra' stages specific to SQL Server and those would be the ones to use. From memory, an OLEDB and perhaps even a specific SQL Server Bulk Load stage? Searches here should turn up discussions on the top...