Starting from the whole network: original SQL Database Synchronization Tool

Data Synchronization is an issue that distributed systems often need to consider. That is, distributed data is collected and summarized for statistics. For example, Nike has stores all over the world. If the primary store needs to know the sales information of the branch, it needs to synchronize the sales data of the Branch to the primary store. Currently, there are two mainstream databases: SQLServer and Oracle. Pair

Data Synchronization is an issue that distributed systems often need to consider. That is, distributed data is collected and summarized for statistics. For example, Nike has stores all over the world. If the primary store needs to know the sales information of the branch, it needs to synchronize the sales data of the Branch to the primary store. Currently, there are two mainstream databases: SQL Server and Oracle. Pair

Programming Design Requirements

Data Synchronization is a problem that distributed systems often need to consider. That is, scattered data is collected together for summary and statistics. For example, Nike has stores all over the world. If the primary store needs to know the sales information of the branch, it needs to synchronize the sales data of the Branch to the primary store.

Currently, there are two mainstream databases: SQL Server and Oracle. Oracle databases have mature synchronization technologies, but SQL databases do not have good solutions. Although some companies have developed synchronization programs, they are too expensive.

At the same time, Database Synchronization Technology is a common technology, so it is necessary to develop an independent Database Synchronization System to avoid repeated efforts.

In summary, the development of "SQL Server Database Synchronization System" is proposed.

Running Environment

The program is developed using. NET 4.0. Therefore, it can only run in the Windows operating system and must be supported by. NET Framwork 4.0.

The SQLite local database system and Hong Kong server are used in the program, but they are supported by itself, without installing other components.

The program is developed for SQL Server databases. Therefore, it only supports SQL Server databases. Currently, it is known to support SQL Server 2003, SQL Server 2005, and SQL Server 2008.

Technical insider

More than 100 replies are posted. Haha ~~~

Application instructions system deployment

Client usage Overview

The system is divided into two parts: the client and the server. The client undertakes a large number of transactions in the system. The server simply executes the commands sent by the client and is a typical thin server mode of the C/S fat client. This design aims to reduce the pressure on the server and make the system smoother.

The client collects data from the distributed database and then summarizes the data to the server. The database connection string to be configured on the client is the connection string of the distributed database. data can be synchronized to the master database only after the connection is successful. For example, if there are three distributed databases A, B, and C, and data needs to be summarized to database D, three clients are required to connect to database A, database B, and database C respectively, it doesn't matter where the client runs, as long as it can connect to the database.

Home Page Description

The home page displays some public information.

The program start date helps you analyze the log synchronization status;

The scanning engine and synchronization engine are the two core engines of the system. The scanning engine is responsible for obtaining data changes in the distributed database, and the synchronization engine is responsible for sending the data to be synchronized to the server. If the database connection string is not set, the engine is not enabled. Otherwise, the engine is automatically enabled without manual intervention.

The space occupied by the database refers to the space occupied by the local SQLite database of the program. Because a large amount of log information is used for a long time, the occupied space will reduce the program efficiency and facilitate timely cleaning. The cleanup interface is as follows:

Select the log type to be cleared, and select a date. After submission, all logs before the date are cleared.

Activity Log description

This page allows you to query the activity status of a program and display the records of a specific date in a date query.

The program activity log is a scan record that records the scan information in detail.