en:datadistribdescription
Differences
This shows you the differences between two versions of the page.
— | en:datadistribdescription [2021/03/25 13:05] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | TitleEngTAG | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | SprinklerTAG eeLiteTAG detects any changes made to the database, like the standard logging procedures; the code is designed to minimize the impact in terms of performance while Dynamics 365 Business Central is up and running. | ||
+ | |||
+ | When a change is made and it is expected to be distributed, | ||
+ | |||
+ | {{TechnicalSchema.png}} | ||
+ | |||
+ | A specific scheduled Job Queue Entry existing on SOURCE, identified as CORE, is charged to move the record into the staging table [eeRis Spk Remote Outbox]; from here, a second Job Queue Entry, identified as HANDLER, transfers the record via a SOAP call to the Web Service exposed by TARGET. Thi call will write the data into [eeRis Spk Remote Inbox] table. A third Job Queue Entry process will copy the record into [eeRis Spk Inbox Entry], and finally replicate the operation received into the destination table. | ||
+ | |||
+ | Every transmitted transaction is stored as a single record into the previously indicated tables, and the data carries only the fields modified (if configured). The only exception to this rule is in case of RENAME modifications, | ||
+ | |||