...
A typical install sets up all SQL Secure components on the same computer. The following table lists the requirements for a typical installation.
| Hardware/software | Requirement |
|---|
| CPU | 2.0 GHz or higher |
| Memory | 2 GB |
| 32-bit or 64-bit Operating System | |
8.1Windows - 10
- Windows Server 2008 SP2
- Windows Server 2008 R2 SP1
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
Plus: |
6 - 5 SP1 or later
- MDAC 2.8 or later
|
| Microsoft SQL Server for Repository | Supports all editions except SQL Server Express for the following versions: - SQL Server 2008 SP1
- SQL Server 2008 R2
- SQL Server 2012 SP1
- SQL Server 2014
- SQL Server 2016
- SQL Server 2017
- SQL Server 2019
- SQL Server on Azure VM
- SQL Server on Amazon EC2
|
| Microsoft SQL Server for audited instances | |
2000SQL Server 2005SQL Server - 2008 SP1
- SQL Server 2008 R2
- SQL Server 2012 SP1
- SQL Server 2014
- SQL Server 2016
- SQL Server 2017
- SQL Server 2019
- Azure SQL Database
- SQL Server on Azure VM
- SQL Server on Amazon EC2
- Amazon RDS for SQL Server
|
| Browser for online Help | - Internet Explorer 9.0+
- Google Chrome
- Mozilla Firefox
|
Console requirements
A console-only installation installs the SQL Secure Console. The console-only installation assumes that a full installation has already been completed on another machine. The following table lists all the requirements for a console-only installation.
| Hardware/software | Requirement |
|---|
| CPU | 2.0 GHz or higher |
| Memory | 2 GB |
| 32-bit or 64-bit Operating System | - Windows 8
- Windows 10
- Windows Server 2008 SP2+
- Windows Server 2008 R2
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
Plus: |
| Browser for online Help | Internet Explorer 9.0 or later |
SQL Server Versions and Editions
| SQL Versions Windows Only | On-Premise | Azure VM | Azure SQL Database | AWS EC2 | AWS RDS |
|---|
| 2000 | X |
|
|
|
|
| 2005 | X | X |
|
|
|
| 2008 SP1 | X | X |
| X |
|
| 2008 R2 | X | X |
| X | X |
| 2012 SP1 | X | X |
| X | X |
| 2016 | X | X |
| X | X |
| 2017 | X | X |
| X | X |
| 2019 | X | X |
| X | X |
| Azure SQL Database V12 |
|
| X |
|
|
Collector permission requirements
The following requirements are necessary for the SQL Secure Collector to access the SQL Server instances you want to audit. During install, you can input credentials for a Windows user account or SQL Server login.
| Type | Requirement |
|---|
| Windows permissions | A Windows user account that has local administrator permissions. |
| SQL Server privileges | A Windows user account that is a member of the sysadmin fixed server role on the SQL Server instance. |
Port requirements
SQL Secure uses the default ports opened by the Windows operating system for local and remote communications. To learn about Windows port assignments, see
| Newtab2 |
|---|
| alias | Article 832017 |
|---|
| url | http://support.microsoft.com/kb/832017/ |
|---|
|
on the Microsoft Support site. To better understand how port assignments work when Windows Firewall has been configured, see
| Newtab2 |
|---|
| alias | "Connecting through Windows Firewall" |
|---|
| url | http://msdn.microsoft.com/en-us/library/aa389286%28VS.85%29.aspx |
|---|
|
on the MSDN site.
| Type | Requirement |
|---|
| SQL Server Object Permissions and configuration collection | Port 1433 (or the configured SQL instance port for the audited instance) |
| Windows file system and registry permissions collection | Port 135 (RPC connectivity) |