Before starting your configuration for Global Workshare with SQL Server, you need to decide how the data is managed or controlled.
For the catalog, catalog schema, site, and site schema, the Host should control the data. The other machines are Satellites of the Host. The Host is a Publisher of site, site schema, catalog, catalog schema, and model data to the Satellites and a Subscriber of model data from the Satellites. The Satellites are Subscribers to the Host for site, site schema, catalog, catalog schema, and model data. They are Publishers of model data to the Host. In small and midsize configurations, the database server is usually its own distributor. However, in the case of large configurations or multiple smaller configurations, it is possible to use a dedicated distributor server. You can specify whether you want to use a dedicated distributor server when you configure the SQL Server Distributor Agent.
One-Way Transactional Replication
Using One-Way Transactional Replication, you have a Host machine for your catalog, catalog schema, site, and site schema. This means that the Host machine communicates information to your Satellite machines, but the Satellites do not communicate information back to the Host. The Host machine is the Publisher, and the Satellites are Subscribers. The communication is all one-way from the Host to the Satellites.
Two-Way (Peer-to-Peer) Replication
For the Model database, you set up Two-Way (Peer-to-Peer) Replication. The Host machine operates as both a Publisher and a Subscriber, pushing information to the Satellites and receiving changes from them. Likewise, your Satellite machines are Publishers and Subscribers so they can communicate changes to the Host and receive information from the Host. The communication is two-way.
The following workflow steps pertain only to configuring Global Workshare for SQL Server databases.
Project administrators manage all Satellite creation and administration from the Host location, and use permission groups to determine data access for both Host and Satellite locations.
The term Peer-to-Peer in SQL Server documentation is what we refer to as a Hub and Spoke configuration.
The procedures below assume some familiarity with the Project Management environment for Global Workshare and are targeted to specific SQL Server settings. For more information, see your Microsoft SQL Server documentation.
Set Up a Configuration of Replicated Servers
Several steps are involved when setting up a first-time configuration of replicated servers for SQL Server.
The SQL Server Replication feature must be installed on the SQL Server instance set up for the Global Workshare configuration.
Configure each server for replication.
Set up a SQL Server Distributor Agent.
Create a profile for the distributor agent.
Set Up Global Workshare with SQL Server
After you create the SQL Server Distributor Agent, you can set up the Global Workshare configuration (GWC) for the SQL Server databases.
For information on setting up permissions for your data, see Permission Groups and Global Workshare.
Set Up Replication Using the SQL Server Wizard
You need to set up one-way replication subscriptions for the catalog, catalog schema, site, and site Schema. For the model, use Peer-to-Peer, two-way replication.
Set Up One-Way Subscriptions for SQL Server
Set Up Two-Way Replication between SQL Server Models
Regenerate Reports Databases
For performance reasons, the reports and reports schema databases are not replicated from the Host location. Instead, at each Satellite location you must point to the site and site schema databases on the respective servers, right-click the model in the Project Management tree view, and then select Regenerate Reports Database. For more information, see Regenerate the Reports database.
Add Satellites to Existing Global Workshare Configurations
After you have set up a Global Workshare configuration with SQL Server, you can add new Satellite locations to the existing configuration.
Remove Replication between a Host and a Satellite
You can remove the replication between a Host and a Satellite in a Global Workshare configuration with SQL Server.
You can also consolidate an existing configuration, or remove all replicated Satellites.
Disable Replication on a SQL Server Instance
If you need to "start from scratch", it can be useful to completely disable all replications within a SQL Server instance.
Monitor Replication in SQL Server
You can use the SQL Server Management Studio to monitor replication activity.
Configuring Global Workshare within an integrated environment is a detailed and complicated process. For more information, contact Intergraph Support at http://www.intergraph.com/support.
What do you want to do?