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

Initialize common errors using backup restore when creating transactional replication

Question 1:

Error: 14151, severity: 18, status: 1.

Replication- replication distribution subsystem: agent test-DB-TDB1-tdb1-test-DB\ MSSQLSERV-299 failed. The process cannot access the database "TDB1" on the server "test-DB\ MSSQLSERVERA".

Solution: the reason for this error is that when using a pull subscription or remote distributor, copying the account test\ SqlReplicator (domain account) does not have access to the subscription database TDB1. It is necessary to give sysadmin,ower permission to ensure that the replication distribution account has the appropriate permissions before the log proxy server can start normally.

Question 2:

A network-related or instance-specific error occurred while establishing a connection. The server cannot be found or cannot be accessed. Check that the instance name is correct and that SQL Server is configured to allow remote connections. For more information, see SQL Server Books online. (source: MSSQLServer, error number: 10061)

Solution: 1) in the list box under "aspect", select "server configuration,"RemoteAccessEnabled" property and "RemotoDacEnabled" to "True", and click "OK".

2) in the list box under "aspect", select "SQLServer Peripheral Application Configurator", "AdHocRemoteQuriesEnabled" to "True", "CltIntegrationEnabled" to "True", "DatabaseMailEnabled" to "True", "RemoteDacEnabled" to "True", and click "OK"

Question 3:

Initialization with backup restore, transaction replication. The self-increment table reports an error as follows: when IDENTITY_INSERT is set to ON or when a replication user inserts content into the NOT FOR REPLICATION identity column, an explicit value must be specified for the identity column in the table 'test_store'.

Analysis: because the table test_store has self-increasing columns, the replication is an error. By default (sql server 2008R), the self-increasing columns of the self-increasing table will not be synchronized, but it is found that in the production environment, another table testchaine table has a trigger (insert,update,delete) to call the test_ store. at this time, even if the test_store table is not synchronized during the initialization replication process, an error will be reported: test_store invalid object. How to solve the problem?

Solution: you can only delete the add, delete and modify triggers in the testchain table, and the log agent is normal after deletion

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.