영어에서 Merge replication 을 사용하는 예와 한국어로 번역
{-}
-
Colloquial
-
Ecclesiastic
-
Ecclesiastic
-
Programming
-
Computer
Log Shipping with Merge Replication.
If an application requires sophisticated conflict detection and resolution capabilities, use merge replication.
Merge replication does not support sparse columns or column sets.
Strategies for Backing Up and Restoring Merge Replication.
Merge replication automatically adds a column if the table does not have one.
For more information, see Web Synchronization for Merge Replication.
Merge replication and snapshot replication do not affect transaction log size, but transactional replication can.
Join filters, which are available only with merge replication.
For more information,see Merge Replication and Detect and Resolve Merge Replication Conflicts.
Learn how to use merge replication to exchange data between a server and one or more clients that are only occasionally connected.
Therefore, conflicts can occur when updates are merged and merge replication provides a number of ways to handle conflicts.
Validation is not required by replication, but it is recommended to run validation periodically for transactional replication and merge replication.
Merge replication can synchronize FILESTREAM data over an HTTPS connection by using Web Synchronization.
For more information about Web synchronization, see Web Synchronization for Merge Replication.
By default, merge replication will publish this schema change, and it will be applied to each subscription database.
Transactional replication tracks changes through the SQL Server transaction log, and merge replication tracks changes through triggers and metadata tables.
Both merge replication and FILESTREAM require a column of data type uniqueidentifier to identify each row in a table.
To do this, you must set a schema option or the publication compatibility level(for merge replication) so the column can be converted to a compatible data type.
Merge replication is primarily designed for mobile applications or distributed server applications that have possible data conflicts.
If you add a FILESTREAM column to a table that is already published for merge replication, make sure that the uniqueidentifier column has a UNIQUE constraint.
Learn how to use merge replication to exchange data between a server and one or more clients that are only occasionally connected.
If you add a FILESTREAM column to a table that is already published for merge replication, we recommend that you set the option to true by using sp_changemergearticle.
Merge replication and transactional replication with updating subscriptions use uniqueidentifier columns to guarantee that rows are uniquely identified across multiple copies of the table.".
Snapshot replication, as well as the initial distribution of data for transactional and merge replication, can store data in unencrypted intermediate files; for example, the bcp files.
The web synchronization option for merge replication provides the ability to replicate data using the HTTPS protocol, which can be a convenient approach to replicating data through a firewall.
All types of Microsoft SQL Server replication can replicate data over a VPN, but consider using Web synchronization if you are using merge replication, because Web synchronization eliminates the need for a VPN.
Originally released in SQL Server 7.0, merge replication is primarily designed for mobile application or distributed server applications that have possible data conflicts.
It is not permitted because replication cannot trackthe changes caused by the operation: transactional replication tracks changes through the transaction log; merge replication tracks changes through triggers on published tables.
All types of MicrosoftSQL Server replication can replicate data over a VPN, but consider using Web synchronization if you are using merge replication, because Web synchronization eliminates the need for a VPN.