User Tools

Site Tools


This translation is older than the original page and might be outdated. See what has changed.

Introduction to Sprinkler




eeRis Sprinkler v.1.2.00
for Microsoft Dynamics NAV 2016 / NAV 2017 / NAV 2018 / Dynamics 365 Business Central on-prem

Sprinkler eeLite technical description

Sprinkler eeLite 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 NAV is up and running.

When a change is made and it is expected to be distributed, this information is inserted in the table [Data Distrib. Outbox Entry]:

The single change is logged by a single record, containing all fields modified and requested by the specific setup of the affected table. The only exception to this rule is the case of RENAME: please find more details in RENAME Important Topic

When the distribution is made via Stored Procedures + SSIS, the changes in the NAV table [Data Distrib. Outbox Entry] are taken from the Stored Procedures existing on the [SprinklerDB] utility database and moved to staging tables of this database: similar procedures on the target [SprinklerDB] database deal to retrieve data (in PULL mode), copy them to the local staging tables and lastly insert them into the table [Data Distrib Inbox. Entry] of the target NAV company.

As a result, the data that originate from the master system are inserted in both cases in the target NAV table [Data Distrib. Inbox Entry]. The transactions are then replicated to the current database by the codeunit [Spk Management], executed by the Sprinkler service working on target NAV database.

en/datadistribdescription.txt · Last modified: 2018/05/14 15:11 (external edit)