Restricted Enterprise edition features
Job details
| Name: |
Restricted Enterprise edition features |
| Platform: |
Sqlserver |
| Category: |
Availability |
| Description: |
Checks if there are any restricted features in use (supported only by Enterprise or Developer SQL Server edition). |
| Long description: |
|
| Version: |
1.2 |
| Default schedule: |
0 6 6 * |
| Requires engine install: |
Yes |
| Compatibility tag: |
.[type=‘instance’ & databasetype=‘sqlserver’]/instance[maj_version > ‘2005′ & hasengine=‘YES’ & engine_edition = ‘Microsoft SQL Server’] |
Parameters
| Name |
Default value |
Description |
Job Summary
- Purpose: The purpose of this job is to monitor and report on the usage of SQL Server features that are restricted to the Enterprise or Developer editions.
- Why: This job is important as it helps ensure that SQL Server instances are compliant with licensing requirements by detecting any unauthorized use of premium features in editions that do not support them. If this threshold is breached, organizations could face legal and financial repercussions.
- Manual checking: You can check this manually in the database by issuing the following SQL commands:
SELECT * FROM dbw_restricted_features_tab
Implementation Details
- The XML defines a task named “Restricted Enterprise edition features” which scans SQL Server instances to find if they are utilizing any features that are exclusive to Enterprise or Developer editions.
- It includes SQL commands to create necessary tables and procedures that help in capturing and storing information about the restricted features being used. These comprise the:
- Detection of databases participating in SQL Server Always On availability groups and marking secondary replicas.
- Scanning of databases to detect and record the use of restricted features by creating and updating entries in ‘dbw_restricted_features_tab’.
Reporting
- The output of this monitoring job is formatted and displayed in a table, illustrating databases that use restricted features:
- Table headers include ‘db_name’, ‘feature_name’, and ‘feature_count’.
- This report helps in quickly identifying which databases need attention either for license review or feature usage adjustment.
Scheduling and Dependencies
- The job has a default schedule to run daily at 06:06 hours.
- Dependencies include self-contained procedures for data handling and updating tasks, ensuring data integrity and consistency during each run of the job.
- Automatic cleanup procedures are implemented in case of task failures to maintain system stability and to prevent corruption of data.
Upgrade Path
- Upgrades from version 1.1 are handled in a manner that ensures all previous data tables and procedures are properly aligned with the new task requirements.
- This involves alterations in stored procedures to refine data capture and enhance performance monitoring.
By leveraging this dbWatch Control Center job, administrators can effectively manage and audit SQL Server instances for compliance with licensing models, especially regarding high-value enterprise features, enhancing operational integrity and legal adherence.