CONCEPT: Policy Wildcards

Various settings within the RockSolid policy framework allow you to use wildcards within the fields.  This allows you to specify settings at a group level for which the wildcard is replaced with actual values from the instance or database when that filed is later used by the RockSolid software.

EXAMPLE: In a group policy (which affects multiple instances) you may want to specify the SQL Server Instance error log directory as the working directory for RockSolid to store temporary trace files.  Each instance may have a different path for this folder however using the {$ErrorLogPath$} wildcard you can make the configuration setting change and on use of the field RockSolid will replace the wildcard with the correct value for each instance.

RockSolid policy wildcards

The following wildcards can be used within RockSolid:

Wildcard Level Description
{$InstanceName$} Instance The name of the SQL Server instance including the server name and the instance name components
{$ServerName$} Instance The server name component of the SQL Server instance name only.  Excludes any named instance component.
{$NamedInstance$} Instance The named instance component of the SQL Server instance name only.  Excludes any server name component.
{$MajorBuild$} Instance The major build number of the SQL Server instance in numeric format.
{$ErrorLogPath$} Instance The current path to the SQL Server error log files for the instance.
{$BackupPath$} Instance The current path to the default SQL Server backup path for the instance.
{$SQLBinaryPath$} Instance The path to the SQL Server binary installation files for the instance.
{$DefaultDataPath$} Instance The current default data file path for new databases, for the current instance.
{$DefaultLogPath$} Instance The current default log file path for new databases, for the current instance.
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.