Database requirements

The TrueSight Network Automation application server requires a database. Currently, Network Automation supports the following databases: 

  • Embedded PostgreSQL
    The embedded PostgreSQL database is packaged and installed with the product. It is configured to function with minimal maintenance.The product administrator is responsible for configuring options for the external databases. 
  • Remote PostgreSQL (RPostgreSQL)
  • Oracle
  • Microsoft SQL Server
Recommendation

BMC strongly recommends that an external database be administered by a qualified database administrator (DBA) to configure, monitor resources (such as disk space and table space), make backups, and troubleshoot the external database.

This topic describes the supported database versions and a few considerations for external databases. 

Note

Supported databases

Note

If you would like Network Automation to support any particular version of database, log an IDEA on BMC Communities.

The following databases are supported for use with the application server:

  • Oracle Database 12c1 (external database encryption)
  • Microsoft SQL Server 2019 (support for encrypted connections)
  • Microsoft SQL Server 2017 AlwaysOn Clustering
  • Microsoft SQL Server 2017 Active-Passive Mode Clustering
  • Microsoft SQL Server 2016 (support for encrypted connections)
  • Microsoft SQL Server 2014 (support for encrypted connections)
  • Microsoft SQL Server 2012 (support for encrypted connections)
  • PostgreSQL 14.1
  • PostgreSQL 13.2
  • PostgreSQL 12.6

  • PostgreSQL 10.22

    Note

    1. The supported version of 12c is 12.1.0.2 with pluggable database (PDB).

    2. When you choose the embedded database option, Network Automation version 23.2 use the PostgreSQL version 14.6.

Warning

Network Automation does not support database compression. Therefore, you must disable database compression prior to installing or upgrading Network Automation.

Considerations during a fresh TrueSight Network Automation installation

  • For SQL Server and PostgreSQL databases, you can create a new database or use an existing one. When using an existing database, the existing database must be clean or empty.
  • For an Oracle database, you can create a new database or use a existing one. When using an existing database, the database schema must be fresh.
  • For an Embedded PostgreSQL database, Network Automation handles the database requirements.
  • Disable database compression.

Important

You cannot change the database type during upgrade.

Oracle and SQL Server database requirements

The following table lists the parameters supported by Oracle and Microsoft SQL Server database servers:

Parameter

Supported by
SQL Server

Supported by
Oracle Server

Are_there_heap_tables

Yes

Yes

Require_DBM (Database Mirroring)

No

No

Preferred Fill Factor for indexes

Default

Default

Is_Data_Archievable

Yes

Yes

Is_Application_logging_in_DB 1  

No

No

Is_Linked_Sever_leveraged

No

No

Is_Bulk_Data_Loaded

No

No

Is_SQLCLR_leveraged (Dot Net CLR)

No

No

Is_Non_Default_Collation_leveraged

No

No

Are_Extended_SPROCs_leveraged (Extended Stored Procedures)

No

No

Is Master_DB called (For SQL Server)

No

No

Is_Partitioning_leveraged

No

No

Are_Materialzied_Views_leveraged

No

No

Are_Triggers_leveraged

No

No

Is_Auditing_leveraged

No

No

Is_Dynamic_SQL_leveraged

Yes

Yes

Is_DB_Trustworthy_Enabled

No

No

Is_forced_parameterization_leveraged

No

No

is_db_chaining_leveraged

No

No

Is_Encryption_leveraged

No

No

Is_Object_Level_Encrytion_leveraged

No

No

Is_Replication_leveraged

No

No

Is_Service_Broker_leveraged

No

No

Is_TDE_Encryption_leveraged

No

No

Is_Full_Text_leveraged

No

No

Is_FileStream_Leveraged

No

No

1 This parameter is used to determine whether the application stores its logs on the application server or in the database.

Related topics

Configuring databases for Windows 
Configuring databases for Linux

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*