Can you extend the import set table?

[nadzm]

is it possible to:

1. import data as a csv which creates an import set table e.g. new_import_table

2. create a new table called new_data that extends from the import set table I created in step 1 above - this is to match all the fields in point 3 below

3. create a transform map and then auto-map the fields

is there any issue in doing this?

[tony_barratt]

Hi Nadeem,

Yes.

Import set tables are essentially temporary - by default they hang around for 7 days.

The overall   concept is that records in the import set table are mapped to persistent   storage.

Did you have something in mind you wanted to achieve?

Best Regards

Tony

[nadzm]

basically i want to import a table (data and fields) to 'permanent storage' from an import set table without having to manually create loads of fields in the target table...i understand that i can do this in other ways; xml...but my export is 5GB, breaking that down would also be cumbersome....hence im trying to find a quick/other solution:)   for a one-off import, what i find difficult to understand is if i can create an import set table with all the fields and data i want,   then why cant i just copy all of this to a permanent table!?

what i also found was that making the import set-table 'extensible' actually seems to stop the scheduled cleanup from wiping the data from it....maybe i could leave it like this!

[srinivasthelu · Accepted solution]

Even if you create a child table of your custom import set table, that is still considered as 'import set' table.

The child table will inherit all the properties of its parent table. So, That way clean job wont give any excuse for the newly created child table.

Create a new table and copy the values using script for the first time. from the next run onwards you can always have   another dedicated transform map for this.