Project Database Configuration Category

The Project Database Configuration Category is divided into two sub-categories:

Settings Sub-Category

The application pane is divided into the following sections:

SQL Server Settings Section

Project data is stored in an SQL database. This section is used to enter details of the SQL server the project database is to use. These details are initially specified when a project is installed or upgraded, but they may subsequently be amended here.

Enter a valid server name in the Server Name field.

Depending on whether the database is to be logged into using Windows Authentication or SQL Server Authentication, select either the Use Windows Integrated Security (Windows Authentication) option or the Login as Administrator with password (SQL Server Security) option.

If the second option is selected, enter the login details in the Admin Login Name and Password fields. This login must be a valid SQL Server Administrator account login.

Test that the entered details are valid by selecting Test Connection. A message will then be displayed indicating whether or not the connection details are valid. For example:

Online Editing Section

If label data is to be saved automatically to an SQL database when it is entered, check the Save to database on Update checkbox. The saved data is used when validating the uniqueness of tags in a project. Refer to Label Validation across all Project P&IDs

When a project is upgraded, in order for Spec Driven data and functionality to be available (refer to Spec Driven Configuration Category), the project database schema must be updated by selecting Upgrade Specdriven Database Schema - Upgrade.

SQL Replication Settings Section

Select Help to view details of these settings.

Check the Restrict write access to drawings based on server name originator checkbox if only the originators of drawings (based on their server names) are to have write access to drawings.

AVEVA P&ID in Citrix Section

Select Help to view details of how AVEVA P&ID functions with Citrix.

Compare/Update Settings Sub-Category

If required, the Compare/Update facility can be used to update a different AVEVA P&ID Reports database from that of the current project. For example, the user can update the P&ID Reports database of the IPE project using the SAM project's Compare/Update functionality.

These "destination" database configurations are defined using this sub-category. They are then available when setting up Compare/Update configurations in AVEVA P&ID Reports.

In addition, this sub-category lists the "source" configurations set up in AVEVA P&ID Reports for the Compare/Update facility (refer to the AVEVA P&ID Reports documentation for details). It provides facilities to import, export, delete, and rename these configurations.

Add a Destination Configuration

To add a destination database configuration, first select the database type from the Data Source list (SQL Server or Oracle):

Next, click Add Configuration.

If the SQL Server database type was selected, the following dialog is displayed:

If the Oracle database type was selected, the following dialog is displayed:

Enter the required details of the database and press OK. The new destination configuration is then added to the upper grid:

It will now be available when setting up Compare/Update configurations in (refer to AVEVA P&ID Reports documentation for details).

Delete a Destination Configuration

To delete a configuration, select it in the upper grid and press Delete Configuration.

Source Configurations

The "source" Compare/Update configurations set up in AVEVA P&ID are displayed in the lower grid.

• To rename a configuration, simply type over its name in the Configuration Name column.

• To delete a configuration, select the configuration row in question and select .

Import a Source Configuration

Source configurations can be imported from XML files.

To import a source configurations, click on the Import from XML link. The Import Configuration File dialog is then displayed:

Click Browse. From the Open dialog that is then displayed, browse for and select the XML file, and click Open.

The selected file and file path will then displayed in the Import Configuration File dialog.

Select Import to import the selected configuration.

If the selected configuration already exists in the current project the user will be prompted to either overwrite the configuration or to cancel the process:

If the configuration is imported, it will be added to the other configurations listed in the lower grid.

Export a Source Configuration

Source configurations can be exported as XML files. These files can then be imported for use by other projects.

To export a source configuration, select the configuration row in the lower grid and click the Export to XML link.

A Browse For Folder dialog will then be displayed.

Browse for the folder to which the XML configuration file is to exported, and click OK.

If the selected configuration file already exists at that location, the user will be prompted to either overwrite the file or to cancel the process: