Set up two-way replication between SQL Server models - Intergraph Smart 3D - Administration & Configuration - Hexagon

Intergraph Smart 3D Project Management

Language
English
Product
Intergraph Smart 3D
Subproduct
Project Management
Search by Category
Administration & Configuration
Smart 3D Version
13

You use the Microsoft SQL Server Management Studio to set up two-way subscriptions for the model. See your SQL Server documentation for information on using Microsoft SQL Server Management Studio.

The following procedure must be performed on the Host machine.

  1. From Microsoft SQL Server Management Studio, in the Object Explorer, right-click the publication created on the Host machine for the appropriate database.

  2. Expand Replication > Local Publications.

  3. Right-click the Model database, and select Configure Peer-to-Peer Topology to open the Peer-to-Peer Topology Wizard.

  4. Click Next to go to the Publication page of the wizard. Select the publication to which to add a new subscriber and click Next.

  5. Right-click an empty area on the Configure Topology page, and select Add a New Peer Node to open the Connect to Server dialog.

  6. Select the first Satellite in the Server name list, and then click Connect to open the Add a New Peer Node dialog.

  7. Select the Model database from the Select Database list, and then click OK to close any open dialogs and return to the Configure Topology page.

  8. Repeat steps 5 through 7 to add more Satellite servers.

  9. On the Configure Topology page, right-click the Host server icon and select Add a New Peer Connection to display a small arrow.

  10. Extend the arrow to the first Satellite server you added.

  11. Repeat the previous two steps for each Satellite you added.

    To set up a Hub and Spoke configuration, make connections only between the Host and each Satellite. Do not connect a Satellite to another Satellite.

  12. Optional: To configure a pull subscription for a Satellite, right-click the arrow that links the Host to that Satellite, and then select Use Pull Subscription. Although a pull subscription is more difficult to manage than a push subscription, a pull subscription delivers better replication performance on a high latency network. Consider using a pull subscription if the network latency is greater than 100 ms, such as when servers are located on different continents.

    You cannot restore a copy of a model database in the same database instance that is using a pull subscription.

  13. Click Next.

  14. On the Log Reader Agent Security page, specify how the Log Reader Agent connects to each server. Click the ellipsis button to set up the connection information for each server on the Log Reader Agent Security dialog. If the same user can connect to the host and satellite, check Use the first peer's security setting for other peers.

  15. Specify a user name and password for the Log Read Agent process. Click OK to accept the settings and return to the wizard.

  16. Click Next on the Log Reader Agent Security page to continue to the Distribution Agent Security page, where you can specify a different user for each server or select the Use the first peer's security settings for all other peers check box.

    If you click the ellipsis button, the Distribution Agent Security dialog displays, allowing you to specify who can connect to the distributor. For the Connect to the Subscriber section, specify who has enough access on the remote server. Click OK to return to the Distribution Agent Security wizard page, and then click Next to continue through the wizard.

    You can configure the distribution and log reader agent security details to run under the SQL Server Agent service account if all necessary database privileges are met for the actions that the agents will perform.

  17. On the New Peer Initialization wizard page, we recommend that you select I restored a backup of the original publication database, and the publication was changed after the backup was taken, and then specify the location of the Model backup that was transferred to the other locations. Consult the SQL Server documentation for more information.

    Select I created the peer database manually, or I restored a backup of the original publication database which has not been changed since the backup was taken only if you are sure that no one has worked on the Model (including quick test), and that no services (such as Interference Checking Service) were running on the model since the backup. However, we recommend that you select I restored a backup of the original publication database, and the publication was changed after the backup was taken because any problems caused by choosing the first option might not appear for weeks.

  18. Click Next to continue.

  19. Verify the choices you made in the wizard, and click Finish to process the peer-to-peer configuration.