Global Databases

You can split a project so that its data is distributed across a number of locations by making the project into a Global project. The AVEVA base product users in the different locations access the same project. The project’s distributed nature is largely invisible to the users. Each location has its own local copy of the product, and local copies of the AVEVA base product databases. To make sure the integrity of data, the project databases are automatically checked and incremental updates are issued across all project sites.

Before the user sets up a Global project, they must understand the basic concepts involved, and the user must carry out some preparatory steps. For detailed information about the Global management concepts, and about how to set up and manage a Global project, the user is advised to read the AVEVA Global User Guide. The user is also advised to take a full backup of their project, as the process of making a standard project into a Global project cannot be reversed using the AVEVA base product.

Then, to make a Global project, the user simply issues a MAKE GLOBAL command from the AVEVA Administration command window. This command splits the System database, creating a local System database and a Global database. The project becomes a Global project based at one Location, known as the Hub. Such a single-location Global project behaves like a standard project as far as most users are concerned. However, the project can now be split over multiple locations.