Edit

Stretch Database Catalog Views - sys.remote_data_archive_tables

  • Article

Applies to: SQL Server 2016 (13.x) and later versions

Contains one row for each remote table that stores data from a Stretch-enabled local table.

Important

Stretch Database is deprecated in SQL Server 2022 (16.x) and Azure SQL Database. This feature will be removed in a future version of the Database Engine. Avoid using this feature in new development work, and plan to modify applications that currently use this feature.

Column name Data type Description
object_id int The object ID of the Stretch-enabled local table.
remote_database_id int The auto-generated local identifier of the remote database.
remote_table_name sysname The name of the table in the remote database that corresponds to the Stretch-enabled local table.
filter_predicate nvarchar(max) The filter predicate, if any, that identifies rows in the table to be migrated. If the value is null, the entire table is eligible to be migrated.

For more info, see Enable Stretch Database for a table and Select rows to migrate by using a filter predicate.
migration_direction tinyint The direction in which data is currently being migrated. The available values are the following.
1 (outbound)
2 (inbound)
migration_direction_desc nvarchar(60) The description of the direction in which data is currently being migrated. The available values are the following.
outbound (1)
inbound (2)
is_migration_paused bit Indicates whether migration is currently paused.
is_reconciled bit Indicates whether the remote table and the SQL Server table are in sync.

When the value of is_reconciled is 1 (true), the remote table and the SQL Server table are in sync, and you can run queries that include the remote data.

When the value of is_reconciled is 0 (false), the remote table and the SQL Server table are not in sync. Recently migrated rows have to be migrated again. This occurs when you restore the remote Azure database, or when you delete rows manually from the remote table. Until you reconcile the tables, you can't run queries that include the remote data. To reconcile the tables, run sys.sp_rda_reconcile_batch.

See also