SessionAudit
  • Infrastructure Documents
  • Overview
    • What is Session Audit
    • FAQs
    • Road Map
    • Licensing
  • Planning
    • POC Requirements
    • Supported Configurations
    • Windows Server Requirements
    • SQL Server Requirements
    • Agent Requirements
    • Other Requirements
    • Network Considerations
    • Design
      • Single Deployment
      • Distributed Deployment
  • Deployment
    • Installing Microsoft SQL Server
    • HTTPS Certificate
    • DNS Records
    • .Net Framework 4.7.2 Download and Install
    • .NET Core 6.0.16 Download and Install
    • Internet Information Service Installation
    • Single Deployment
      • DB Creation
      • IIS and Site Settings
      • Database Permissions
    • Distributed Deployment
    • Upgrade Existing SessionAudit Installation
  • Initial Configuration
    • First time Login to SessionAudit
    • License Management
    • LDAP Settings
    • Role Management
    • Change Admin Password
  • Advanced Configuration
    • Login to the Portal with Domain Account
    • Settings
      • Server Settings
      • Agent Settings
      • LDAP Settings
      • Notification Settings
      • Syslog Settings
  • Managing
    • Dashboard (Home)
    • Tracker
    • Reporting
    • Computers
    • Role Management
    • License Management
  • Troubleshooting
    • SQL Express Usage
    • Securing Windows Server
Powered by GitBook
On this page
  • Supported versions of SQL Server
  • SQL Server architecture version
  • Database collation
  • Database compatibility level
  • Permissions

Was this helpful?

  1. Planning

SQL Server Requirements

Scope: SessionAudit 1.0

SessionAudit environment requires a supported SQL Server version and configuration to host the SessionAudit database.

SQL Server can be located on:

  • SessionAudit server computer,

  • A computer that is remote from the site server.

The following instances are supported:

  • The default or named instance of SQL Server,

  • A SQL Server Always On failover cluster instance,

  • A SQL Server Always On Availability Group.

Supported versions of SQL Server

In a hierarchy, all SessionAudit servers access the same SQL Server database:

  • The SQL Server versions you use remain in support by Microsoft.

  • For SQL Server 2016 and prior, support for each SQL Server version and service pack follows the Microsoft Lifecycle Policy. Support for a specific SQL Server service pack includes cumulative updates unless they break backward compatibility to the base service pack version

SQL Server 2019: Standard, Enterprise or Express. You can use this version with cumulative update 5 (CU5) or later, as long as your cumulative update version is supported by the SQL Server lifecycle. CU5 is the minimum requirement for SQL Server 2019 as it resolves an issue with scalar UDF inlining.

SQL Server 2017: Standard, Enterprise or Express. You can use this version with cumulative update version 2 or higher, as long as your cumulative update version is supported by the SQL Server lifecycle.

SQL Server 2016: Standard, Enterprise or Express. You can use this version with the minimum service pack and cumulative update supported by the SQL Server lifecycle.

SQL Server 2014: Standard, Enterprise or Express. You can use this version with the minimum service pack and cumulative update supported by the SQL Server lifecycle.

SQL Server architecture version

Configuration Manager requires a 64-bit version of SQL Server to host the site database.

Database collation

SQL Server that's used for the database must use the following collation: SQL_Latin1_General_CP1_CI_AS.

Database compatibility level

The following table identifies the recommended compatibility levels for Configuration Manager site databases:

SQL Server version
Supported compatibility levels
Recommended level

SQL Server 2014

120, 110

110

SQL Server 2016

130, 120, 110

SQL Server 2017

140, 130, 120, 110

SQL Server 2019

150, 140, 130, 120, 110

150

Permissions

During the installation of SessionAudit, the user account that will perform the database operations needs the sysadmin role to create a database and make basic settings. After the installation is finished, the dbOwner role is necessary and sufficient for service accounts and SessionAudit administrators.

PreviousWindows Server RequirementsNextAgent Requirements

Last updated 2 years ago

Was this helpful?