RELEASE: This document describes changes and enhancements made to ApexSQL Enforce Best viewed with 'WORD WRAP' unchecked -------------------------------------------------------------------------------------------------- RELEASE 2008.02.0012 DATE: March 10, 2008 DESCRIPTION: Minor Fix Release -------------------------------------------------------------------------------------------------- Fixes: - Screen refresh issue on the Create a New Rulebase dialog - Invalidated CLI switches displaying only warnings instead of stopping the execution - Crash on specifying non-existent folder in Open Trace Log - Databases from last used server being shown although unavailable - Flickering when repositioning dialogs - Inability to generate HTML reports and XML exports from CLI - "Login failed for user (null)" issue on FixSQL script generation with SQL Authentication selected - SQL 2005 max types being incorrectly defined - Status bar showing incorrect info for rules count in some cases - Stored procedures being prefixed with database name in results grid - Keyboard context menu call not working in Rulebase Explorer - Incomplete table bottom border in HTML Report - English language grammar, spelling and semantics for both CLI and GUI - Added more helpful GUI and CLI messages in various places - Several disconnected and missing help file sections - Several dialog positions weren't remembered on close - Application icon missing in the Open Rulebase dialog - "..." missing on several menu items - Exception on modified SQL Server BackupDirectory registry key - Warning message after cancelling processing during the initial object counting phase - Menu and toolbar commands improperly categorized when customizing menus - Result Details panel Result tab controls inadequately resizing - Rule is marked as dirty during editing when opening category or severity forms - Wrong starting folder is shown in Open Rulebase in some cases - Open Rulebase closes rulebase grid filters even after cancelling the action - Exception in some cases during processing if server becomes unavailable - HTML report and CLI output type show incorrect database verdict in some cases of output scope filtering - HTML report and CLI output type display wrong summary values in some cases of output scope filtering - Bad total impact value in Details sections in HTML report for some cases of filtering items - Database / Server summary is empty in CLI output type in some cases of output scope filtering - Excess validation of HTML report options resulting in a warning message Changes: - Removed Summary and Detail options from the HTML Report dialog - Path is no longer shown abbreviated in Export Rules dialog - Made Suspended column in Result Summary to not look clickable - Last column in Result Summary renamed to "Reason for Suspension" - Empty sections are no longer shown in the HTML Report and CLI output type - Changed display mode for summary, statistics and details data in HTML Report - Changed to navy color for Show System Databases default option - Binary presentation is now used for scripting assemblies - Main status bar is now always showing total active and inactive rules and not just filtered count - When HTML and XML are generated using Checked Results Only option, only checked and filtered-in results are considered - Violation Statistics in HTML report now orders severity columns by their impact value - HTML report now shows author information from application options instead of rulebase properties - Suspended databases are automatically judged as failed disregarding the failure thresholds - CLI switch /output_scope (/os) now has three combinable argument values (Passed, Failed and Errors) Enhancements: - DML triggers are prefixed with table name in results grid - Export Rules dialog can be closed by pressing Esc key - Sub-objects display parent object's schema in Owner/Schema resultset column - Added "Refresh Metadata" option as a checkbox to Select Databases dialog - Added "Include Rules" option as a checkbox when basing a new rulebase on an existing one - CLI now has a range of success and failure return codes -------------------------------------------------------------------------------------------------- RELEASE 2005.01.0011 DATE: February 5, 2008 DESCRIPTION: Release --------------------------------------------------------------------------------------------------