Step by step teach you how to configure SQL server merge and copy (4) improve the security of distributor

To enable devices that have subscribed to databases to better contact each other Distributor,You must add a domain user to the database so that the device can access the publishing database with the user's permissions.

OpenSQL ServerResource Manager, expandSecurityThis option, right-clickLoginFolder, selectNew Login...
 

InLogin-NewOn this page, selectWindows AuthenticationSelect one button, and then clickSearch.

In the pop-upSelect user or groupOn this page, clickLocations, ExpandEntire directoryNode, selectSyncdomain. InternalThen clickOKInEnter the object name to selectEnterSyncuserAnd then clickCHECK NAMESAnd then clickOK.Syncdomain. InternalInSyncuserThe user is added to the new user list.

InLogin-NewSelectUser MappingIn the check box on the right, selectPublicationDatabaseDistributionAnd then clickOK.

How do I cancel a distributor or publisher?

In some cases, you may want to removeDistribution DatabaseOr a database for publishing and replication, manual deletion is certainly a method, but here is a more thorough method, and it is very simple. OpenSQL ServerResource Manager, right-clickReplicationThen selectDisable publishing and distributionAs shown in.

The first page displayed is a Wizard Page. ClickNext.

InDisable PublishingOn this page, you need to selectYes, disable publishing on this serverClick the single-choice button to delete the published database, delete all copies of the database, and delete all subscriptions.

InConfirm disabling remote publishersThis interface will be a warning page, warning you to delete the copy and subscription of the following servers.

The next page is a confirmation page and select whether to generate a script file to facilitate future repetitive work.

If you choose to generate a script file, you will see the following interface, which is used to let you choose the location where the script file is stored and the file format.

Now, our work is almost finished. Here is a complete confirmation message to ensure that this information is consistent with the information you entered.

When you see the following interface:SuccessIt indicates that your work has been completed.

Name pies

When you do a good job of merging and copying the security, you are about to start and run the SQL Server distributor, but you are still in the last step, even in the TCP/IP environment, SQL Server still needs to start named pipes to complete merge and copy tasks. Start SQL Server Configuration Manager, expand SQL Server 2005 network configuration, click protocols for MSSQLServer, right-click named pipes in the list on the right, and select Enabled, as shown in.

Keep running:

After your distributor is set up, you must keep it running at high speed. Whether it is the first synchronization or 50th synchronization, here is a simple and practical trick, that is, the indexes in the rebuilding distribution database, because these indexes are frequently used, some of their fragments will slow down the server synchronization speed. You will find the following table in the databases | System databases | distribution | tables | system tables directory of SQL Server:
• Msmerge_agents
• Msmerge_articlehistory
• Msmerge_indentity_range_allocations(If you include automatically increasing columns in the table of the database for publishing and replication, this table will be available)
• Msmerge_sessions
• Msmerge_subscriptions
• Msrepl_errors
• Msreplication_monitordata
• Mssnapshot_history
You can manually rebuild the indexes of these tables, open these tables, right-click indexes, select rebuild all, and click OK at the end of the page. I suggest you perform this task once a week. Of course, you can also create a new job in SQL Server to complete this task.

Note by the author (note that it is not the Translator's note ):

In my experience, releasing distributor and publisher on different servers is a good way to improve performance, if the CPU, memory, and hard disk only serve publisher, publisher can better process the combined replication between the database and the device.

Because sqlserver will create a large number of files on the disk, in order to achieve better file transmission speed, you must allocate the disk space of the server reasonably, and it is best to store them separately, for example, the system is mounted on disk C, SQL Server is mounted on disk D, distributor database files are stored on disk E, distributor log files are stored on disk F, and snapshot folders are stored on disk G.

When your system grows larger, I suggest that the memory of SQL Server and Windows 2003 servers should be at least 16 GB, and it can support at least 64-bit systems.

For the sake of security of your synchronization system, when you configure it according to the Configuration Wizard, you do not need to use the SQL Server account SA to add access SQL Server and IIS to your domain, this greatly improves the security of the synchronization system.