SQL Server Pre-Installation Notes

Security Controls will store all scan and patch deployment results in an SQL Server database. The SQL Server backend enables real-time collaboration and knowledge management amongst all individuals responsible for performing patch management tasks. Some of the benefits to using the SQL Server database include:

  • High performance when scanning either a handful of machines or many machines
  • Storage of data on a remote machine
  • Ability for multiple Security Controls consoles to share templates, comments, reports, and scan results

What You Need to Know About SQL Server Before Installing Security Controls

Before installing Security Controls, please review the following SQL Server notes:

  • Microsoft SQL Server is required.
    If you do not have SQL Server, the option to install Microsoft SQL Server Express Edition will be provided during the Security Controls installation process.
  • The SQL Server Database Engine feature must be installed. No other SQL Server features are required.
  • If you will be using an Express Edition of Microsoft SQL Server, you should consider downloading and installing Microsoft SQL Server Management Studio Express. This free software can be used to perform backups and to manage your database.
  • Installation of SQL Express may fail if you have a SQL Native Client previously installed. It is strongly recommended you uninstall SQL Native Client using Add or Remove Programs before running the installation program.
  • You must have access to the specified SQL Server. The program will support either Windows authentication or SQL Server authentication to access the specified SQL server. Although administrative access is not required, this account does need permissions to create and populate the product database on the specified SQL Server. In addition, the Security Controls console machine background services must be able to access the SQL Server. All background services run using the LocalSystem account on the console. If you are using Integrated Windows Authentication on a remote server, be sure to use the machine account when defining the console login account on SQL Server.
  • For security purposes, Ivanti recommends using Windows authentication where possible. For information on configuring a remote SQL Server to accept Windows authentication credentials from the Security Controls console, see SQL Server Post-Installation Notes.

  • In order to create the database, the user account you specify during the installation process must be assigned the dbcreator role.
  • If you are using SQL Server on a remote machine, you must configure the server to allow remote connections. This can be done using SQL Server Configuration Manager.
  • For information about configuring the database connection encryption, see Set Advanced options - database connection encryption.

  • If you want to use a clustered configuration for redundancy purposes it must be configured prior to installation. You then reference the virtual clustered instance during the installation process. Clustered configurations are not supported with SQL Server Express Editions.

Related Topics