DSXchange

Sure can. Search DSXchange for vertical pivot - there are at least three different ways available in server jobs. Which to use depends on your particular circumstances, in particular how many distinct values there might be per row and whether this number is fixed or variable.

Then an always-running job that does exactly that would seem to me to be exactly what you require.

When did you receive your software? I had a similar problem with 8.0 - I received the software before FastTrack was available and my license some time later, so I had the ridiculous situation of having FastTrack licensed but not installed!

I suspect, from context, that the request here is about getting metadata that are already stored within SQL Server tables into BG. Not getting definitions of SQL Server tables into BG.

Tell us the expression that you used to effect the transformation, as well as the data types of the input and output fields. Without that we would be unable to assist without guessing what you did, a probably unproductive enterprise.

Change the format to "no line terminators" then your Convert() function will work. Of course you will then only have one line of data.

Most find commands have an option to limit the number of levels of search.

Are you SURE that that message is coming from the date column? The mention of "€8" suggests that something else may be involved.

It may also be that null is not being handled gracefully.

Search also for VERIFY.SQL command, and UV.ACCOUNT table.

Search worked for me, were you not able to search for some reason?

What are you supposed to do, then, if the number of fields supplied is insufficient? (That's the same question, with mention of any particular number removed. And that's the problem you need to address before designing anything.)

That will depend totally on the format in which your metadata are stored in SQL Server. I daresay that it's not compatible with the formats used in the unified repository used for Information Server products and therefore will require some manipulation, which is why I suggested DataStage earlier.

Describe the process you are using to "import the schema file" fully.

Your job parameter needs to have the intermediate quote characters.

Resist the requirement. There's nothing sensible that an ETL tool can do with a CLOB.