Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Engineering

TABLE OF CONTENTS

Database Access

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedNov 26, 2021
  • 1 minute read

This section introduces the basic database access mechanism. For information about more extensive Data Access Control, refer to Data Access Control (DAC).

Database access depends on attributes of the User and of the Database.

Users can be FREE or GENERAL:

FreeUsers

May enter all modules.

May update any databases.

General Users

May not enter the Restricted modules; usually AVEVA Administration and Lexicon.

May only modify databases for teams of which they are members.

Restricted Users

Allows a user read-only access to a database, due to:

  • The user has general security (as opposed to free) and is not a member of the database's team

  • The database is secondary at a Global location

  • The database is included foreign from another project.

Note:
User privileges also control access to modules; refer to Modules.

Databases can be Update or Multiwrite:

Upated

Allow one writer and n readers.

Multiwrite

Allow m writers and n readers. Refer to Multiwrite Databases and Extracts for further information about multiwrite databases.

Model, Catalogue, Draft (PADD) and Isodraft databases can be multi-write. The System database is always multi-write.

Both Update and Multiwrite databases can also be Controlled, in which case write access is controlled externally to the AVEVA base product. Refer to Controlled Databases.

  • The user can change an update database to multi-write at any time.

  • The user can only change a multi-write database to update if no extracts have been created from it. Refer to Extracts for further information.

TitleResults for “How to create a CRG?”Also Available in