Go Up
You are here: DeploymentDeployment PlanningSQL Server and Audit DatabaseSQL Server Placement

SQL Server Placement

When planning for SQL Server that will host Netwrix databases, consider the following:

  • Both standalone servers and SQL Server clusters are supported, as well as AlwaysOn Availability Groups.
  • For PoC, evaluation scenario or small environment SQL Server can run on the same computer where Netwrix Auditor Server will be installed, or on the remote machine accessible by Netwrix Auditor. Remember to check connection settings and access rights.
  • For large and extra-large environments – SQL Server should be installed on a separate server or cluster; installation of Netwrix Auditor and SQL Server on the same server is not recommended in such environments.
  • You can configure Netwrix Auditor to use an existing SQL Server instance, or deploy a new instance. If setting up a new instance, you will need to provide the path for storing the SQL databases — it is recommended that you specify the data drive for that purpose (by default, system drive is used).
  • You will also need to add the user accounts who will be assigned the sysadmin role. Add the following accounts:
    1. Configure Data Collecting Account
    2. The account currently logged in
    3. Local administrator of the machine

  • If you plan to have Netwrix Auditor and SQL Server running on different machines, then you should establish fast and reliable connection between them (100 Gbps or higher).
  • If you plan to have more than one Netwrix Auditor Servers in your network, make sure to configure them to use different SQL Server instances. The same SQL Server instance cannot be used to store audit data collected by several Netwrix Auditor Servers.

See also Requirements for SQL Server to Store Audit Data

Go Up