Hi community!Lets take the following setup for a replication scenario:I have a SQL Server Express installation in the field [FDS] on a production system. The database collects trend data (environment data like temperature, humidity, ...) and supplies the UI client with "master data" information which is needed for the production (setup parameters for the production machine, recipes). The FDS has no high load. The complete DB has maybe 50 MB (including the trend data, index, ...)The "master data" resides on a central SQL Server [CDS] (Standard upwards). The CDS replicates the master data. If the client changes the "master data" information and the CDS is online, the "master data" is stored on the CDS and should get replicated immediately to the FDS. If the network connection between CDS and FDS is lost and master data must be changed, the change should happen on the FDS to continue with the production. As soon as the connection gets back online, the data is replicated again to the FDS and the earlier change to the master data is overwritten."Transactional replication, however, is sensitive to external changes to the target database. Any such change can potentially break replication so, for all intents and purposes, the target database should be considered read-only. There are exceptions to this rule, however. For example, you can modify objects in the target database that are not part of the replication setup." "Fundamentals of SQL Server 2012 replication" [Sebastian Meine, from Red Gate, page 32]After reading the book, I would say that I should set up the scenario as transactional replication in the push mode. However, i am irretated by the above statement which would break the replication. As the transactional replication is reading from the log writer, do I have to setup the CDS with the "Full" backup option? How would you set up such a scenario?Thank you for your input.
↧