Date: Thu, 28 Mar 2024 17:20:42 +0000 (UTC) Message-ID: <1024000046.68609.1711646442862@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_68608_1731880019.1711646442860" ------=_Part_68608_1731880019.1711646442860 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Registering a SQL Server instance allows you to audit this insta= nce and the associated databases. For each database you want to audit, regi= ster the corresponding SQL Server instance. When you register the instance,= you can also deploy the SQL Compliance Manager Agent to begin auditing SQL= events on this instance.
Indicate whether you want to deploy the SQL Compliance Manager Agent= now or later, and then click Next. You can also choose to= deploy the SQL Compliance Manager Agent manually, allowing you to install = the agent at the physical computer that is hosting the registered SQL Serve= r instance.
If you are auditing a virtual SQL Server or a SQL Server in= stance running in a non-trusted domain or workgroup , you mus= t manually deploy the SQLcompliance Agent to the computer hosting the insta= nce. For more information, see Deploy the SQL Compliance Manager Agent manually= a>.
C:\Program Files\Idera\SQLcomplian=
ce\AgentTraceFiles
You can use the command line interface to register a new SQL Server= instance and apply audit settings. The audit settings can be configured us= ing the Typical auditing settings or an audit template (audit settings you = exported to an XML file).
Keep in mind the following requirements and limitations:
register
command supports case-sensitive named instanc=
es. Ensure you are using the appropriate case when you cite the instance na=
me.registerinstance
command does not support registering =
a virtual SQL Server instance hosted on a Windows cluster.SQL Compliance Manager includes a sample instance audit settings templat=
e (Sample_Server_AuditSettings.xml) for your convenience. Use this sam=
ple template to familiarize yourself with how specific audit settings are d=
efined. By default, the sample template is located under C:\Program F=
iles\Idera\SQLcompliance
.
SQLcmCmd [-h=
ost CollectionServer] [-port number] registerinstance instance
.The FERPA regulation guideline is provided as an XML template (FER=
PA_Server_Regulation_Guideline.xml
) stored in the SQL Complianc=
e Manager installation directory (C:\Program Files\Idera\SQLcomplianc=
e
). Ensure the path you cite for the FERPA template reflects the dir=
ectory you chose during installation.
SQLcmCmd [-h=
ost CollectionServer] [-port number] registerinstance instance -config "FER=
PA regulation guideline file path"
.The SOX regulation guideline is provided as an XML template (SOX_S=
erver_Regulation_Guideline.xml
) stored in the SQL Compliance Ma=
nager installation directory (C:\Program Files\Idera\SQLcompliance). Ensure the path you cite for the SOX template reflects the directory=
you chose during installation.
SQLcmCmd [-h=
ost CollectionServer] [-port number] registerinstance instance -config "SOX=
regulation guideline file path"
.SQLcmCmd [-h=
ost CollectionServer] [-port number] registerinstance instance -config "exp=
orted audit settings file path"
.SQL Compliance Ma=
nager audits all acti=
vity on your server. Learn more >=
; >
IDERA Website | Product= s | Buy | Support&= nbsp;| Community | About Us&n= bsp;| Resources | Legal