What objects can be transferred

The main objects transferred are tables and data schemas.

In addition, certain types of endpoints support a transfer of empty objects or views.

Processing empty objects

Transfers between endpoints of different types (such as from PostgreSQL to ClickHouse) only move non-empty objects. For example, tables (in relational DBs) that don't contain tuples or contain zero number of fields aren't transferred.

Transfers between same-type endpoints (such as from PostgreSQL to PostgreSQL) move empty objects as part of a schema.

Processing VIEWs

In general, Yandex Data Transfer transfers VIEWs (from databases where these objects may exist) with some restrictions:

• Increment transfers don't replicate VIEW data changes.
• Snapshot and Snapshot and increment transfers (in the copy step) between same-type endpoints, such as from PostgreSQL to PostgreSQL, only move a VIEW as part of a schema. VIEW data (strings) aren't transferred. Schema transfers are configured by the "Schema transfer" setting and related settings available in some source endpoints.
• Snapshot and Snapshot and increment transfers (in the copy step) between endpoints of different types, such as from PostgreSQL to ClickHouse, move VIEW as regular tables and not as regular views. This feature allows converting and exporting data to external databases and can be helpful when making regular transfers of the Snapshot type.

Some sources may impose additional restrictions on transfers of VIEW and similar objects. For more information about how to work with views from particular sources, see Yandex Data Transfer specifics for sources and targets.