Prior to configuring SQL Server instance maintenance periods, which can be performed before or after creating schedules, a SQL instance must be added.
For more information on adding SQL instances and creating schedules in ApexSQL Manage refer to the following articles:
To configure a maintenance period, go to the Inventory tab in the main ribbon, check the desired SQL instance from the shown grid, and click the Maintenance button.
This will open the Configure maintenance period window where the maintenance plan can be configured:
Several options of the SQL Server instance maintenance period can be configured, and they serve to address specific operations from the tool:
For the purpose of this article, a maintenance period with the following parameters will be configured:
Click the OK button to save the configuration of the maintenance period to the above-mentioned parameters:
The maintenance period for the checked SQL instance is now configured and visible in the column labeled Maintenance in the main grid of the Inventory tab:
Now, when running a Health check, Comparison, Snapshot, or Documentation schedule from the Schedules tab of the main ribbon, the results will vary depending on the maintenance period configuration.
The health check schedule of the previously configured SQL instance will be successful while Snapshot, Documentation, and Comparison schedules will show Skipped in the column labeled Last result. Hovering the cursor over the results will show a tooltip message stating that the job was skipped because the related server instance(s) are in the maintenance period:
To summarize, the main benefits of configuring maintenance periods in ApexSQL Manage are:
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center