لطفا منتظر باشید ...
Understanding When Replication Isn't Appropriate
Despite the many positive aspects of replication, it is not appropriate in a few situations, such as when data consistency is critical. If an application requires that data be current at every given moment, it isn't a good candidate for replication. Replication is also not effective when many different users modify a large number of existing records throughout the day. In a situation like this, resolving conflicts that happen when multiple users update the same record wouldn't be practical. Furthermore, you cannot use replication if you are using Visual SourceSafe to manage the development process. Finally, you cannot rename or move design masters, and a design master that becomes corrupted can be difficult to recover.
