Enterprise 11 database requirements

For Oracle Database, one instance of the database with two separate schemas of the same database are required. For Microsoft SQL Server, two databases on the same instance of the database server are required. View the list of supported databases, database server type, version, hardware, and operating system requirements, and database backup and recovery requirements.

Automation Anywhere databases

Automation Anywhere installation creates databases to store bot data and metadata for the analytics dashboards.

  • Database for Control Room
  • Databases for Bot Insight and Bot Insight metadata
Note: Automation Anywhere does not provide any monitoring functions for database activities, such as disk space usage, memory, or other alert mechanisms related to databases. There are commercial tools available from database vendors and other third-party independent software vendors (ISV) who provide such tools.

For all Custom installations: As of Version 11.3.4, have a user, with the minimum database permissions, create the databases before you install. See Enterprise 11 credential requirements for the database permissions required.

Database for component Default database name
Control Room CRDB-NEW
Bot Insight BotInsight
Bot Insight metadata BIVisualization


Note: You can rename the CRDB-NEW and BotInsight database names. The name provided for the BIVizualization database during installation will be used as a prefix for -Scheduler database. Therefore, do not change the suffix part in -Scheduler database. The BIVizualization and the BIVisualization-scheduler databases will be created during the Control Room installation.

Starting from Automation Anywhere Control Room release 11.3.5, the BIVisualization-keyset and BIVisualization-upload databases are integrated with the Bot Insight services.

If you are upgrading from a previous version of Automation Anywhere Control Room, the following databases will be available:
  • BIVisualization
  • BIVisualization-scheduler
  • BIVisualization-keyset
  • BIVisualization-upload

Database server hardware requirements

Component server Processor RAM Storage Network
Microsoft SQL Server database 4-core Intel Xeon Processor 8 GB 500 GB 1 GbE
PostgreSQL Server database 2-core Intel Xeon Processor 4 GB 10 GB 1 GbE
Oracle Server database(1) 8-core Intel Xeon Processor 32 GB 500 GB 1 GbE
Note: If you are hosting Control Roomdatabases along with other application databases, ensure the hardware resources are increased proportionately.
Note 1
For Oracle databases, do not use containers or pluggable databases.

Database server version and operating system requirements

One of either a Microsoft SQL Server database or Oracle Database is required.

Database type Database version Database Edition Installed database OS Configuration requirement
Microsoft SQL Server database



2014 SPI

2014 SP3



For Microsoft Azure installations, use version 2014, 12.0.2000.8 (RTM) or later

Standard, Enterprise and Express

Windows Server 2008 R2 Standard or later Installed and configured.

Only option for Express installations

Enable protocols for Named Pipes and TCP/IP.

See Enterprise 11: Working with SQL Servers.

Oracle Database (1)

Standard and Enterprise

Server 2016 Datacenter Installed and configured.

Only allowed with Custom Installations and for non-container database.

When you install Control Room with Oracle Database ,PostgreSQL Server is required to support Bot Insight metadata databases.

Install JDBC driver on Control Room server.

Create users for Automation Anywhere to access the database.

PostgreSQL Server database 9.5.19 - Windows Server 2008 R2 Standard or later, Red Hat Enterprise Linux, or Ubuntu LTS

Optionally installed with Control Room. Supports metadata related to analytics dashboards only.

Configure PostgreSQL Server as PaaS and enable SSL.

For Microsoft Azure installations, disable SSL.

  • We recommend Enterprise or Standard editions of Microsoft SQL Server database for production use and to ensure business continuity with HA and DR deployments. You can configure the Express edition of Microsoft SQL Server for Automation Anywhere Enterprise testing and proof of concept (POC) purposes.
  • (1): Oracle Database that is hosted on a Linux server is also supported.
  • When you access the Operations Manager dashboard (Dashboard > Workload), no data is displayed. A warning message is displayed, which you can close.

Database backup and recovery requirements and schedules

Database action Requirement
Backup database process
  • Follow your standard best practices.
  • Verify that your database backups and file system backups are in sync.

    Backups are used to maintain consistency between the database and the file system. Database backups are used in recovery processes.

Backup maintenance schedule
  • Weekly: Full database backup.
  • Every 3 days: Differential backups.
  • Daily: Incremental backups every 24 hours.
  • Hourly: Transaction log backup every hour.
Backup installation and configuration files Files are listed in Automation Anywhere configuration and properties files. This includes:
  • Bot Creator schedules configuration files
  • AutoLogin configuration files
  • Enterprise Client configurations files
  • Database configuration files
Configure Microsoft SQL Server database

Required database information for Automation Anywhere installation

When you install Automation Anywhere, you are prompted to provide information specific to the database type you are using. See Enterprise 11: Configure database type and server. The following table summarizes the required information.

Microsoft SQL Server database
Required information Description
Database (SQL Server) authentication Provide credentials for a Microsoft SQL Server user who has permission to connect to the database.
Database names Ensure the database names for Control Room and Bot Insight are the same with Microsoft Azure installations.

Database names cannot be blank, have spaces, or include a % (percent character). Restrict the names to alphanumeric, period (.), dash (-), and underscore (_).

Database port Default: 1433

Dynamic ports are not supported.

Secure connection (optional) and certificate Provide a CA certificate. Ensure the certificate host name and database connection are the same. See Enterprise 11: Import HTTPS and CA certificates.
Service credentials Provide Local system account user or Domain user account. This becomes the assigned user for the created databases and tables. The preferred method is to use the Domain user account.
Windows authentication User-provided (or default) used to connect to the Microsoft SQL Server, test database exists, create database if not present, and set db_owner to the service account user.
Oracle database
Required information Description
Bot Insight database instance name Created when database was created.
Bot Insight database instance credentials

Username and password.

Database port Default 1521.
Database server Provide Oracle Database server host name details, including IP address and user credentials.
Control Room database instance name Created when database was created.
Control Room database user credentials

Username and password.

Secure connection (optional) and certificate Provide a CA certificate. Ensure the certificate host name and database connection are the same. See Enterprise 11: Import HTTPS and CA certificates.
User permissions for databases vary depending on the installation mode, the Automation Anywhere Enterprise version and the database server.
Database user condition Database required permission Notes
Custom,Version 11.3.4 or later, Microsoft SQL Server database Can have the minimum database permissions: datareader, datawriter and ddladmin. Microsoft SQL Server database must be created before Control Room installation.
Custom, Version 11.3.4 or later, Oracle Database Can have the minimum database permissions: GRANT CONNECT, RESOURCE, CREATE TABLE, CREATE VIEW Oracle Database database must be created before Control Room installation.
Custom, older than Version 11.3.4 Database Owner (DBO) permissions. Databases created during Control Room installation.
Note: The user permission for databases that is set during Control Room installation remains the same after installation.