Author: Eric Vasbinder
ERPs Applicable:
Vista
Change Data Capture (CDC) is a powerful capability, supported by Microsoft SQL, and other databases, to allow for data changes in tables to be tracked and logged, ensuring that insertions, deletions, changes, etc. will be visible and easily consumable by third party tools and applications. This allows for these tools to receive a streamlined data feed of information that they need without the need to set up heavier replication processes or to enable API access through AppXchange to every endpoint.
However, only certain tables in Vista are supported for CDC. Other tables are possible but not supported in the application itself.
Please click on the heading for the "Tables Supported" section below to see a LONG, detailed list of all of the tables supported for CDC.
The most important item we must consider with deploying CDC is whether or not you wish to use CDC in a live, production environment in our cloud, or if you wish to test CDC in a pre-production cloud environment during your cloud transformation.
The method that we use for this is slightly different depending upon if you are wanting CDC in a live, production environment, vs. a non-live pre-production cloud transformation environment that WILL BE live in the future.
such as when testing third party integrations, we will need to perform a series of three manual steps.
Another option is to use your Enterprise Test Environment, available for ESB Silver tier or higher customers. This will allow you to set up CDC prior to go-live with our complete Analytics stack.
As we do not normally implement CDC in a customer's production, cloud environment until after that environment is live in the cloud, there are a number of steps that need to be performed that will be manual if done prior to the cloud transformation being complete. Given this complexity, we do not normally recommend that customers test CDC prior to a cloud go live in their cloud preproduction environment.
However, in the event that enabling CDC in a cloud preproduction environment during testing, prior to the go live itself, is desired, the following manual steps must be performed (NOTE: an Initial Data Upload from on-premise MUST be completed prior to enabling CDC in your cloud pre-production environment):
CUSTOMER: Submit Cloud Transformation support case with specific list of tables for which you require CDC be activated.
TRIMBLE: Activate CDC on viewpoint database
TRIMBLE: Activate CDC on requested tables
TRIMBLE: Activate CDC Capture and Cleanup jobs using internal deployment tools.
TRIMBLE and CUSTOMER: Ensure direct ODBC connectivity to the Vista DB is available using either the IPSEC VPN or a TLS Database Endpoint (TLS VPN/Load Balancer).
TRIMBLE and CUSTOMER: Use the steps in the following article to create a SQL Service account for querying the data with CDC: I need a dedicated SQL account for my integration to Vista in your cloud. How do I set that up?
NOTE: Any future data refreshes into this pre-production environment, such as to update data during the transformation testing stage (Stage 5), will cause steps 2-4 to be redone, and an additional step of reassociating the appropriate SQL service account from the cloud MSDB to the newly refreshed Viewpoint records DB will be needed.
Implementing CDC in a live, production Vista environment is more straight forward and involves an automated set of processes that are executed by default with every new environment that is set up in our cloud.
In this case, our team will automatically set up CDC on the tables against which our data pipeline for TC1 Analytics queries data as part of the environment go live process. This automatically activates the DB for CDC, turns on the SQL CDC Capture job, and turns on the SQL CDC Cleanup job.
As such, the only thing remaining for a customer to do who wants CDC added to additional tables, beyond those used for our own TC1 Analytics process is:
CUSTOMER: Submit a cloud engineering support case with the specific list of tables for which you would like CDC turned on.
Available at the Silver tier or higher of the Enterprise Solutions Bundle (ESB), Enterprise test environments are designed to provide the totality of what production environmments provide. As such, when your Enterprise Test environment is stood up, we should also set up the CDC pipeline for TC1 Analytics. Given that, again, all a customer would then need to do is to put in a cloud engineering support case with a list of the tables on which they wish to have CDC activated.
The following tables and schemas are supported for CDC usage - listed in API Schema format:
{"schema":"api", "table":"vBusinessUnit"},
{"schema":"api", "table":"vGlobalEntityMap"},
{"schema":"dbo", "table":"bAPAA"},
{"schema":"dbo", "table":"bAPCO"},
{"schema":"dbo", "table":"bAPHD"},
{"schema":"dbo", "table":"bAPTD"},
{"schema":"dbo", "table":"bAPTH"},
{"schema":"dbo", "table":"bAPTL"},
{"schema":"dbo", "table":"bAPUI"},
{"schema":"dbo", "table":"bAPVM"},
{"schema":"dbo", "table":"bARCM"},
{"schema":"dbo", "table":"bARRT"},
{"schema":"dbo", "table":"bARTH"},
{"schema":"dbo", "table":"bARTL"},
{"schema":"dbo", "table":"bEMCM"},
{"schema":"dbo", "table":"bEMDM"},
{"schema":"dbo", "table":"bEMEM"},
{"schema":"dbo", "table":"bEMLM"},
{"schema":"dbo", "table":"bHQCO"},
{"schema":"dbo", "table":"bHQMT"},
{"schema":"dbo", "table":"bHQTX"},
{"schema":"dbo", "table":"bHQUM"},
{"schema":"dbo", "table":"bINLM"},
{"schema":"dbo", "table":"bINMT"},
{"schema":"dbo", "table":"bJCCD"},
{"schema":"dbo", "table":"bJCCH"},
{"schema":"dbo", "table":"bJCCI"},
{"schema":"dbo", "table":"bJCCM"},
{"schema":"dbo", "table":"bJCCO"},
{"schema":"dbo", "table":"bJCCP"},
{"schema":"dbo", "table":"bJCCT"},
{"schema":"dbo", "table":"bJCDM"},
{"schema":"dbo", "table":"bJCID"},
{"schema":"dbo", "table":"bJCIP"},
{"schema":"dbo", "table":"bJCJM"},
{"schema":"dbo", "table":"bJCJP"},
{"schema":"dbo", "table":"bJCMP"},
{"schema":"dbo", "table":"bJCOI"},
{"schema":"dbo", "table":"bJCPM"},
{"schema":"dbo", "table":"bJCPP"},
{"schema":"dbo", "table":"bPMCO"},
{"schema":"dbo", "table":"bPMCT"},
{"schema":"dbo", "table":"bPMDH"},
{"schema":"dbo", "table":"bPMDT"},
{"schema":"dbo", "table":"bPMMF"},
{"schema":"dbo", "table":"bPMOA"},
{"schema":"dbo", "table":"bPMOI"},
{"schema":"dbo", "table":"bPMOL"},
{"schema":"dbo", "table":"bPMOM"},
{"schema":"dbo", "table":"bPMOP"},
{"schema":"dbo", "table":"bPMPA"},
{"schema":"dbo", "table":"bPMPC"},
{"schema":"dbo", "table":"bPMSC"},
{"schema":"dbo", "table":"bPMSL"},
{"schema":"dbo", "table":"bPOCD"},
{"schema":"dbo", "table":"bPOHB"},
{"schema":"dbo", "table":"bPOHD"},
{"schema":"dbo", "table":"bPOIB"},
{"schema":"dbo", "table":"bPOIT"},
{"schema":"dbo", "table":"bPORD"},
{"schema":"dbo", "table":"bPREH"},
{"schema":"dbo", "table":"bSLCD"},
{"schema":"dbo", "table":"bSLHD"},
{"schema":"dbo", "table":"bSLIT"},
{"schema":"dbo", "table":"debezium_signal"},
{"schema":"dbo", "table":"vDDDS"},
{"schema":"dbo", "table":"vDDDTc"},
{"schema":"dbo", "table":"vDDSG"},
{"schema":"dbo", "table":"vDDSL"},
{"schema":"dbo", "table":"vDDSLc"},
{"schema":"dbo", "table":"vDDSU"},
{"schema":"dbo", "table":"vDDUP"},
{"schema":"dbo", "table":"vEMLocationHistory"},
{"schema":"dbo", "table":"vEMLocationHistoryAttach"},
{"schema":"dbo", "table":"vPMPOCO"},
{"schema":"dbo", "table":"vPMSubcontractCO"}
changelog
Tuesday, 23 June 2026 at 01:33PM:
Based on latest conversations with engineering, we CAN turn on CDC prior to go-live in pre-production environments. However, it is complex, with three manual steps.
Tuesday, 23 June 2026 at 11:33AM:
Added details as to why CDC cannot be turned on until after go-live.
Tuesday, 23 June 2026 at 11:30AM:
Called out that CDC can only be enabled in a production environment AFTER the customer is live in the cloud. Test environments are different.
Friday, 07 February 2025 at 11:06AM:
Initial posting