Table 40033 "Migration Setup Table Mapping"

HybridBaseDeployment · Microsoft.DataMigration · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Extensible	false
DataClassification	SystemMetadata

Fields

Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

No.	Name	Type	Explanation
1	Source Sql Table Name	Text[128]	Specifies the name of the source SQL table to be replicated. The name must match exactly the name of the destination table in SQL.
2	Destination Sql Table Name	Text[128]	Specifies the name of the destination SQL table in the cloud environment. The name must match exactly the name of the destination table in SQL.
3	Company Name	Text[30]	Specifies the company name associated with this table mapping. The value should be blank if the table is per-database.
4	Table Name	Text[128]	Specifies the name of the table. For example, “Customer” or “Sales Header”.
5	Preserve Cloud Data	Boolean	Specifies whether to preserve existing data in the cloud during replication. If set to true, existing data in the destination table will not be overwritten during replication, only new records will be added. It is recommended to set this to true for per-database table, while it should be false for p…

Keys

Key1: Source Sql Table Name, Destination Sql Table Name (clustered)
Key2: Destination Sql Table Name

Ask your agent

Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Migration Setup Table Mapping"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.