We edit a very basic mapping from a SQL Server table to the same table in PostgreSQL technologie. This mapping has just one filter on the source table.
The goal is to truncate the cible table and after to load it with source data with one filter on the source table.
The mapping bring two template and even with the "append mode" there is an intermediate table wich is create (and drop at the end).
We would like to have a direct "select ... from <source> where <clause>" and after a "insert into <cible> values ( :field1 , :filed2 , ...)" without temporary table.
Is it possible with standard template or do we have to create our specific template ?
Best Answer
R
Romain ALCARAZ
said
7 months ago
Hi Jérôme !
When you use different technologies on your source and target in a mapping, xDI will always add a LOAD step. You will see the same if you use the same technology (and possibly the same instance) but with your source and target in different metadatas. Sure It's not clean, but it's the principle.
And automatically, if there is a LOAD step, you always have a temporary table created to store your source elements. This table will be used on target to integrate your data, and probably to control data, or to detect data already created on target to perform insert/update mechanism, etc...
Don't forget that xDI is an ELT, so you always have an L (load) step, before the target.
1 Comment
R
Romain ALCARAZ
said
7 months ago
Answer
Hi Jérôme !
When you use different technologies on your source and target in a mapping, xDI will always add a LOAD step. You will see the same if you use the same technology (and possibly the same instance) but with your source and target in different metadatas. Sure It's not clean, but it's the principle.
And automatically, if there is a LOAD step, you always have a temporary table created to store your source elements. This table will be used on target to integrate your data, and probably to control data, or to detect data already created on target to perform insert/update mechanism, etc...
Don't forget that xDI is an ELT, so you always have an L (load) step, before the target.
Jérôme LESTEVEN
We edit a very basic mapping from a SQL Server table to the same table in PostgreSQL technologie. This mapping has just one filter on the source table.
The goal is to truncate the cible table and after to load it with source data with one filter on the source table.
The mapping bring two template and even with the "append mode" there is an intermediate table wich is create (and drop at the end).
We would like to have a direct "select ... from <source> where <clause>" and after a "insert into <cible> values ( :field1 , :filed2 , ...)" without temporary table.
Is it possible with standard template or do we have to create our specific template ?
Hi Jérôme !
When you use different technologies on your source and target in a mapping, xDI will always add a LOAD step. You will see the same if you use the same technology (and possibly the same instance) but with your source and target in different metadatas. Sure It's not clean, but it's the principle.
And automatically, if there is a LOAD step, you always have a temporary table created to store your source elements. This table will be used on target to integrate your data, and probably to control data, or to detect data already created on target to perform insert/update mechanism, etc...
Don't forget that xDI is an ELT, so you always have an L (load) step, before the target.
Romain ALCARAZ
Hi Jérôme !
When you use different technologies on your source and target in a mapping, xDI will always add a LOAD step. You will see the same if you use the same technology (and possibly the same instance) but with your source and target in different metadatas. Sure It's not clean, but it's the principle.
And automatically, if there is a LOAD step, you always have a temporary table created to store your source elements. This table will be used on target to integrate your data, and probably to control data, or to detect data already created on target to perform insert/update mechanism, etc...
Don't forget that xDI is an ELT, so you always have an L (load) step, before the target.
-
Set webservice password dynamically in XDI
-
Unable to use "PATCH" as HTTP verb in a REST API call
-
SQL SERVER INTEGRATED SECURITY FOR RUNTIME LOGS
-
Microsoft SQL server "Could not establish a secure SQL Server connection using SSL encryption"
-
how to import SQLITE database
-
Chiffrement de fichier
-
Azure Service Bus - possible to connect to a topic?
-
Export Log
-
Error HttpRest metadata when reversing API
-
API key authentication instead of basic authentication
See all 17 topics