You specify the tables to capture by sending an execute-snapshot message to the signaling table. Running an incremental snapshot captures the following data changes: The connector runs the snapshot while it continues to stream real-time changes from the tables. (Optional) If the connector performed a schema_only snapshot, after the snapshot completes, initiate an incremental snapshot to capture data from the tables that you added. The connector completes the type of snapshot specified by the snapshot.mode. Use this option if you want to restart the connector more quickly than with a full snapshot. Unlike a full data snapshot, this option does not capture any table data. When you restart the connector, it takes a snapshot that captures only the table schema. If you select this option, consider setting the value of the .tables.ddl property to false to enable the connector to capture the schema of all tables. When you restart the connector, it takes a full snapshot of the database that captures the table data and table structures. The schema history provides information about the structure that is in effect when a change event occurs. The connector persists this information in its internal database schema history topic. Read the maximum log sequence number (LSN) position in the server’s transaction log.Ĭapture the structure of all non-system, or all tables that are designated for capture. The level of the lock is determined by the configuration property. Obtain a lock on the SQL Server tables for which CDC is enabled to prevent structural changes from occurring during creation of the snapshot. To have the connector capture a subset of tables or table elements, you can set a number of include and exclude properties to filter the data, for example, or.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |