Date: Fri, 29 Mar 2024 08:36:03 +0000 (UTC) Message-ID: <1276351230.69799.1711701363169@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_69798_139037414.1711701363169" ------=_Part_69798_139037414.1711701363169 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 SQLcompliance Agent to begin auditing SQL events o= n this instance.
Indicate whether you want to deploy the SQLcompliance Agent now or l= ater, and then click Next. You can also choose to deploy t= he SQLcompliance Agent manually, allowing you to install the agent at the p= hysical computer that is hosting the registered SQL Server instance.
If you are auditing a virtual SQL Server or a SQL Server in= stance running in a non-trusted domain or workgroup, you must= manually deploy the SQLcompliance Agent to the computer hosting the instan= ce. For more information, see Deploy the SQLcompliance Agent manually.
C:\Program Files\Idera\SQLcompliance\AgentT=
raceFiles
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
.
To register an instance and apply the Typical (default) audit se= ttings:
SQLcmCmd [-h=
ost CollectionServer] [-port number] registerinstance instance
.To register an instance and apply a FERPA regulation guideline:<= /strong>
The FERPA regulation guideline is provided as an XML template (FER=
PA_Server_Regulation_Guideline.xml
) stored in the SQL CM instal=
lation directory (C:\Program Files\Idera\SQLcompliance
). Ensur=
e the path you cite for the FERPA template reflects the directory you chose=
during installation.
SQLcmCmd [-h=
ost CollectionServer] [-port number] registerinstance instance -config "FER=
PA regulation guideline file path"
.To register an instance and apply a SOX regulation guideline:
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"
.To register an instance and apply a custom audit template:
SQLcmCmd [-h=
ost CollectionServer] [-port number] registerinstance instance -config "exp=
orted audit settings file path"
.