SQL Server requirements

Explore supported high availability (HA) options for SQL Server in 1E 9.x, including AlwaysOn Availability Groups and Failover Cluster Instances. Learn setup, upgrade, and configuration best practices to ensure database resilience and minimize downtime in enterprise environments.

Local or remote SQL Server

You will need to decide if 1E databases are installed locally or on remote SQL Server instance(s). Databases that are remote from their 1E Servers increase the complexity of design and installation in the following ways:

• 1E Server installation depends on the server installation account having appropriate rights on the SQL Server instance. Remote SQL Servers are typically run on farms managed by other teams who may not want to grant permissions to your installation account.

• If a Response Stack serves over 500 devices then you will require an additional network interface, which requires network routing, refer to Network interfaces.

Microsoft SQL Server Express is not supported for either Master or Responses databases, due to its limitations.

You will also require SQL Server Analysis Services if you are using Business Intelligence (as required by the Patch Success application).

Below is a list of SQL Server requirements covered in other sections on this page:

• SQL Server editions and configuration, refer to Server software:

  • SQL Server database instance is required for databases

  • SQL Server Analysis Server (SSAS) instance for the SLA-BI cube (required by Patch Success)

• Network interface for remote SQL Server, refer to Network interfaces

• SQL Login for the Network Service account

• SQL Logins for the server installation account

• Microsoft Bulk Copy Program (BCP) s installed on the Response Stack server(s) where the Tachyon Core component is installed, refer to Export all feature.

Refer to the Server sizing requirementsand High Availability options for SQL Server

Backup and recovery

You will need to regularly backup the following databases. The 1E server can be re-installed from scratch using the existing databases or a restored backup.

• 1E Catalog

• ContentDistribution (optional, required by Content Distribution)

• SLA-Data

• SLA-Shared

• SLA-Integrate

• SLA-BI (optional, required for Patch Success)

• TachyonMaster

• TachyonExperience (optional, required for Experience Analytics)

There is no requirement to backup the 1E Responses database because it only contains transient data. You can backup and restore the Responses database if that is your organization's preference for recovery.

For more detail about upgrading, refer to Upgrading 1E.

Export all feature

The Export all feature is available on the Endpoint Troubleshooting responses page, when an instruction has finished retrieving all its responses. To enable 1E users with the appropriate permissions to use this feature, you must ensure that the Microsoft Bulk Copy Program (BCP) is installed on the same Response Stack server(s) where the 1E Core component has been installed.

Refer to Configure 1E to support the Export all responses feature for more details on configuring SQL BCP and setting up a suitable share.