Fivetran Platform Connector - Table Reference Guide
You can use this guide to understand all tables in the Fivetran Platform Connector, organized by functional category. You'll see complete column definitions with data types and enumerated values where applicable.
Table categories
- Core account & access management
- Role-based access control (RBAC)
- Destinations & connections
- Logging & monitoring
- Usage & billing
- Source metadata (Enterprise+)
- Destination metadata (Enterprise+)
- Lineage mapping (Enterprise+)
- Change tracking (Enterprise+)
Core account & access management
ACCOUNT table
Stores top-level information for the Fivetran account this connection is configured for. This table always contains exactly one row.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | STRING | Primary key. Unique account identifier | |
name | STRING | Account name | |
created_at | TIMESTAMP | Account creation timestamp | |
status | STRING | Account status | ACTIVE, SUSPENDED, TRIAL |
country | STRING | Account country |
Primary key: id
Use cases:
- Account-level reporting and analytics
- Compliance and audit tracking
USER table
Contains information about all users across your Fivetran account(s).
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | STRING | Primary key. Unique user identifier | |
given_name | STRING | User's first name | |
family_name | STRING | User's last name | |
email | STRING | User's email address | |
email_disabled | BOOLEAN | Whether email notifications are disabled | |
verified | BOOLEAN | Whether user's email is verified | |
created_at | TIMESTAMP | User creation timestamp | |
phone | STRING | User's phone number |
Primary key: id
Use cases:
- User management and provisioning
- Contact management
TEAM table
Organizational teams within an account for access control.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | STRING | Primary key. Unique team identifier | |
name | STRING | Team name | |
description | STRING | Team description | |
parent_id | STRING | Parent team ID (for hierarchical teams) | |
account_id | STRING | Foreign key to account.id |
Primary key: id
Foreign keys: account_id → account.id
Use cases:
- Hierarchical team structure management
- Organizational reporting
TEAM_MEMBERSHIP table
Links users to teams with their assigned roles.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
user_id | STRING | Primary key (composite). Foreign key to user.id | |
team_id | STRING | Primary key. Foreign key to team.id | |
role_id | STRING | Primary key (composite). Foreign key to role.id | |
created_at | TIMESTAMP | Membership creation timestamp |
Primary key: user_id, team_id, role_id
Foreign keys:
user_id→user.idteam_id→team.idrole_id→role.id
Use cases:
- Team composition analysis
- Access auditing
- Role assignment tracking
Role-based access control (RBAC)
ROLE table
Custom roles with specific permissions and connector type restrictions.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | STRING | Primary key. Unique role identifier | |
name | STRING | Role name | |
description | STRING | Role description | |
account_id | STRING | Foreign key to account.id | |
connector_types | JSON | Array of connector_type IDs this role can access |
Primary key: id
Foreign keys: account_id → account.id
Use cases:
- Custom permission management
- Connector-specific access control
- Enterprise security policies
ROLE_PERMISSION table
Individual permissions assigned to each role.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
role_id | STRING | Primary key. Foreign key to role.id | |
permission | STRING | Primary key. Permission identifier |
Primary key: role_id, permission
Foreign keys: role_id → role.id
Use cases:
- Granular permission auditing
- Role permission comparison
- Security compliance reporting
ROLE_CONNECTOR_TYPE table
Maps roles to specific connector types they can access.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
role_id | STRING | Primary key. Foreign key to role.id | |
connector_type | STRING | Primary key. Connector type identifier |
Primary key: role_id, connector_type
Foreign keys: role_id → role.id
Use cases:
- Connector-level access control
- Service-specific permissions
- Security boundary enforcement
RESOURCE_MEMBERSHIP table
Central access control table linking users/teams/roles to specific resources.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | BIGINT | Primary key. Unique membership identifier | |
role_id | STRING | Foreign key to role.id | |
team_id | STRING | Foreign key to team.id | |
user_id | STRING | Foreign key to user.id | |
account_id | STRING | Foreign key to account.id | |
destination_id | STRING | Foreign key to destination.id | |
connection_id | STRING | Foreign key to connection.connection_id | |
organization_id | STRING | Organization identifier | |
created_at | TIMESTAMP | Membership creation timestamp |
Primary key: id
Foreign keys:
role_id→role.idteam_id→team.iduser_id→user.idaccount_id→account.iddestination_id→destination.idconnection_id→connection.connection_id
Use cases:
- Unified access control reporting
- Permission inheritance analysis
- Multi-resource access auditing
Destinations & connections
DESTINATION table
Data warehouse or database destinations where data is loaded.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | STRING | Primary key. Destination identifier | |
name | STRING | Destination name | |
account_id | STRING | Foreign key to account.id | |
created_at | TIMESTAMP | Destination creation timestamp | |
region | STRING | Cloud region where destination is deployed | AWS: us-east-1, us-west-2, eu-west-1, etc.GCP: us-central1, europe-west1, etc.Azure: eastus, westeurope, etc. |
is_active | BOOLEAN | Whether destination is active | |
deployment_type | STRING | Deployment model | Fivetran, Hybrid |
destination_type | STRING | Type of data warehouse/database | snowflake_db, bigquery_db, redshift, azure_synapse_analytics, databricks, postgres, mysql, etc. |
Primary key: id
Foreign keys: account_id → account.id
Use cases:
- Destination inventory management
- Multi-destination analytics
- Regional compliance tracking
CONNECTION table
Connections syncing data to destinations.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
connection_id | STRING | Primary key. Connection identifier | |
connecting_user_id | STRING | Foreign key to user.id | |
connector_type_id | STRING | Foreign key to connector_type.id | |
group_id | STRING | Foreign key to destination.id | |
connection_name | STRING | Connection name | |
signed_up | TIMESTAMP | Connection creation timestamp | |
paused | BOOLEAN | Whether connection is paused | |
sync_frequency | INTEGER | Sync frequency in minutes | |
deployment_type | STRING | Deployment model | Fivetran, Hybrid |
Primary key: connection_id
Foreign keys:
connecting_user_id→user.idconnector_type_id→connector_type.idgroup_id→destination.id
This table replaces the deprecated CONNECTOR table.
Use cases:
- Connection health monitoring
- Sync frequency analysis
- Connection lifecycle tracking
CONNECTOR_TYPE table
Catalog of available connector types.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | STRING | Primary key. Connector type identifier (e.g., 'salesforce', 'mysql') | |
official_connector_name | STRING | Display name of connector | |
type | STRING | Connector category | |
availability | STRING | Maturity/availability status | ALPHA, BETA, GA, DEPRECATED |
created_at | TIMESTAMP | Connector type creation timestamp | |
public_beta_at | TIMESTAMP | Public beta release timestamp | |
release_at | TIMESTAMP | General availability release timestamp | |
deleted | BOOLEAN | Whether connector type is deleted |
Primary key: id
Use cases:
- Connector availability tracking
- Beta vs. GA connector identification
- Connector adoption analysis
Logging & monitoring
LOG table
Comprehensive log events for all connections.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | STRING | Primary key (composite). Log event identifier | |
time | TIMESTAMP | Primary key (composite). Log event timestamp | |
connection_id | STRING | Foreign key to connection.connection_id | |
event | STRING | Event type/severity | INFO, WARNING, SEVERE |
message_event | STRING | Log event name identifying the specific operation. For all possible values, see the Log Events documentation section. | |
message_data | STRING | Event details in JSON format | |
sync_id | STRING | Associated sync identifier |
Primary key: id, time
Foreign keys: connection_id → connection.connection_id
Use cases:
- Connection troubleshooting
- Error pattern analysis
- Sync performance monitoring
- Alerting and notifications
CONNECTOR_SDK_LOG table
Logs specific to custom connectors built with the Fivetran Connector SDK.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | STRING | Primary key (composite). Log event identifier | |
event_time | TIMESTAMP | Primary key (composite). Log event timestamp | |
connection_id | STRING | Foreign key to connection.connection_id | |
level | STRING | Log severity level | INFO, WARNING, SEVERE, ERROR |
message | STRING | Log message in plain text | |
message_origin | STRING | Source of the log event | connector_sdk |
sync_id | STRING | Associated sync identifier |
Primary key: id, event_time
Foreign keys: connection_id → connection.connection_id
Use cases:
- Custom connector debugging
- SDK connector monitoring
- Development and testing validation
AUDIT_TRAIL table
Detailed audit log of all user actions and system changes. This table is available for Enterprise and Business Critical plans only.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | STRING | Primary key (composite). Event identifier | |
captured_at | TIMESTAMP | Primary key (composite). Action timestamp | |
user_id | STRING | Foreign key to user.id | |
action | STRING | Action type | CREATE, EDIT, DELETE |
interaction_method | STRING | How action was performed | WEB_UI, API, SYSTEM |
primary_resource_type | STRING | Primary resource type | ACCOUNT, DESTINATION, CONNECTION, TEAM, USER, TRANSFORMATION, ROLE, EXTERNAL_LOG_SERVICE |
primary_resource_id | STRING | Primary resource identifier | |
secondary_resource_type | STRING | Secondary resource type | ACCOUNT, DESTINATION, CONNECTION, TEAM, USER, TRANSFORMATION, ROLE, EXTERNAL_LOG_SERVICE |
secondary_resource_id | STRING | Secondary resource identifier | |
old_values | STRING | JSON of old resource attributes | |
new_values | STRING | JSON of new resource attributes |
Primary key: id, captured_at
Foreign keys: user_id → user.id
Availability: Enterprise and Business Critical plans only
Use cases:
- Security auditing
- Compliance reporting
- Change tracking
- Forensic analysis
AUDIT_TRAIL table log structure
This table stores detailed information about user actions and their results.
This table has the user_id, captured_at, and interaction_method columns that store information about the user who completed an action, when they did it, and how they interacted with the system. Events are composed of resources and actions where a resource is used to represent any type of system entity and an action represents something a user does.
For a given event, we support a primary and optional secondary resource to represent actions involving multiple entities, for example, adding a user to a team. This approach allows to decompose any high-level business logic to a collection of basic actions. The primary and secondary resources are specified based on the entity hierarchy and composition. The primary resource is a container, and the secondary resource is a member.
Some examples using this approach are as follows:
- An account (the container) is composed of destinations, connections, users, teams, and transformations (members).
- A team (the container) is composed of users (members).
- A destination (the container) contains an external log service (members).
To track changes to a resource's attributes and settings, we use the old_values and new_values columns that contain minimally-spanning JSON objects. It allows auditors to easily identify how an entity has changed as a result of an action. An example can be a user-renaming log event that contains an old value: {“name”: “Alice”} and a new value: {“name”: “Eve”}.
Usage & billing
INCREMENTAL_MAR table
Daily Monthly Active Rows (MAR) consumption per connection, schema, and table.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
destination_id | STRING | Primary key (composite). Foreign key to destination.id | |
connection_name | STRING | Primary key (composite). Foreign key to connection.connection_name | |
schema_name | STRING | Primary key (composite). Destination schema name | |
table_name | STRING | Primary key (composite). Destination table name | |
measured_date | DATE | Primary key (composite). Date of MAR measurement | |
sync_type | STRING | Primary key (composite). Type of sync | HISTORICAL, INCREMENTAL, UNKNOWN |
free_type | STRING | Billing category | PAID, INITIAL_SYNC, CONNECTOR_TRIAL, ACCOUNT_TRIAL, TABLE_TRIAL, NON_CBP_ACCOUNT, FREE_RESYNC, PROMOTION, SYSTEM, PRIVATE_PREVIEW, FREE_DBT, FREE_PLAN, CAP_PROMOTION, LDP_LIMITED_RESYNC, REFUND, TRANSFORMATION_TRIAL, ACTIVATION_TRIAL, FREE_ACTIVATION |
incremental_rows | BIGINT | Number of new distinct primary keys synced | |
updated_at | TIMESTAMP | MAR update timestamp |
Primary key: destination_id, connection_name, schema_name, table_name, measured_date, sync_type, free_type
Foreign keys:
destination_id→destination.idconnection_name→connection.connection_name
The deprecated connector_name column has been replaced by connection_name.
Use cases:
- Usage monitoring and forecasting
- Cost allocation by connection/table
- Free vs. paid MAR tracking
- Chargeback reporting
TRANSFORMATION_RUNS table
A transformation job consists of one or several models run in sequence. The TRANSFORMATION_RUNS table provides the total number of successful transformation model runs in each job and destination schema. Additionally, it provides a timestamp of when the model run count was updated.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
destination_id | STRING | Primary key (composite). Foreign key to destination.id | |
job_id | STRING | Primary key (composite). Transformation job identifier | |
project_type | STRING | Primary key (composite). Project type | DBT_CORE, QUICKSTART |
measured_date | DATE | Primary key (composite). Date of measurement | |
free_type | STRING | Billing category | PAID, INITIAL_SYNC, CONNECTOR_TRIAL, ACCOUNT_TRIAL, TABLE_TRIAL, NON_CBP_ACCOUNT, FREE_RESYNC, PROMOTION, SYSTEM, PRIVATE_PREVIEW, FREE_DBT, FREE_PLAN, CAP_PROMOTION, LDP_LIMITED_RESYNC, REFUND, TRANSFORMATION_TRIAL, ACTIVATION_TRIAL, FREE_ACTIVATION |
job_name | STRING | Transformation job name | |
model_runs | BIGINT | Number of model executions | |
updated_at | TIMESTAMP | Update timestamp |
Primary key: destination_id, job_id, project_type, measured_date, free_type
Foreign keys: destination_id → destination.id
Use cases:
- Transformation usage tracking
- dbt job monitoring
- Quickstart vs. custom model analysis
USAGE_COST table
Monthly cost summary per destination.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
measured_month | STRING | Primary key. Month of measurement (YYYY-MM format) | |
group_id | STRING | Primary key. Foreign key to destination.id | |
amount | DECIMAL(10,2) | Total dollar amount spent |
Primary key: measured_month, group_id
Foreign keys: group_id → destination.id
Use cases:
- Financial reporting
- Budget tracking
- Cost optimization analysis
CREDITS_USED table
Monthly credit consumption for credits-based billing plans.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
measured_month | STRING | Primary key. Month of measurement (YYYY-MM format) | |
group_id | STRING | Primary key. Foreign key to destination.id | |
credits_consumed | INTEGER | Number of credits consumed |
Primary key: measured_month, group_id
Foreign keys: group_id → destination.id
Use cases:
- Credit-based billing analysis
- Consumption forecasting
- Credit allocation tracking
Source metadata
Source metadata tables are available only on Enterprise and Business Critical plans.
SOURCE_SCHEMA table
Schemas detected in source systems.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | INTEGER | Primary key. Schema identifier | |
connection_id | STRING | Foreign key to connection.connection_id | |
name | STRING | Schema name | |
created_at | TIMESTAMP | Creation timestamp |
Primary key: id
Foreign keys: connection_id → connection.connection_id
Use cases:
- Source schema inventory
- Multi-schema connection tracking
- Schema discovery monitoring
SOURCE_TABLE table
Tables discovered in source systems (includes enabled and disabled tables).
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | BIGINT | Primary key. Table identifier | |
connection_id | STRING | Foreign key to connection.connection_id | |
schema_id | INTEGER | Foreign key to source_schema.id | |
name | STRING | Table name | |
created_at | TIMESTAMP | Creation timestamp |
Primary key: id
Foreign keys:
connection_id→connection.connection_idschema_id→source_schema.id
This table stores metadata for ALL tables that have ever been synced, including currently disabled tables.
Use cases:
- Source table catalog
- Table enablement tracking
- Historical table inventory
SOURCE_COLUMN table
Columns from source system tables with metadata.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | BIGINT | Primary key. Column identifier | |
connection_id | STRING | Foreign key to connection.connection_id | |
table_id | BIGINT | Foreign key to source_table.id | |
name | STRING | Column name | |
type | STRING | Column data type | |
is_primary_key | BOOLEAN | Whether column is part of primary key | |
created_at | TIMESTAMP | Creation timestamp | |
updated_at | TIMESTAMP | Last update timestamp |
Primary key: id
Foreign keys:
connection_id→connection.connection_idtable_id→source_table.id
Use cases:
- Source schema documentation
- Primary key identification
- Column-level lineage (with lineage tables)
SOURCE_FOREIGN_KEY table
Foreign key relationships detected in source systems.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
column_id | BIGINT | Primary key. Foreign key to source_column.id | |
ordinal | INTEGER | Ordinal position of a column within a composite foreign key. Columns sharing the same ordinal belong to the same composite foreign key. NULL if the foreign key is not composite. | |
foreign_key_reference | STRING | String representation of the foreign key | |
created_at | TIMESTAMP | Creation timestamp | |
updated_at | TIMESTAMP | Last update timestamp |
Primary key: column_id
Foreign keys: column_id → source_column.id
Use cases:
- Relationship mapping
- Data modeling
- Referential integrity tracking
Destination metadata
Destination metadata tables are available only on Enterprise and Business Critical plans.
DESTINATION_SCHEMA table
Schemas created in destination systems.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | INTEGER | Primary key. Schema identifier | |
destination_id | STRING | Foreign key to destination.id | |
connection_id | STRING | Connection identifier | |
name | STRING | Schema name | |
created_at | TIMESTAMP | Creation timestamp |
Primary key: id
Foreign keys: destination_id → destination.id
Use cases:
- Destination schema inventory
- Schema organization tracking
DESTINATION_TABLE table
Tables created in destination by Fivetran.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | BIGINT | Primary key. Table identifier | |
destination_id | STRING | Foreign key to destination.id | |
schema_id | INTEGER | Foreign key to destination_schema.id | |
connection_id | STRING | Connection identifier | |
name | STRING | Table name | |
created_at | TIMESTAMP | Creation timestamp |
Primary key: id
Foreign keys:
destination_id→destination.idschema_id→destination_schema.id
Use cases:
- Destination table catalog
- Table proliferation tracking
DESTINATION_COLUMN table
Columns in destination tables.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
id | BIGINT | Primary key. Column identifier | |
destination_id | STRING | Foreign key to destination.id | |
table_id | BIGINT | Foreign key to destination_table.id | |
connection_id | STRING | Connection identifier | |
name | STRING | Column name | |
type | STRING | Column data type | |
created_at | TIMESTAMP | Creation timestamp | |
updated_at | TIMESTAMP | Last update timestamp |
Primary key: id
Foreign keys:
destination_id→destination.idtable_id→destination_table.id
Use cases:
- Destination schema documentation
- Column inventory
- Type conversion tracking
Lineage mapping
Lineage tables are available only on Enterprise and Business Critical plans.
SCHEMA_LINEAGE table
Maps source schemas to destination schemas.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
source_schema_id | INTEGER | Primary key (composite). Foreign key to source_schema.id | |
destination_schema_id | INTEGER | Primary key. Foreign key to destination_schema.id | |
created_at | TIMESTAMP | Lineage creation timestamp |
Primary key: source_schema_id, destination_schema_id
Foreign keys:
source_schema_id→source_schema.iddestination_schema_id→destination_schema.id
Use cases:
- Schema-level lineage visualization
- End-to-end data flow mapping
- Impact analysis for schema changes
TABLE_LINEAGE table
Links source tables to destination tables.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
source_table_id | BIGINT | Primary key (composite). Foreign key to source_table.id | |
destination_table_id | BIGINT | Primary key. Foreign key to destination_table.id | |
created_at | TIMESTAMP | Lineage creation timestamp |
Primary key: source_table_id, destination_table_id
Foreign keys:
source_table_id→source_table.iddestination_table_id→destination_table.id
Use cases:
- Table-level lineage tracking
- Data flow documentation
- Downstream dependency mapping
COLUMN_LINEAGE table
Traces individual columns from source to destination.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
source_column_id | BIGINT | Primary key (composite). Foreign key to source_column.id | |
destination_column_id | BIGINT | Primary key. Foreign key to destination_column.id | |
created_at | TIMESTAMP | Lineage creation timestamp |
Primary key: source_column_id, destination_column_id
Foreign keys:
source_column_id→source_column.iddestination_column_id→destination_column.id
Use cases:
- Column-level lineage visualization
- Data governance
- Field-level impact analysis
- Compliance reporting (GDPR, etc.)
Change tracking
Change event tables are available only on Enterprise and Business Critical plans. All change event tables track CREATE, EDIT, and DELETE events.
SOURCE_SCHEMA_CHANGE_EVENT table
History of schema creation and modification events in source systems.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
schema_id | INTEGER | Primary key (composite). Foreign key to source_schema.id | |
detected_at | TIMESTAMP | Primary key (composite). When change was detected | |
connection_id | STRING | Foreign key to connection.connection_id | |
change_type | STRING | Type of change | CREATE, EDIT, DELETE |
Primary key: schema_id, detected_at
Foreign keys:
schema_id→source_schema.idconnection_id→connection.connection_id
Use cases:
- Schema evolution tracking
- Change impact analysis
- Schema drift detection
SOURCE_TABLE_CHANGE_EVENT table
History of table-level changes in source systems.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
table_id | BIGINT | Primary key (composite). Foreign key to source_table.id | |
detected_at | TIMESTAMP | Primary key (composite). When change was detected | |
connection_id | STRING | Foreign key to connection.connection_id | |
change_type | STRING | Type of change | CREATE, EDIT, DELETE |
Primary key: table_id, detected_at
Foreign keys:
table_id→source_table.idconnection_id→connection.connection_id
Use cases:
- Table change tracking
- Source system evolution monitoring
- Schema migration planning
SOURCE_COLUMN_CHANGE_EVENT table
Column-level change history in source systems.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
column_id | BIGINT | Primary key (composite). Foreign key to source_column.id | |
detected_at | TIMESTAMP | Primary key (composite). When change was detected | |
entity_type | STRING | Primary key (composite). Type of entity | |
attribute_name | STRING | Primary key (composite). Name of the changed attribute | |
connection_id | STRING | Foreign key to connection.connection_id | |
change_type | STRING | Type of change | CREATE, EDIT, DELETE |
new_value | STRING | New value after the change |
Primary key: column_id, detected_at, entity_type, attribute_name Foreign keys:
column_id→source_column.idconnection_id→connection.connection_id
Use cases:
- Column evolution tracking
- Breaking change detection
- Data type migration tracking
DESTINATION_SCHEMA_CHANGE_EVENT table
Destination schema change history.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
schema_id | INTEGER | Primary key (composite). Foreign key to destination_schema.id | |
detected_at | TIMESTAMP | Primary key (composite). When change was detected | |
destination_id | STRING | Foreign key to destination.id | |
connection_id | STRING | Foreign key to connection.connection_id | |
change_type | STRING | Type of change | CREATE, EDIT, DELETE |
Primary key: schema_id, detected_at Foreign keys:
schema_id→destination_schema.iddestination_id→destination.idconnection_id→connection.connection_id
Use cases:
- Destination schema evolution
- Change audit trail
- Downstream impact analysis
DESTINATION_TABLE_CHANGE_EVENT table
Destination table change history.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
table_id | BIGINT | Primary key (composite). Foreign key to destination_table.id | |
detected_at | TIMESTAMP | Primary key (composite). When change was detected | |
destination_id | STRING | Foreign key to destination.id | |
connection_id | STRING | Foreign key to connection.connection_id | |
change_type | STRING | Type of change | CREATE, EDIT, DELETE |
Primary key: table_id, detected_at Foreign keys:
table_id→destination_table.iddestination_id→destination.idconnection_id→connection.connection_id
Use cases:
- Table modification tracking
- Destination schema changes
- Table lifecycle monitoring
DESTINATION_COLUMN_CHANGE_EVENT table
Destination column change history.
| Column name | Data type | Description | Enum values |
|---|---|---|---|
column_id | BIGINT | Primary key (composite). Foreign key to destination_column.id | |
detected_at | TIMESTAMP | Primary key (composite). When change was detected | |
attribute_name | STRING | Primary key (composite). Name of the changed attribute | |
destination_id | STRING | Foreign key to destination.id | |
connection_id | STRING | Foreign key to connection.connection_id | |
change_type | STRING | Type of change | CREATE, EDIT, DELETE |
new_value | STRING | New value after the change |
Primary key: column_id, detected_at, attribute_name Foreign keys:
column_id→destination_column.iddestination_id→destination.idconnection_id→connection.connection_id
Use cases:
- Column evolution in destination
- Type change tracking
- Schema compatibility monitoring
Quick reference
Tables by category
| Category | Tables | Availability |
|---|---|---|
| Core account & access | account, user, team, team_membership | All plans |
| RBAC | role, role_permission, role_connector_type, resource_membership | All plans |
| Destinations & connections | destination, connection, connector_type | All plans |
| Logging & monitoring | log, connector_sdk_log, sync_statistics, audit_trail | All plans (audit_trail: Enterprise+) |
| Usage & billing | incremental_mar, transformation_runs, usage_cost, credits_used | All plans |
| Source metadata | source_schema, source_table, source_column, source_foreign_key | Enterprise+ |
| Destination metadata | destination_schema, destination_table, destination_column | Enterprise+ |
| Lineage | schema_lineage, table_lineage, column_lineage | Enterprise+ |
| Change tracking | 6 *_change_event tables | Enterprise+ |