Data synchronization between SQL server servers 1

Before setting and using database replication in SQL Server 2000, check whether the following SQL Server servers meet the requirements:

1. Does the MSSQLserver and Sqlserveragent services start and run as domain users (. \ administrator users can also)

If you use the local account to log on, the network function is unavailable and the following error occurs:

The process failed to connect to the Distributor '@ Server name'

(If your Server has used the full-text retrieval service of SQL Server, do not modify the local startup of MSSQLserver and Sqlserveragent services.
The full-text search service is unavailable. Use another machine as the distribution Server for SQL Server 2000 replication .)

To modify the login user who starts the service, you must restart the MSSQLserver and Sqlserveragent services to take effect.

2. Check whether the names of the related SQL Server servers have been changed. (The srvname and datasource must be the same on the local machine with srvid = 0)

Run the following command in the query Analyzer:
Use master
Select srvid, srvname, datasource from sysservers

If there is no srvid = 0 or srvid = 0 (that is, the current machine) but the srvname is different from the datasource, You need to modify it as follows:

USE master
GO
-- Set two variables
DECLARE @ servERProperty_servername varchar (100 ),
@ Servername varchar (100)
-- Obtain information about the Windows NT Server and the instance associated with the specified SQL Server instance
SELECT @ serverproperty_servername = CONVERT (varchar (100), SERVERPROPERTY ('servername '))
-- Returns the name of the local Server running Microsoft SQL Server.
SELECT @ servername = CONVERT (varchar (100), @ SERVERNAME)
-- Display the obtained Parameters
Select @ serverproperty_servername, @ servername
-- If @ serverproperty_servername is different from @ servername (because you changed the computer name), run the following
-- Delete the wrong server name
EXEC sp_dropserver @ server = @ servername
-- Add the correct server name
EXEC sp_addserver @ server = @ serverproperty_servername, @ local = 'local'

To modify this parameter, you must restart the MSSQLserver and Sqlserveragent services to take effect.

In this way, errors 18482 and 18483 will not occur during replication creation.

3. Check whether the registration names of the SQL Server related to the SQL Server Enterprise Manager are the same as those described in the second section above.

You cannot use the registration name of an IP address.

(We can delete the registration of IP addresses and create a new Server name registered as an SQL Server administrator)

In this way, errors 14010, 20084, 18456, 18482, and 18483 will not occur during replication creation.

4. Check whether the network of Several SQL Server servers can be accessed normally.

If you can ping the Host IP address but cannot ping the host name, you must

Winnt \ system32 \ drivers \ etc \ hosts (WIN2000)
Windows \ system32 \ drivers \ etc \ hosts (WIN2003)

The correspondence between the IP address of the database server and the host name.

For example:

127.0.0.1 localhost
192.168.0.35 Oracledb oracledb
192.168.0.65 fengyu02 fengyu02
202.84.10.193 bj_db

Or create an alias in the network utility of the SQL Server Client, for example:

5. Whether the extended storage process required by the system exists (if it does not exist, it needs to be restored ):

Sp_addextendedproc 'xp _ regenumvalues ', @ dllname = 'xpstar. dll'
Go
Sp_addextendedproc 'xp _ regdeletevalue ', @ dllname = 'xpstar. dll'
Go
Sp_addextendedproc 'xp _ regdeletekey ', @ dllname = 'xpstar. dll'
Go
Sp_addextendedproc xp_cmdshell, @ dllname = 'loglog70. dll'

Next, you can use the SQL Server Enterprise Manager to [copy]-> right-click to select
-> The [configure Publishing, subscription server, and Distribution] graphic interface is used to configure database replication.

The steps for configuring replication are as follows:

1. Create a publishing and distribution server

[Welcome to the configuration release and distribution wizard]-> [select a distribution server]

-> [Make "@ servername" its own distribution Server, and SQL Server will create distribution databases and logs]

-> [Create a snapshot folder]-> [custom configuration]-> [No, use the following default configuration]-> [complete]

After the preceding steps are completed, a distribion library and

A distributor_admin administrator-level user (we can change the password as needed)

Four new jobs are added to the server:
[Clear Agent history: distribution]
[Clear distribution: distribution]
[Copy proxy check]
[Re-initialize a subscription with failed data verification]

The SQL Server Enterprise Manager has a replication Monitor, which allows you to publish, distribute, and subscribe to the current machine.