Edit

sys.dm_db_xtp_merge_requests (Transact-SQL)

  • Article

Applies to: SQL Server 2014 (12.x)

Tracks database merge requests. The merge request may have been generated by SQL Server or the request could have been made by a user with sys.sp_xtp_merge_checkpoint_files (Transact-SQL).

Note

This dynamic management view (DMV), sys.dm_db_xtp_merge_requests, exists until Microsoft SQL Server 2014. But starting with SQL Server 2016 this DMV no longer applies.

Columns in the report

Column name Data type Description
request_state tinyint Status of the merge request:
0 = requested
1 = pending
2 = installed
3 = abandoned
request_state_desc nvarchar(60) Meanings for the current state of the request:

Requested - a merge request exists.
Pending - the merge is being processing.
Installed - the merge is complete.
Abandoned - the merge could not complete, perhaps due to lack of storage.
destination_file_id GUID The unique identifier of the destination file for the merge of the Source files.
lower_bound_tsn bigint The minimum timestamp for the target merge file. The lowest transaction timestamp of all the source files to be merged.
upper_bound_tsn bigint The maximum timestamp for the target merge file. The highest transaction timestamp of all the source files to be merged.
collection_tsn bigint The timestamp at which the current row can be collected.

A row in the Installed state is removed when checkpoint_tsn is greater than collection_tsn.

A row in the Abandoned state is removed when checkpoint_tsn is less than collection_tsn.
checkpoint_tsn bigint The time that the checkpoint started.

Any deletes done by transactions with a timestamp lower than this are accounted for in the new data file. The remaining deletes are moved to the target delta file.
sourcenumber_file_id GUID Up to 16 internal file IDs that uniquely identify the source files in the merge.

Permissions

Requires VIEW DATABASE STATE permission on the current database.

Permissions for SQL Server 2022 and later

Requires VIEW DATABASE PERFORMANCE STATE permission on the database.

See also

Next steps