# Table exports for JDBC systems are now available

**URL:** <https://community.palantir.com/t/table-exports-for-jdbc-systems-are-now-available/555>\
**Category:** Inside the Product\
**Tags:** data-connection\
**Created:** [June 28, 2024, 4:04am UTC](https://community.palantir.com/t/table-exports-for-jdbc-systems-are-now-available/555 "2024-06-28T04:04:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![krandoing](https://avatars.discourse-cdn.com/v4/letter/k/cdc98d/32.png) [@krandoing](https://community.palantir.com/u/krandoing)\
**Post date:** [June 28, 2024, 4:04am UTC](https://community.palantir.com/t/table-exports-for-jdbc-systems-are-now-available/555/1 "2024-06-28T04:04:05Z")

</div>

## [Table exports for JDBC systems are now available](https://www.palantir.com/docs/foundry/announcements/2024-06/#table-exports-for-jdbc-systems-are-now-available)

Datasets can now be exported to external JDBC systems using [table exports](https://www.palantir.com/docs/foundry/data-connection/export-overview/#table-exports) in Data Connection. Table exports introduce a new user experience for configuring exports of tabular data through an intuitive interface, a rich export mode selection, and the ability to explore the target system to configure the export. Table exports will work with [custom JDBC systems](https://www.palantir.com/docs/foundry/data-integration/jdbc-sources/) configured with both direct connection and agent runtimes.

### Export modes

Table exports support six distinct export modes to accommodate your unique requirements:

- **Efficiently mirror dataset to external table (_recommended_):** The external table will always match what you see in the Foundry dataset.
- **Full dataset without truncation:** Always export a snapshot of the entire view of the Foundry dataset, without truncating the external table first.
- **Full dataset with truncation:** Truncate (drop) the target table, then export a snapshot of the full current dataset view.
- **Export incrementally:** Exports _only_ unexported transactions from the current view without truncating the target table.
- **Export incrementally with truncation:** Truncate (drop) the target table, then export only transactions from the current view that have not previously been exported.
- **Export incrementally and fail if not `APPEND`:** Exports only unexported transactions from the current view, failing if there is a `SNAPSHOT`, `UPDATE`, or `DELETE` transaction (after the first run).

Learn more about the [details of each export mode](https://www.palantir.com/docs/foundry/data-connection/export-overview/#export-mode) in our documentation.

 ![tej1-1](https://canada1.discourse-cdn.com/palantir/original/1X/0e88358c60e51195b191ac7ae6156c5e5569192f.png)

_Example of an export mode selection in Data Connection._

### Explore target systems

For a dataset to be exported, its schema _must_ match the schema of a table on the target system. To help you configure the correct table, a source explorer is available to navigate all schemas and tables available on the target source.

 ![tej2-1](https://canada1.discourse-cdn.com/palantir/original/1X/3e168d3de7a8222c43dbfbcff6ba2f352a509c0a.png)

_Example of a source exploration dialog._

### Migrate from export tasks

The addition of table exports is intended to replace the usage of the now sunsetted [export tasks](https://www.palantir.com/docs/foundry/data-connection/export-tasks/) to export tabular data, and every user of export tasks is encouraged to migrate to table exports. Learn more about the [differences between Data Connection exports and export tasks](https://www.palantir.com/docs/foundry/data-connection/export-overview/#exports-vs-export-tasks), and learn how to [migrate your workflows](https://www.palantir.com/docs/foundry/data-connection/export-overview/#migrating-from-export-tasks-to-table-exports).

### What’s next on the development roadmap?

Currently, table exports are only available for [custom JDBC sources](https://www.palantir.com/docs/foundry/data-integration/jdbc-sources/#jdbc-sources). We plan to expand support for more connector types in the near future.

---

<div class="post-metadata">

**Author:** ![nicornk](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/nicornk/32/192_2.png) [@nicornk](https://community.palantir.com/u/nicornk)\
**Post date:** [June 29, 2024, 4:16am UTC](https://community.palantir.com/t/table-exports-for-jdbc-systems-are-now-available/555/2 "2024-06-29T04:16:30Z")

</div>

Since the new table exports are less flexible than legacy export tasks could you please add more documentation how to use external transforms for JDBC sources, including examples of pre- and post-sql?  
Those configuration options have been very convenient to trigger processing of the exported data in the target system.