SQL Server database synchronization question sharing [unfinished, To be continued] (1)
SQL Server database synchronization problem sharing (2) --- operation steps [unfinished, To be continued]
(1)ModifyFTPConnection
During data synchronization, the publisher needs to generate a data snapshot and save it in a local folder. Of course there is no problem with this, but the subscription server needs to be able to read the Snapshot package in this folder.
In the same CIDR block, we can use shared folders to read these files. If it is a synchronization between the public network and the Intranet, It is a synchronization between the public network and not a CIDR block. here we can useFTPTo connect
Right-click a local release and choose properties:
Select allow subscription ServerFTPDownload the snapshot file. Used hereFTPThis can effectively solve the problem of reading snapshot files from different network segments.
AboveFTPYou can set relevant information according to your own needs, and pay attention to it hereFTPThe path starting from the root folder must point to the location where the snapshot is generated."/FTP /".After the application is confirmed, it will promote whether to re-generate the snapshot file. Here, it is enough to re-generate the snapshot file, and then use it on the client.FTPCheck whether the client can be downloaded once. Of course, the client is not used for synchronization.
FTPA large number of servers are created on the Publishing Server.FTPThere are many sites,Windows2003There are built-inFTPService, you can also useServer_uIn short, you can download the snapshot file.
(2)View releaseProgramRunning status
If the data is large, the snapshot generated here may be slow. Click monitoring to view the specific running status.
You can see the running status here. If any published file appears, a warning is displayed.
(3) create a subscription
Select the Publishing Server, that is, the new publishing machine.
(4) Select subscription content
(5)Distribution Proxy Server Selection
You can also select multiple subscription servers. The above explains a structure of publishing and subscription. The subscription server is like a newspaper reader. A publishing newspaper can have multiple readers.
(6)Security Settings of distribution agent
SelectWindowsRun under the Account. Enter the user name and password of the Publishing Server.
Connect to the distributorSQL ServerLogin Name: Enter the Publishing Server, that is, the machine set above.After the settings are complete, the next step is complete.
(7) single user problems
Many people should have encountered this problem. Solution:
Use Master
Go
Declare @ SQL Varchar ( Max )
Set @ SQL = ''
Select @ SQL = @ SQL + ' ; Kill ' + Rtrim (Spid)
From Master .. sysprocesses
Where Dbid = Db_id ( ' Dbname ' )
Exec ( @ SQL )
Go
Alter DatabaseDbnameSetMulti_user
(8)The specified database cannot be opened.
The database log shows that the service opens a clear database. Check whether the data access permission is sufficient.
Of course, there is another situation.
If this problem occurs, try to disable this service! It cannot be ensured that this problem is caused, but this service can also cause this problem.
(9)The process cannot be rushedFTPDownload Site files
This problem has been encountered too many. There are many such problems. The download file is too large to be interrupted. However, when I perform this synchronization, because multiple machines are involved, some machines run normally, and some machines have this problem. It takes a long time for hichina to disable ports.
(10) distributed transactions
Transaction replication is used above, and transaction relationships are established between multiple machines. This should be a distributed transaction. Windows Related services must be enabled on!
This service must be enabled.
And MSDTC You must also enable relevant settings. Enter Dcomcnfg Command, my computer À MSDTC À Security Configuration
The above isWindows2003Configuration diagram above
This is Win7 System Configuration