Shulou(Shulou.com)06/01 Report--

About sql server2012 database replication synchronization Times error: "

The job failed. Schedule 1127 (replication Agent Plan.) The job was invoked. The last thing to run is step 1 (run the agent.) . .

Executed as user NT SERVICE\ SQLSERVERAGENT. The directory'F:\ Program Files\ Microsoft SQL Server\ MSSQL11.MSSQLSERVER\ MSSQL\ ReplData\ unc\ 20120723102721\ 'cannot be deleted. Check the security context of xp_cmdshell and close other processes that may be accessing the directory. [SQLSTATE 42000] (error 20015) copy-@ rowcount_only parameter value must be 0, 1, or 2. A checksum that is compatible with 0. 0. 0. 1 = check only the row count. 2 = the new checksum feature introduced in version 8.0. The scheduled proxy distribution@rowcount_only parameter value must be 0, 1, or 2. A checksum that is compatible with 0. 0. 0. 1 = check only the row count. 2 = the new checksum feature introduced in version 8.0. Try again. Unable to clear the distribution transaction table. [SQLSTATE 01000] (message 14152). The step failed. "

The reason for this problem is that the data update rate of the tables in the source database far exceeds the subscription requirements from the database.

The replication mechanism with the above errors usually uses "pull subscription". The DBA who knows the pull subscription must know that it takes a while for the subscriber to ask the publisher to replicate the data that has changed in the publication database. Therefore, when the subscriber requests the changed data from the publisher after a period of time, the publisher will calculate and compare the changes of the master-slave database data. If the publisher finds that the main library can't find the last change in the data from the database, it will report that "SQL SERVER2012 synchronization Times made an error while executing a batch of commands incorrectly. Retrying a single command." Mistake.

Solution: remove the previous pull subscription mechanism and solve the problem of creating push subscription (pay attention to the case of CREATE/DROP in stored procedures).

There are other ways to solve this problem, such as handwritten scripts to establish synchronization mechanisms. The masters are not hesitant to continue.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.