en:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
en:start [2017/01/27 13:25] eeris |
en:start [2018/11/05 11:36] (current) |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| <HTML><H3>What is Sprinkler?</H3></HTML> | <HTML><H3>What is Sprinkler?</H3></HTML> | ||
| - | Sprinkler is a Data Distribution System, developed to simplify any information replication needed between two or more Microsoft Dynamics NAV databases, and available for every version from NAV 2013 R2 to NAV 2016. | + | Sprinkler is a Data Distribution System, developed to simplify any information replication needed between two or more Microsoft Dynamics NAV databases, and available for Dynamics NAV, versions NAV 2016, NAV 2017, NAV 2018, Dynamics 365 Business Central (on-premise). |
| - | Sprinkler is available in two versions, the base SprinklerTAG LiteTAG (free) and the full SprinklerTAG eeLiteTAG offering all advanced option. ([[ProductMatrix|Product Versions]]) | + | [[WhatsNew|What's New in v.1.1.00]] |
| - | In his most simple configuration, Sprinkler detects any data modification operated on first database (called Master) and transfers this information to the second database (called Slave), in order to replicate the same operation. | + | Sprinkler is available in two versions, the base SprinklerTAG LiteTAG, permitting an on-demand replication, and the full SprinklerTAG eeLiteTAG offering all advanced option and nearly real-time replication. ([[ProductMatrix|Product Versions]]) |
| - | A flexible setup on master database allows to define precisely which operations are to be detected, and a similar setup on slave database allows to define which reported operations has to be imported and replicated. ([[DataDistributionSetup|Basic Configuration]]) | + | In his most simple configuration, SprinklerTAG eeLiteTAG detects any data modification operated on a company belonging on a first database (called Source Company or Source Peer) and transfers this information to one or even more company on the same or different databases (called Target Companies or Target Peers), in order to replicate the same operation. |
| - | A single database can be at the same time master and slave, allowing a bi-directional distribution configuration; moreover, in the eeLiteTAG version is allowed also the communication between more than two databases at the same time, creating a very flexible distribution system. | + | {{DistributionSchema-01.png}} |
| - | In SprinklerTAG LiteTAG the Data Distribution is implemented using Stored Procedures between linked servers, while in SprinklerTAG eeLiteTAG we offer a proprietary distribution layer that allows you to have a distributed architecture, possibly using a relay server resident on Microsoft Azure. | + | A flexible setup on Source company allows to define precisely which operations are to be detected, and a similar setup on each Target company allows to define which reported operations has to be imported and replicated, or discarded. ([[DataDistributionSetup|Basic Configuration]]) |
| + | A single company can be at the same time Source and Target, allowing a bi-directional and very flexible distribution schema. | ||
| - | [[WhatsNew_0_5_00|What's New in v.0.5.00]] | + | {{DistributionSchema-02.png}} |
| + | |||
| + | The Data distribution is implemented by a SSIS Package, that allows you to have a distributed architecture. In future versions a relay service resident on Microsoft Azure will be provided. (Note: the relay service is not yet available for the current 1.1.00 version) | ||
| + | |||
| + | {{DistributionSchema-03.png}} | ||
| (r) eeRisTAG | (r) eeRisTAG | ||
en/start.1485519940.txt.gz · Last modified: 2017/01/27 13:25 by eeris
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
