Database requirements
This topic describes the supported database versions and a few considerations for external databases.
- Supported databases
- Considerations during a fresh TrueSight Network Automation installation
- Oracle and SQL Server database requirements
Supported databases
The following databases are supported for use with the application server:
- Oracle Database 21c Innovation Release
- Oracle Database 19c (external database encryption)
- Oracle Database 18c (external database encryption)
- Oracle Database 12c RAC1 (external database encryption)
- Oracle Database 12c1 (external database encryption)
- Microsoft SQL Server 2022
- 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.6
- PostgreSQL 14.4
- PostgreSQL 14.1
- PostgreSQL 13.2
- PostgreSQL 12.6
PostgreSQL 10.22
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. To use the Embedded PostgreSQL database, you must install Microsoft Visual C++ 2015 (x64) (14.0.2xxxx version). For instructions on installation, see the Microsoft website.
- Disable database compression.
Oracle and SQL Server database requirements
The following table lists the parameters supported by Oracle and Microsoft SQL Server database servers:
Parameter | Supported by | Supported by |
---|---|---|
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.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*