In this version of MC, inline tokens are accepted for remote CheckDB operations. Specifically, the PreferredDBName and RemoteJobName in the Minion.CheckDBSettingsDB table:
UPDATE Minion.CheckDBSettingsDB SET PreferredDBName = '%Server%_%DBName%', RemoteJobName = 'MinionCheckDB_%Server%_%DBName%';MC recognizes %Server% and %DBName% as Inline Tokens, and refers to the Minion.DBMaintInlineTokens table for the definition. Note that custom tokens must be used with pipe delimiters, instead of percent signs: ‘|MyCustomToken|’.
For more information, see “About: Inline Tokens”.
Note that this table is shared between Minion modules.
| Name | Type | Description |
|---|---|---|
| ID | Int |
Primary key row identifier. |
| DynamicName | varchar |
The name of the dynamic part, e.g., “Date”.
We recommend you do not include any special symbols – only alphanumeric characters. |
| ParseMethod | varchar |
The definition of the dynamic part.
Typically, this is a TSQL expression that resolves to the value desired. For example, the ParseMethod for “Millisecond” is
DATEPART(MILLISECOND, @ExecutionDateTime)
Note: Custom inline tokens cannot use internal variables like @ExecutionDateTime; only SQL functions and @@ variables. |
| IsCustom | bit |
Whether this is a custom dynamic part, or one that came with the product originally. |
| Definition | varchar |
This is the official description of the dynamic part.
Example (BackupTypeExtension): “Returns a dynamic backup file extension based on the backup type.”
Note that certain built-in token definitions are hard coded in the procedure; entries here are simply a placeholder. So, do not modify or disable definitions. |
| IsActive | bit |
The current row is valid (active), and should be used in the Minion Backup process. |
| Comment | varchar |
For your reference only. You can label each row with a short description and/or purpose. |