Skip to main content
To homepage To homepage

We are investigating the External Table feature to handle some special tables outside of TX, but still be able to utilize these for down-stream TX based processing.
We would like to orchestrate the updates of these table from TimeXtender, but it seems like pre- and post execute scripts are not allowed on these tables.

Can you confirm that pre- and post scripts are not available for external tables, alternatively provide a work-around to enable these. (It seems like a strange design choice to remove these hooks for this feature).
Also, I find the schema option page grayed out on the table settings for an External table, would be nice to be able to put the generated views in some meaningful containers (not dbo).

Thanks in advance.

Hi @Manggaard 

Please review our legacy documentation for external tables:

https://legacysupport.timextender.com/hc/en-us/articles/360051848171-Tables

It is possible to set pre- and post-scripts for for external tables

 

However this script will only be executed on deployment of the external table (not execution of the external table). 

If you would like to execute the script on execution of the DW, perhaps you can use the following workaround - create a new table (that is not external) or use an existing non-external table, and set the script to be executed as part of this table execution.

Regarding the schema for external tables, it will be set to the default schema for the DW, and as you mention this cannot be changed.

 

@Manggaard Did this answer your question? If so please help us by marking best answer above. Please let us know if you have any follow up questions 

@Manggaard Did this answer your question? If so please help us by marking best answer above. Please let us know if you have any follow up questions 

Hi Christian,

It did answer my question, but we have not persued this direction.
We have loaded the tables on the side, and surfaced the tables from the separate database (not managed by TimeXtender) using Custom Views in TX with 3-part naming to the other database (will exist on the same instance).
Thanks for the provided workaround.
/René

 

Reply


Terms and ConditionsCookie settings