This Client Server article is republished in its entirety from 2004 for reference purposes.
By Bentley Technical Support Group25 October 2004
AutoPLANT provides a wide array of options with regard to project modes and supported project databases. It is important to understand all of the benefits related to these options for a successful AutoPLANT project.
When considering AutoPLANT project modes and database options, ask yourself a few questions:
The term "project mode" refers to the different ways information can be stored in the PDW environment. There are three available project modes:
The Standalone mode is typically recommended for projects that include only a few documents. All PDW data is stored in the local drawing database. In this project mode it is not possible to share information between PDW and PIW, import and export documents, and have component connections between PDW documents. This project mode is most like PDW 2.01.
In Distributed mode, all piping and equipment data is stored in a drawing database (MDB) alongside the PDW drawing (DWG). Items called project objects (line number, area, unit, and service) are stored in the project database. This mode allows the three main functions that Standalone prohibits, sharing information between PDW and PIW, importing and exporting PDW documents, and having component connections between PDW documents.
The Central project mode is the most robust and favored mode of operation. All piping and equipment data is stored in the Project Database, thus eliminating the need for a local drawing database. Only DWG files are required by the user, which provides for a more stable environment. Project objects (line number, area, unit, and service) are stored in the project database as well. All data can therefore be managed from one centrally located database.
he following table considers the above described project modes:
Note: The values in the table are recommendations.
The following four database providers are supported for AutoPLANT projects:
Microsoft Access does not require the configuration of a server and is easy to use. Typically, a DBA is not required. Access does not handle concurrent connections very well, which limits the number of users.
MSDE stands for Microsoft SQL Server Desktop Engine. This database option does not require the configuration of a server. With an ADP link in Microsoft Access, this SQL Server data can be viewed. You get the power of SQL Server with the ease of Microsoft Access. However, we recommend using SQL Server, not Microsoft Access, to administer an MSDE project. SQL Server provides tools to manage and compress an MSDE database.
A SQL Server database is capable of 32,767 concurrent connections (theoretical). The size of the database is limited only by the hardware. The SQL Server database is hidden from users and provides better security. This option requires the configuration of a server.
An Oracle database is capable of unlimited concurrent connections (theoretical). The size of the database is limited only by the hardware. Again, the Oracle database is hidden from users and provides better security. This option requires the configuration of a server and client machines.
The following table considers the above described database options:
With the above project modes and database options available for use with AutoPLANT, you may want to discuss this document and your concerns with Bentley Support or Services personnel. They will be able to guide you and provide suggestions with regard to project setup and configuration.
Client Server Archive
Plant TechNotes And FAQs
Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!