You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

You can easily and quickly install IDERA SQL Secure on any computer that meets or exceeds the following hardware, software, and permission requirements. Before installing SQL Secure, also review the product components and architecture as well as how the product works.

Typical requirements

A typical install sets up all SQL Secure components on the same computer. The following table lists the requirements for a typical installation.

Hardware/softwareRequirement
CPU2.0 GHz or higher
Memory2 GB
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
  • Windows Server 2019

Plus:

  • .NET Framework 4.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 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
  • 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 11.0+
  • Google Chrome
  • Mozilla Firefox
  • Microsoft Edge
  • Safari

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/softwareRequirement
CPU2.0 GHz or higher
Memory2 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:

  • .NET Framework 4.6
Browser for online HelpInternet Explorer 9.0 or later

SQL Server Versions and Editions

SQL Secure monitors different SQL Server versions intalled on-premise or on cloud platforms.

SQL Versions Windows OnlyOn-PremiseAzure VMAzure SQL DatabaseAWS EC2AWS RDS
2000X



2005XX


2008 R2XX
XX
2012 SP1XX
XX
2016XX
XX
2017XX
XX
2019XX
XX
Azure SQL Database V12

X

Cloud 

SQL Secure runs on various Cloud Virtual Machines running Microsoft Windows Server and Microsoft SQL Server.

The following table shows all services that SQL Secure can work with, depending on the could service delivery model and the cloud provider:

Cloud Service Delivery ModelIaaSPaaS (DBaaS)
Amazon Web Services

Amazon Elastic Compute Cloud (EC2)

  • Windows Server
  • SQL Server

Amazon Relational Database Service (RDS)

  • Windows Server
  • SQL Server
Microsoft Azure

Azure Virtual Machines

  • Windows Server
  • SQL Server
Azure SQL Database
Google Cloud Platform

Google Compute Engine

  • Windows Server
-

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.

TypeRequirement
Windows permissionsA Windows user account that has local administrator permissions.
SQL Server privilegesA 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 Article 832017 on the Microsoft Support site. To better understand how port assignments work when Windows Firewall has been configured, see "Connecting through Windows Firewall" on the MSDN site.

TypeRequirement
SQL Server Object Permissions and configuration collectionPort 1433 (or the configured SQL instance port for the audited instance)
Windows file system and registry permissions collectionPort 135 (RPC connectivity)

IDERA | Products | Purchase | Support | Community | Resources | About Us | Legal
  • No labels