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

AVEVA Enterprise SCADA

Deploy an extended or modified database structure

  • Last UpdatedApr 24, 2025
  • 1 minute read

If you modify the database schema, ensure that you apply the change to all systems before deploying packages that include the new database structure. Otherwise, the zones will not be able to recognize and handle the customized database structure, and package deployment will fail.

Prior to creating any new packages with database modifications, deploy and run an .MSI package with those modifications on each independent RealTime node in every MoC zone. Refer to Reconfigure RealTime database (RTDB) fields for more information on database extensions and database conversion.

Important: Regardless of whether or not they are specifically referenced by individual projects, you should never delete AVEVA Enterprise SCADA databases and tables. AVEVA Enterprise SCADA routines often assume the existence of these tables and will not operate correctly in their absence.

If you are patching the systems to a higher level, ensure that the new patch is applied to all RealTime servers in the environment before deploying the packages. Package deployment will fail when patches are mismatched between machines in the environment, regardless of whether the server is Hot or Standby, owning or non-owning. All machines must have the same patch in order for the package deployment to succeed.