ApexSQL's Best Practices Rulebase is a collection of more than 60 generally accepted Industry Best Practice rules for SQL server. These rules are written and tested by ApexSQL enabling end users to simply load and run them. All rules can be edited, ignored, and even deleted allowing you to fully customize the rulebase.

The ApexSQL Enforce Online Law library is a great resource allowing you to download updated versions of ApexSQL Rulebases as well as rulebases posted by others.

Users can browse, view, and download rulebase code or discuss them on the forum.

The Rulebase Explorer is a powerful tool to allow users to quickly browse and edit rulebases.

ApexSQL Enforce includes a powerful, internal Editor for writing Rule conditions that features IntelliPrompt, compilation, and standard word processing features.

The results are presented in a feature-rich grid allowing for multi-column grouping and sorting and column level filters. Severity, Result (pass or fail), and Object Type can all be viewed via icons.

Rules can easily be exported and imported into existing rulebases.

Each rule can contain a customizable "FixSQL" script which can be run to fix the detected violation. FixSQL scripts can be combined in a single SQL script which, when executed, will fix all rulebase violations.

After a rulebase has been processed, a detailed report can be produced quickly and shared among peers. The generated report shows a full inventory of the results, from database level pass/failure status down to individual object-level violations.

ApexSQL Enforce implements a powerful trace logging mechanism by default. It can also be customized to display your own user-defined messages. This helps isolate issues encountered during rulebase processing, debugging, etc.

ApexSQL Enforce has a powerful command line interface that supports a variety of option switches. All GUI Project wizard configurations can be performed via command line interface. This is helpful for scheduled batch runs and large database documenting.

ApexSQL Enforce allows users to customize the threshold at which a Database will be considered to have failed at the individual Rulebase level. Processing can be suspended based on additional criteria to avoid unneccessary processing after a database has already failed or exceeded some other extreme threshold.

Users have full control over rule severities including creating new Severities as well as editing them, changing impact score & description, and even selecting an icon from our large library of Severity icons.