Data Ingestion from Oracle DB to SQL Server

Appian is a business process automation platform, but not a ETL tool and no good fit for just shifting large volumes of data from one DB to another.

Can you elaborate on your use case and share more details?

I currently have view access to an Oracle database and need to extract data in batches. The data will serve as a source for my task and will be loaded from a staging table to another destination using a stored procedure.

Here is the approach I am considering:

1. Batchwise Data Extraction:

   • I plan to query data from the Oracle database in batches to efficiently manage the extraction process.

2. Appian Data Store Entity:

   • My intention is to store the extracted data in an Appian Data Store Entity, utilizing Appian's capabilities for handling and managing data.

3. Error Log Mechanism:

   • I aim to implement a robust error log mechanism within Appian to track any issues that may arise during the extraction process.

4. Stored Procedure for Data Loading:

   • Once the data is in the Appian Data Store Entity, I plan to use a stored procedure to load it from the staging table to the final destination.

I currently have view access to an Oracle database and need to extract data in batches. The data will serve as a source for my task and will be loaded from a staging table to another destination using a stored procedure.

Here is the approach I am considering:

1. Batchwise Data Extraction:

   • I plan to query data from the Oracle database in batches to efficiently manage the extraction process.

2. Appian Data Store Entity:

   • My intention is to store the extracted data in an Appian Data Store Entity, utilizing Appian's capabilities for handling and managing data.

3. Error Log Mechanism:

   • I aim to implement a robust error log mechanism within Appian to track any issues that may arise during the extraction process.

4. Stored Procedure for Data Loading:

   • Once the data is in the Appian Data Store Entity, I plan to use a stored procedure to load it from the staging table to the final destination.

If I would have to do it in Appian, I would do it in the way you planned out.

How will be the performance.

I am missing all the relevant details to make any assumptions on performance.

An Appian approach typically is very slow when compared to using a real ETL tool. But if performance is not of concern to you ...

Ok   thank you for your help