The principles for tuning restores are exactly the same as those for tuning backups. We have chosen, therefore, not to duplicate tuning documentation for both backup and restore. Refer to the sections “About: Dynamic Backup Tuning Thresholds” and “How to: Set up dynamic backup tuning thresholds”.
Name | Type | Description |
ID | bigint | Primary key row identifier. |
ServerName | varchar | Name of the remote server. Valid inputs: <specific server name> MinionDefault |
DBName | sysname | Database name Valid inputs: <specific database name> MinionDefault |
RestoreType | varchar | Restore type. Valid inputs: Full Diff Log All |
SpaceType | varchar | The way in Minion Backup determines the size of the database (e.g., data only, data and index, etc.) Valid inputs: DataAndIndex Data File |
ThresholdMeasure | char | The measure for our threshold value. Valid inputs: GB |
ThresholdValue | bigint | The correlating value to ThresholdMeasure. So, if ThresholdMeasure is GB, then ThresholdValue is the value – the number of gigabytes. |
Buffercount | smallint | From MSDN.Microsoft.com: “Specifies the total number of I/O buffers to be used for the backup operation. You can specify any positive integer; however, large numbers of buffers might cause "out of memory" errors because of inadequate virtual address space in the Sqlservr.exe process.” |
MaxTransferSize | bigint | Max transfer size, as specified in bytes. This must be a multiple of 64KB. Note that a value of 0 will allow Minion Backup to use the SQL Server default value, typically 1MB. From MSDN.Microsoft.com: “Specifies the largest unit of transfer in bytes to be used between SQL Server and the backup media. The possible values are multiples of 65536 bytes (64 KB) ranging up to 4194304 bytes (4 MB).” |
BlockSize | bigint | From MSDN.Microsoft.com: “Specifies the physical block size, in bytes. The supported sizes are 512, 1024, 2048, 4096, 8192, 16384, 32768, and 65536 (64 KB) bytes. The default is 65536 for tape devices and 512 otherwise. Typically, this option is unnecessary because BACKUP automatically selects a block size that is appropriate to the device. Explicitly stating a block size overrides the automatic selection of block size.” |
Replace | bit | Whether to enable the WITH REPLACE restore option. |
WithFlags | varchar | Additional WITH flags. You can use any of the standard RESTORE statement WITH options, using a comma-delimited list. Note that log backup restores are automatically restored with NORECOVERY. Example: NORECOVERY |
BeginTime | varchar | The start time at which this threshold applies. IMPORTANT: Must be in the format hh:mm:ss, or hh:mm:ss:mmm (where mmm is milliseconds), on a 24 hour clock. This means that both ’00:00:00’ and ’08:15:00:000’ are valid times, but ‘8:15:00:000’ is not (because single digit hours must have a leading 0). |
EndTime | varchar | The end time at which this threshold applies. IMPORTANT: Must be in the format hh:mm:ss, or hh:mm:ss:mmm (where mmm is milliseconds), on a 24 hour clock. This means that both ’00:00:00’ and ’08:15:00:000’ are valid times, but ‘8:15:00:000’ is not (because single digit hours must have a leading 0). |
DayOfWeek | varchar | The day or days to which the settings apply. Valid inputs: Weekday Weekend [an individual day, e.g., Sunday] |
IsActive | bit | Whether 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. |