Restricted Enterprise edition features 2005
Job details
| Name: | Restricted Enterprise edition features 2005 |
| 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.1 |
| 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 the usage of features that are restricted to Enterprise or Developer editions of SQL Server 2005, ensuring compliance and optimizing SQL Server edition deployment.
- Why: This job is important to ensure that no unauthorized or accidental use of restricted features occurs in non-Enterprise or Developer SQL Server environments. Use of such features can lead to potential licensing issues or functionality limitations if not adhered to the correct server editions.
- Manual checking: You can check this manually in the database by executing the following SQL command:
select * from dbw_restricted_features_tabImplementation Details
The SQL procedure involved in this job checks if the SQL Server edition is either Enterprise or Developer. It then iterates through each database, looking for specific features (VarDecimal storage and Partitioning) that are exclusive to these editions. It executes dynamic SQL commands specifically tailored to each database to check the usage of these features and consolidates this data into a table named “dbw_restricted_features_tab”.
Dependency
- This task depends on itself for some operational logic and also uses an auxiliary table “dbw_restricted_features_tab” to store the results.
- Dependency on data correctness and continuity ensures that any failure in the execution leads to cleaning up for maintaining data integrity.
Job Execution Schedule
The default schedule set for this job is to run every day at 6:06 AM, which helps in daily monitoring of restricted feature usage across all checked databases.
Tables and Outputs
This job generates a report which includes:
| Database Name | Feature In Use | Count of Feature Usage |
|---|---|---|
| db_name | feature_name | feature_count |
This table lists all databases where restricted Enterprise edition features are in use, which is crucial for audit and compliance purposes.
Conclusion
The “Restricted Enterprise Edition Features 2005″ job is vital for organizations relying on SQL Server to ensure they are operating within the licensing agreements and utilizing the SQL Server capabilities efficiently across the right editions. This monitoring helps prevent potential legal issues from unauthorized use of restricted features and assists in the appropriate management of SQL Server resources.