28. Credit
Combined copy
Use the merger
Set a merged copy system
Management
Monitoring and commanding of consolidated compound
Summary of this chapter
The merged replications and trading have different places where consolidated replications multi-work. Using merged complications allows issuers and subscribers to update the issuance set. Although trading replication also allows subscribers to update the issuer, the functionality of these two replusive types is very different. In this chapter, it will learn the mode of operation of the merged replication, and how to set up, monitor and calibrate merger.
Combined DCCMCCC performs two-way replication between the issuer and one or more subscribers. This allows several systems to have a copy of the updated distribution set and can modify its own distribution set. The modification of the subscriber will be represented to the issuer and then go to other subscribers. Unlike trading replications, the execution of merchant-based replications is to install trigger programs in the issuer and subscriber. When a copy of the issuance or distribution set is changed, the appropriate trigger program is touched, generate a copy command, and listen to the distribution database. This copy command will finally be sent to the distributed database and then transfer to the system participating in the Repro. Based on such an implementation method, the merchant replication is larger than the burden of the transaction type, especially in the issuer. In this chapter, you will learn two important members in the merged replication, one is a merge agent, one is a distributed database. The merged agent will be combined with the incremental data change that occurred from the previous merge. When you use a merged documered (do not use the distributed agent), the merged agent will communicate with the issuer and the distributor. The snapshot agent is only used to establish an initial database. The merged agent has executed the following jobs:
Merger Agents Upload all subscribers to change information. All information columns with no conflicts are immediately uploaded (these data columns are information columns that have not changed in the issuer and the subscriber). Conflict-related materials (these data are listed in the issuer and subscribers) will be sent to the conflict. Resolver is a module for resolving a conflict of conflicts in a merged replication, you can set your own solution. All changes can be used to the issuer. Merger Agents Upload all changes from the issuer's change. There is no conflict information column upload immediately; conflict is sent to the conflict. All changes are used to subscribers. This processing process will be repeated in accordance with the schedule. In the send subscription mode, the merged agent is executed in the transmitter; in the extraction subscription mode, the merged agent is executed in the subscriber. Each consolidated issue has its own merged agent program.
Using a merged complicated complicated complicated complicated compliance, the application level is very broad, which allows subscribers to modify the incremental information. This will bring a lot of benefits. The following is the application of consolidated replications: the company's internal information sharing: such as a department responsible for salary, accounts payable, and receivable accounts can access the same information. The user of each department can modify the information, then consolidate all modifications on the department's system. Multi-click sharing: When used by users of different locations need to use the same information, and need to modify the information, they can be used to recall.
Information delivery: MCD can be used as a message-delivered system, which can modify the information and transfer the changed data back to the original system. Set merged replication system setting merged replication and setting snapshots are similar to trading. First, you must set the distribution set and then subscribe to the issuer to send or extract.
Note You must set the issuance and distribution before setting any type of SQL Server replication. Please refer to the description of the
Setting the issuance set setting of the merged replication duplication set and the previous two types of issues have different, the following is the steps set:
Use Enterprise Manager to perform settings throughout the following steps, select Tools / Replication, press and manage the issuance set; or select Tools / Elf, choose the establishment of the wake wizard. The dialogue between the establishment and management of the issuance set can be entered with any party, as shown in Figure 28-1. Here you can choose the pre-issued database or data sheet. Figure 28-1 "Establishing and Management Distribution Set" dialogue
If the issuance set exists, the following buttons will be displayed:
Send a new subscription: You can create a new send subscription for the existing issues, this step will be discussed in the
Choose the issuance of the fund-raising material (as shown in Figure 28-1, select Northwind to the Distribution Capital Rack), select the establishment of the issuance set to enter the welcome to build the distribution set wizard window, as shown in Figure 28-2. Select the Advanced Options Options in this Elf.
Figure 28-2 Welcome window of "Establishment of the Works"
Press the next step to enter the library window of the selected release set, as shown in Figure 28-3. You can select the information you want to issue again. The library selected in step I will display it.
Figure 28-3 "Library of the Decoration Set" screen
Press the next step to enter the selection issuance set type screen, as shown in Figure 28-4.
Figure 28-4 "Select the Issue Type" screen
You can choose any copy type, the functions of the three issues are as follows:
Snapshot Issue: The snapshot of the issuance that can periodically reply to the subscriber. You can use any information table to establish a snapshot issuation. Trading-style issuance set: You can establish a trading replication set, which updates the subscriber data by the issuer's change. Only when the data table has a main index key, the issuance of the trading replication can be established. Completed issues: Credit Duplex Distribution Sets can be established, which allows you to double-mode between issuers and subscribers. You can use any information table to establish a merged issuation.
Press the merged issuance set, press Next to enter the specified subscriber type window, as shown in Figure 28-5. This window can specify if all subscribers perform SQL Server. Figure 28-5 shows the preset value, and the preset setting specifies that all subscribers perform SQL Server 2000. If this setting is accepted, it is set to set the copy of the data using the native SQL Server 2000. Others can also choose SQL Server 7.0 server, or other nature of server, this option will convert the reply information to the filament format, of course, have some complicated conversion procedures.
Figure 28-5 "Specify Subscriber Type" Window
Press Next to enter the specified issuance screen, as shown in Figure 28-6. In this picture, you can specify a data sheet or other database object as an issue to be dictated. These issues constitute the issued set you established. On the left, the listed items can be copied in the display, including the data sheet, the pre-deposit program, and the view table. Once any item is selected, the window of these items will be listed in the window. Then you can choose the information table you want to issue in the you're going to the right, or return to the window on the left, select all the information sheets in all Issuance items. Remember, each data sheet, pre-deposit procedure or inspection table is considered an independent issue, and the issuance set is constructed of a set of issues.
Figure 28-6 "Specified issuance item" screen
Note If the subscriber already exists, you can use a copy of the call pre-store, without delivering the result of the pre-stored program on the Internet.
Since the choice is a consolidated replication, we can define more properties for the issuance item. Press the [...] button to enter the information table issuance item property screen setting property, as shown in Figure 28-7. You can set different properties through the tab in this window, and Figure 28-7 is a general tab. Here you can specify the owner of the issuance item name and source data sheet and determine the definition of the data conflict. The preset option will change the same information line as a conflict. Figure 28-7 "General" tab in the "Data Sheet Release" attribute
Select Split Tab Specify the SPR, as shown in Figure 28-8. If you use a preset solution, the issuer will be considered one end of the victory when the conflict occurs. Also, if a conflict occurs between the subscriber, the first synchronized subscriber will be considered a winner (other subscribers that will be executed later are considered a failure). You can also choose another SPR or a custom solution. In the Merging Change tab (as shown in Figure 28-9), you can specify additional security to a specific operation. By selecting one or more options in checking use permissions, you can specify permission to consolidate the agent to perform specific operations, or specify check before performing some operations. In addition, there is a preset option in the tab page, specifying a multi-demarily update, accept this preset value. Press to determine the continued setting.
Figure 28-8 "Stroller" tab window in the "Data Sheet Release" attribute
Figure 28-9 "Merge Change" window in the "Data Sheet Release" attribute
Press Next. Check the result after the issuance set will be displayed here, and the most likely seen the window will be shown in Figure 28-10. Combined replication requires a unique identification line, this information guild will automatically add it to the information table. In addition, the NOT for Replication option will be created on the recognition data line.
Figure 28-10 "Problem of Items" screen
Press the next step to enter the selected issue set name and description screen, as shown in Figure 28-11. In this picture, a simple specified issuance set name is described in this. Press the next step to enter the property screen of the self-subscription set, as shown in Figure 28-12. In this picture, you can decide whether you need to define the data filtering or custom other issues, select No, and establish the issuance set according to the designated.
Figure 28-11 "Select the Issue Name and Description" screen
Figure 28-12 "Property of Self-Order Set" screen
Select Next to enter the completion of the establishment of the distribution wizard screen. To do it, you can see the process of establishing the issuance set of the elves, and the establishment of the setup will be established after the execution. Now check the compact information of the replication monitor, there is no information, which is because the merged agent program is used for two-way compilation, so you need to set the subscriber before replying. After the subscriber is set, the merged agent program will appear in the data clip of the SMS. Setting Subscription Like the previous two types, the last step of setting a merged replication is to set a subscriber. First, you must enable subscribers in the distributed database, enabled methods to introduce in the
Enter the extraction subscription spirit. Enter the welcome to use the extract subscription wizard screen. Press the next step to enter the search screen, select the issuance set in the server where the registered server is selected in this example. Press the next step to enter the selection issuing set screen and select the issued set to use. Press Next to enter the specified synchronous agent program login screen, specify the way the agent is connected to the issuer and login account. Press the next step to enter the selection of the database screen, specify which database is to be placed in. Press Next to enter the initial subscription screen, select the appropriate option. Press the next step to enter the snapshot collection, select the snapshot collection. Press the next step to enter the setting merged agent schedule screen. This screen setting is similar to the setup distribution of the setup of Chapter 27. You can refer to the previous setting logic to select the appropriate option. Press Next to enter the priority picture of the setting subscription, as shown in Figure 28-13. Priority means that when the conflict occurs, it is considered correct when the conflict occurs. The preset setting (also recommended settings) Specifies that when the conflict occurs, the issuer's settings are prioritized to resolve conflicts. Press the next step to enter the necessary service screen, and start the unusable SQL Server agent program. Press the next step to enter the completion of the extracting subscription spirit screen. After the view setting is determined, the selection is complete to complete the setting job of the subscription set, and now extracting the subscription periodically updated.
Figure 28-13 "Priority" screen for setting subscription
Setting Send Subscription Send Subscription To start in the issuer, you can use the Send Subscribe Elf to be set. Please refer to the following steps to send subscription wizels:
Use any of the following methods to enter the send subscription wizard. The first method is to press the tool in Enterprise Manager, select Subscribe / Send Subscription to other servers, and enter the establishment and management server issues dialogue, as shown in Figure 28-14.
Figure 28-14 "Establishing the Dance Set" dialogue of the Management Server
Select a distribution set in the Database and Issue, and press the Send a new subscription button. To use the second method to enter the dialog box of Figure 28-14, select the tool in the tool column, select the wizard in the selection list, then expand, and select Establishment Send Subscription Wizard. After sending new subscriptions, you will see the welcome wizard screen as shown in Figure 28-15.
Figure 28-15 "Welcome to the Send Elf" screen
Press the next step to enter the selection subscriber picture, as shown in Figure 28-16. Here you can specify which subscriber to send to the issuance set. Select the subscriber in the enabled subscriber list.
Figure 28-16 "Select Subscriber" screen
Press the next step to enter the selection target, as shown in Figure 28-17. Here you can specify the subscriber's database, you can choose the existing database, or create a new database as needed. Press the browse or create buttons to see a list of existing databases. To create a new database, press this button to set up a new item again, then create a new database in the information library properties. Press the next step to enter the location screen of the set merge agent program, as shown in Figure 28-18. Specify the location of the merged agent execution, select the preset value to the merged agent program, and you can also choose to execute the agent at the subscriber. It is recommended to accept preset unless the work is very busy.
Figure 28-17 "Select the Database" screen
Figure 28-18 "Setting the Compound Agent Program" screen
Press the next step to enter the scheduled screen of the merged agent, as shown in Figure 28-19. Here you can choose a continuous update subscription or select the scheduled schedule. Select the Subscribe Subscriber according to the scheduling, press the Change button to enter the Edit Repeat Job Schedule Square Change Schedule and Update the Frequency. Remember If you choose a continuous update, it will cause the system's burden. Figure 28-19 "Setting the Merge Agent Program" screen
Press the next step to enter the initial subscription screen, as shown in Figure 28-20. Here you can specify whether the subscribe set needs to be initialized. The initialization structure description and the subscriber's data set has been specified by the preset. If the structure description already exists, it cannot be selected, ... this option. The snapshot agent program can also be started in this picture. It is recommended to start the snapshot set agent program when initializing the quick illumination set, otherwise you must manually start the agent. Once the snapshot set is enabled, the snapshot set is not used before the new subscription is established. Each new subscription is established, it is necessary to establish a new snapshot set. Press the next step to enter the priority screen of the setting subscription, as shown in Figure 28-21. Here you can set the priority of the subscription when the conflict occurs. Establishing a preset value, that is, when the conflict occurs, there will be priority.
Figure 28-20 "Initialization Subscription" screen
Figure 28-21 "Priority of Setting Subscription"
Press the next step to enter the necessary service screen, as shown in Figure 28-22. Here you can start the SQL Server Agent that has not been launched.
Figure 28-22 "Start the necessary service" screen
Press the next step to enter the completion of the subscription sprite screen, as shown in Figure 28-23. Check if all settings are correct, press and complete the start of the snapshot set to the subscriber's program. You will see a conversation block for a description program, and finally the message block completed by the operation program. When the wizard is completed, send a subscription to establish and update regularly.
Figure 28-23 "Completing Send Subscription Elf"
Managing Replication Learn how to establish and set up a repository in the SQL Server 2000 environment, you can now learn to use Enterprise Manager's monitoring features and setting options, management and troubleshooting when rewriting cannot be executed as expected. Surveillance and Management of the Complication Program Operation in Enterprise Manager can find the agent program. Please refer to the following steps to access the proxy program:
Expand the servo group, your server, and reply monitor data clips. If the publisher server, the issuer, and the agent program folder will appear in the replication monitor data clip. The issuer's data clip contains all the issuers belonging to this server. The agent programcard contains a snapshot set agent program, distributing agency program, merged agency, and other agents with information on removal and history.
Although the agent usually does not need to be manually started or stopped, you can use a replication monitor when needed. If the replication system is not executed in accordance with the setting, it is probably due to the use of the preset option without immediately starting the snapshot agent program. (This is why we recommend that the initial express collection is performed immediately before the setting process. Press the agent program folder in Enterprise Manager, check the status of the agent, and reserved information about the agent program in the right pane, as shown in Figure 28-24. Here you can decide whether to perform an agent program, or you can see if the agent is in use. When a proxy is launched, the agent is executed until the task is completed, then stopping the job. At the terminal, the SQL Server agent will be divided into the agent.
Figure 28-24 Merger Agents in Enterprise Manager
Press the right button to call the fast display function table in the agent program, and there are several options that provide monitoring and managing the agent, as shown in Figure 28-25. Summary of these options is as follows:
Error Details: List all the wrong lists that have happened. Agent program history: List the agent program activity. Agent Properties: Let you modify the scheduling of the copy agent program, the information, the proxy step, and the operational action after the job is completed, for example, you can choose to let the system notify you the completion of the agent execution event. Agent program setting file: You can review and modify the agent program parameters, such as logging in over time, the batch operation size, and the setting of the query time is over time. Perform a proxy program at the subscriber: You can specify the proxy program in the subscriber. Execute agency in a radiator: specifies that the agent program is executed in the distributor. Start a proxy program and stop agency: You can start or stop the agent program. Realizing the speed and set value: You can modify the frequency of reintegration to perform monitoring data. Select the field: You can specify the result of the result of the result to be viewed. Display anonymous subscription: Specify whether to display anonymous subscriptions in the window. Description: Provides explanation information about this window. Figure 28-25 Merged Agent Options
After setting the merged agent program, you may need to modify the behavior mode of the merged agent program. For example, you can specify the startup mode of the merged agent program. In continuous mode, the merged agent is also started after the SQL Server agent program is started. In the mode executable in accordance with the scheduled schedule, the merged agent has been started in accordance with the scheduled scheduled schedule, and the transaction to complete the read and write transaction record will stop. Changing the mode and other properties can improve performance performance and reduce the burden of the issuer. The following is the step of setting the merged agent:
In Enterprise Manager, expand the server you want to modify, expand the copy monitor data clip, and select the merged agent program folder after the agent program is expanded. In the pane on the right, select the issuance set to right button to call the fast display function table, then select the agent program attribute.
Merger Agent Properties Windows appear, as shown in Figure 28-26.
Figure 28-26 "General" tab in the "Merge Agent Properties" window
Select the step tab as shown in Figure 28-27. On the tab, we can see the steps executed by the merged agent, each of which is performed by:
Record the read agent program startup message: Record the message in the history record of the record read agent (in the MSLogReader_histroy data sheet) of the distributed database). Perform a proxy program: Start the agent according to the specified scheduling, when the mode is continuous, the agent will stop execution at the end of the system. Detecting the end of the non-recorded agent: Put the message that the agent event failure is in the history record of the record reader agent. Select Perform Agent Steps Select the Edit button to enter the editing job step dialogue, as shown in Figure 28-28. In this dialogue, you can set how to start the consolidated agent program.
Figure 28-27 "Step" tab in the "Compound Agent Properties" window
Figure 28-28 "Mental" tab in the "Edit Step" dialogue
Merger Agents can set a lot of options. The preset merged agent program parameters can be changed in the details of the command squares and the DRC setting file (later will be described later). The two parameters that can be changed are as follows:
Contunuous: Specifies whether the merge agent is executed in a continuous mode or according to the schedule. Delete parameters can be executed according to the schedule. DistributorsecurityMode: Specifies the consolidation agent program to verify using SQL Server or Windows NT mode.
Alternatively, you can specify other parameters in the editing dialogue, such as login timeout, buffers, polling interval, query timeout, distributors, and issuer information and Output.
Related Information The settings of these parameters can be found in SQL Server "Online Books". After entering the merged agent program in the index tab, select the startup topic. After completing the modification of the merged agent program attribute, press OK to save the modification. With the merge agent program, you can modify other options, follow these steps:
In the pane on the left of Enterprise Manager, expand the merged agent program, select the Right button, call the fast display, select the agent set file, as shown in Figure 28-29.
Figure 28-29 "Merger Agent Settings" dialogue
Note that the options included in this dialogue are more than recorded reader agents (which is described in Chapter 27). These setting files provide a functional range that allows you to choose a most suitable setting file. Press to add a setup button to create a new setting file. Existing settings are not allowed to modify. When the button is pressed, it will see the screen as shown in Figures 28-30.
Figure 28-30 Detail of the Details of the Docked Agent Settings "dialogue
In this dialogue, you can modify the following parameters:
BCPBATCHSIZE: The number of information transmitted in a large number of copies. When executing BCP in a job for structural descriptions, the "Merge Agent" uses the batch size to determine the time of the recording progress message. Value 0 indicates that no message is not logged. ChangesPerhistory: Record the critical value of uploading and downloading the message. DownloadGenerationsperbatch: From "Publisher" Download Change to "Subscriber", the number of generations in a single batch is processed. The generation is defined as a logical group of changes in each issue. The preset value of unreliable communication link is 10. However, under various conditions, the actual number of generations processed each batch will equalize the larger value between the UPLOADGENERATIONSPERBATCH setting and the number of issued issues. DownloadReadChangesperbatch: From "Publisher" Download Change to "Subscriber", the number of changes read in a single batch. DownloadWriteChangesperbatch: From "Publisher" Download Change to "Subscriber", a single batch is used in a single batch. FastrowCount: Specifies the type of the data column count method used when verifying the data column count. Numerical 1 (preset value) represents a quick way; numerical 0 represents a method of using a full data column count. HistoryverBoseEvel: The number of processes recorded during the merge work can be:
Always update the previous history message (start, progress, success, etc.). Insert a new record if there is no previous record of the same state. This level will record the minimum number of messages. Insert a new process record unless this record is used in an item similar to the idle (IDLE) message or a long-term execution, the previous record is updated. This level will record the message of level 1 and other messages in progress. Always insert new records unless it is an idle message. You can set the ChangesPerhistory parameter to minimize the effect of the history record. KeepaliveMessageInterval: History Performing Conditioning Check for the number of seconds before waiting for the server to respond. This value can be added to avoid long-term execution batch, the agent program is inspected to be inspected to be suspicious. Logintimeout: Try to log in before the agent has timeout. MaxDownloadChanges: The maximum number of changes you want to download during the specified merge work phase. Since the complete generation is handled, the number of downloaded information columns may exceed the specified maximum. MAXUPLOADCHANGES: The maximum number of changes you want to upload during the specified merge work phase. Since the complete generation is handled, the number of columns uploaded data may exceed the maximum value specified. MaxdeadLockRetries: The number of times the merge process re-attempts the internal job while suffering from Deadlock. Can be any value between 1 and 100. PollingInterval: In continuous mode, the "Publisher" or "Subscriber" query the number of seconds. QueryTimeout: The number of queries will be issued before the agent has passed the timeout. UPLOADGENERATIONSPERBATCH: Since the "Subscriber" upload change to "Publisher", the number of generations processed in a single batch. The generation is defined as a logical group of changes in each issue. The preset value of unreliable communication link is 1. However, under various conditions, the actual number of generations processed each batch will equalize the larger value between the UPLOADGENERATIONSPERBATCH setting and the number of issued issues. UploadReadChangesperbatch: From "Subscriber" Upload Change to "Publisher", the number of changes read in a single batch. UPLOADWRITECHANGESPERBATCH: From "Subscriber" Upload to "Publisher", the number of changes in single batch is used. Validate: Specifies whether it is to be verified at the end of the merged work phase, if so, this verification is not. Value 0 (preset value) means no verification. Numerical 1 indicates that it is only verified by the data column count. Numerical 2 indicates that the data list count and the CHECKSUM verification. Value 3 represents the binary plus total check code (only for SQL Server 2000). ValidateInterval: When setting to continuous mode, verify the number of minutes. If the merged docker is executed according to the scheduled mode, it will be started by the SQL Server Agent, and the number of times the change is handled according to MaxUploadChanges and MaxDownloadChanges. Deactivate Documents Using Enterprise Manager to deactivate all or part of the replication, as long as you remove the selected replication components in the Enterprise Manger's reputation. This section will learn how to implement this job.
Removing Send Subscription In the radiator system, send subscriptions using Enterprise Manager to send subscriptions. After starting the send subscription, the establishment and management issuance set dialog will appear. After pressing the subscription to delete, press the right party to delete the set of issues, the prompt block, ask if you confirm the deletion of this subscription. Press to remove subscriptions. Removing the extraction subscription In the subscriber system, the extract subscription can be removed using the ENTERPRISE Manager's extraction subscription wizard. After starting the extract subscription, the establishment and management issuance set dialog will appear. After pressing the subscription to delete, press the right party to delete the dash button, the prompt block appears, ask if you confirm the deletion of this subscription. Press to remove subscriptions. Removing and issue to remove distribution and distribution, you must open the disabled distribution and distribution wizard. In the first picture of the wizard, you must specify whether all distributed and release, or remove the release. If the first option is selected, all the issues, subscriptions, and distributors on the server will be removed; if the second option (preset option) is selected, only the issuer will be removed. After the option is determined, a confirmation screen will appear, and then the selected replication component will be removed after the button is pressed. Monitoring and Calling of Corporated Documents This section will learn how to monitor and calibrate the merged replication system to make it optimized. In addition, the set points of the merged replication system will also be introduced, and the attributes of the consolidated replications are also introduced. The consolidated rewritable attribute consolidated compounds and other two types of reprocesses are not very different, and the maximum difference is that the merger replication does not adopt a one-way copy method, and the issuer or any subscriber can be modified. In addition, the transaction record file of the trading type is read to track changes, belonging to external operations of SQL Server; consolidated compounds are to establish trigger programs in the replication data table to track changes. The snapshot set is taken in the first execution of the consolidated compound, but only once, so there is no need to adjust the fast-tracking process. The merged copy is simultaneously established in the issuer and the distributor to perform the replication. In addition, a GUID information guild will be added to each of the data sheets, which can uniquely identify each of the data columns, so the reply agent can track the affected changes. When inserted or modified by the data column, the trigger program tagged the information to write, and when the merged agent program is started in the future, it will be sent to the distribution of the distribution. At the same time, the information columns modified in the subscriber system will also be modified to the issuer. This completes the two-way copy programs. Setting the merged complicated complicated complications requires the correct settings of the I / O subsystem of all participating systems. The network is also very important to improve reproction performance. Setting the correct batch operation size is also important. If the batch operation size is increased, the content of each batch operation is increased, and the number of files is small, which is more efficient. In addition, you can also call fast-seeking. However, since the snapshot application only uses only once, this step can be skipped. Finally, you can modify the consolidated agent, this modification has mentioned this chapter. This section describes the settings of I / O and merging batch operation capacity. Set enough I / O capacity If the capacity of I / O is sufficient, the performance of the replication process can be enhanced. Like other SQL Server systems, transaction record files responsible for records in the system should be placed in their own RAID 1 disk area to protect data, and the data file should be placed in one or several RAID 10 or RAID 5 disk disks . The same place as the trading type is that the merged replication requires only a micro-adjustment standard I / O setting. In general, when setting the issuer's I / O subsystem, it should be set in accordance with the key points constant in this book.
And trading reprocesses differ, consolidated rewrites do not increase the burden of transaction record files, as long as they follow the general point settings. The transaction record gear of the distributed I / O subsystem radiator library should be set in the RAID 1 disk area. This allows the record file of the distributor database to achieve the best performance, improve the performance of the distributed person. In the subscriber set I / O subsystem, the subscriber and the issuer's school modulation mode is similar, and as long as the general point is set. Setting the merged batch operation capacity In a busy system, you can improve reproction using the settings that combine batch operation capacity. The merged batch operation capacity determines how many changes in a single batch of operations are written. If the batch operation capacity is increased, each batch operation is increased, and the number of files is small, which is more efficient. Monitor combined replications Monitor transaction-based compliance activities can be performed through the Viglation Monitor. Efficacy Monitor will add some items when installing SQL Server, the objects are as follows: SQLServer: Replication Agents: Calculation Now there are several different types of agents in the system being executed. SQLSERVER: Replication Merge: Provides rate information about the merged complications, including conflicts per second, uploaded and downloaded. Please note that these information will not really have a way to assist the school call. Using the performance monitor to monitor these values to let you know if you have difficulty in performing performance. Although these performance monitor materials provide a lot of useful information, it is not necessarily to find true problems. Calling the best way to compare the best way to pay attention to the performance of the network, and the check may generate a network performance bottleneck. Referring to the main points in the first two chapters, check if the distributed load is too heavy. The main steps of caller-calling complicated replications to calibrate complicated replications are the correct settings and monitoring systems, which have been mentioned in the previous section. Monitor your system through the Efficvision Monitor, pay attention to the performance of the network. However, for consolidated replications, the information provided by the Efficiency Monitor is not so useful. Instead, you may need to refer to the system with the counter of the other SQL Server's counter and the Microsoft Windows 2000 counter. Chapter 24 Once mentioned that when the number of updates of the system is frequent, you may need to modify BCP batch operation capacity and merged batch operation capacity. If the BCP batch operating capacity is increased, the performance performance of the original snapshot agent will also increase. If the merged batch operating capacity is increased, the number of files in each batch is less, and the number of updates is reduced, which is more efficient. However, there will be more workloads when compliance. In addition, you can change the polling frequency and change the polling frequency to increase or decrease the frequency of consolidated replications. However, if it is not necessary, this change is not recommended. If you want to call the polling time, try to change the batch operation capacity. If necessary, monitor whether the network can carry load. If the system is not executing, for example, if the CPU and I / O subsystem reachable, or the time is too long, it may be a problem. The problem of the network is more difficult, because the problem of the network is not the inspection efficiency monitor, and there may be a network monitoring product such as Microsoft System Management Server (SMS) to monitor whether the network card has been saturated. If the network card has reached a saturation, the solution is to buy faster online cards, or add a exclusive network to write, backup, and recovery. Whether it is issuer, distributor or subscriber, it belongs to the SQL Server system. So the way these systems are noted as they should pay attention to when the SQL Server system is adjusted. This chapter summarizes the last chapter of the copy series. In this chapter, you should have learned the execution of the merged replication, and the purpose of the consolidated replication.
