ApexSQL Trigger release notes

Enhancements:

• SQL Server 2019 support

Changes:

• Software Transaction Agreement is added as a new step in the installation wizard and updated in accordance with https://www.quest.com/legal/sta.aspx

Fixes:

• "Sequence contains no matching element" error is encountered when the Apply button in the Standard report window is clicked
• Installation messages are displayed when the /VERYSILENT switch is used to install the application
• "Object reference not set to an instance of an object" error is encountered after a lookup is edited and the OK button is clicked in the Add lookup window
• Previously lookup values cannot be edited once the Test or OK button is clicked in the Add lookup window

Enhancements:

• SQL Server 2019 CTP 2.0 support

Fixes:

• "System.ArgumentOutOfRangeExceptio" error is encountered when editing a batch script template in the Automation script window
• The application crashes when the "%" symbol is entered in the batch script editor in the Automation script window

Changes:

• The application now requires Microsoft .NET framework 4.7.2

Enhancements:

• New error handling and send logs functionality
• Improved application installer with a dark theme
• New application icon
• Save automation script as a PowerShell script
• CLI switches:
  • Skip audited tables [/eat]
  • Exclude tables for auditing [/et]

Fixes:

• The application repeatedly asks for the activation key when it is started on an Amazon EC2 instance after the virtual machine resources were deallocated and allocated again
• Audited data cannot be deleted by specifying a condition in the Delete audited data dialog
• The application creates wrong script for purging audited data based on the specified condition
• Column pairs in the Watches tab cannot be deleted after auditing triggers are re-created
• The auditing report shows excessive records when the Watches feature is set in a way values from two columns needs to be shown in a report when a change occurs in one column
• The application creates a wrong script for purging all of the audited data
• Template dialog is empty after opening it for the second time in case there were previously unsaved changes
• "The path is not of a legal form." error is encountered when running the script from the template editor when it is empty

Changes:

• The "ApexSQL Trigger architecture.audx" file has been made read only to prevent accidental overwrite
• Save as batch is now Automation script

Fixes:

• "Object reference not set to an instance of an object" error is encountered when the Apply button under the Standard report tab is clicked on
• "ExecuteScalar requires an open and available Connection. The connection's current state is closed" error is encountered when display scaling is set to more than 100%

Enhancements:

• Support for SQL Server on Amazon RDS
• Support for SQL Server 2017 CTP 2.1

Fixes:

• Part of the DML trigger template script is hidden after using the horizontal scroll in the Template editor dialog
• Variables are not highlighted in the Template editor dialog
• "Input string was not in a correct format" error is encountered when the Start date in the Monthly section under the Schedule job dialog is later than the End date
• The Schedule job dialog does not load the previous Start date and End date values under the Daily frequency section

Enhancements:

• 'Select repository’ option added to the Advanced tab for storing the auditing architecture and data in a repository database separate from the audited database
• CLI switches:
  • Define a full path to save a SQL script file for creating triggers [/os]
  • Define paths to include multiple ApexSQL Trigger utility files [/iuf]
  • Display all return codes to the console [/rc]
  • Play sound upon finished operation [/be]
  • Logging level [/log] with four levels:
    • Errors
    • Warnings
    • All
    • None
• CLI error return codes:
  • Invalid switch [2]
  • Duplicate switch [3]
  • Incompatible switches [4]
  • Missing argument [5]
  • Missing a dependent switch [6]
  • Invalid value [7]
  • Value out of range [8]
  • Invalid file path [9]
  • Invalid project file [10]
  • Unsupported edition [11]
  • Invalid activation key [12]
  • Trial has expired [13]
  • Connection timeout [14]
  • Connection failed [15]
  • IO error [16]
  • Operation canceled [17]
  • Application error [18]
  • Execution error [19]
  • Execution timeout [20]
  • Insufficient permissions [21]

Fixes:

• CLI always returns error code 0 (success)
• The verbose [/v] and force [/f] switches are missing if the project is saved as a batch file, before being saved as a project file first
• The "Access to the path …\’ProjectName’.axap is denied" error is encountered when overwriting a project file in a location that requires administrator privileges
• Any part of the architecture file script cannot be commented out through the Template editor
• Incorrect SQL Server version is displayed in the status bar when connected to SQL Server 2016 (13.0)
• The Schedule Job window does not memorize the daily frequency Starting at and Ending at options values
• The “Object reference not set to an instance of an object” error is encountered and the application crashes when the Test button is clicked in the Lookups dialog if no columns are previously added to the lookup
• The Action filter in Standard, Aggregate and DDL reports does not work
• All tables will be automatically selected for auditing when the Check Columns button is clicked
• Read-only columns can be checked as Nullable in the Columns grid
• The Uncheck tables command unchecks all SQL tables except the already highlighted ones

Changes:

• The Standard report is renamed to Standard data change report
• The DDL report is renamed to Schema change report
• The Aggregate report is renamed to Aggregate data change report

Known issues:

• The syntax highlighting in the Template editor does not recognize VB code

Fixes:

• Fixed problem with auditing triggers created using a project file via CLI
• Fixed problem with inappropriate warning message when overwriting a project file

Enhancements:

• Users can now choose between 3 themes: white, colorful or dark
• Theme chooser is added in Options

Fixes:

• The selected row key column is not automatically selected in the Row key grid
• The notification section of the Template editor is not updated when a change is made
• Missing option to save results to output file
• The "Defaults" button in the application options does not revert the appropriate arguments to its default values
• Missing confirmation button in the "Results" dialog
• The grid in the "Row key" form isn't disabled when trying to uniquely identify the row in a table with the objects that are not custom row keys
• "Login failed for user 'sa'" error appears when trying to save SQL Agent job to delete audited data, even if the windows authentication is used to connect to SQL Server
• Canceling the process of creating the trigger script, when SQL Server Management Studio is selected as SQL editor closes the project file
• "Failed to create the trigger script" error is encountered when using the modified audx file that does not have the appropriate utils file in the same folder
• Missing informative message that the utils file should be in the same location where the .audx file is saved
• The "OK" button in the "Manage templates" form does not work
• The application will indicate that selected table is audited even the trigger creation script is executed with errors and triggers are not created
• Sort ascending/descending options in main grid context menu don’t work
• Both Identity field and Primary key textboxes are enabled in Edit key dialog
• "Cannot access a disposed object" error is encoutered when creating triggers
• The "Application error" occurs in the "Columns" tab when there are no columns for selecting and using options from popup menu
• The "Local" tab under the Servers tab does not shows local server, insted all servers are placed under the "Network" tab
• After setting the Lookup and clicking the name of the table in the conditions box the name will disappear
• The "Search" form has disabled cursor in the search field
• The CLI command in the "Save as batch" form is not correct

Enhancements:

• SQL Server 2016 support
• Azure SQL Database V12 support
• Save as batch file feature for auditing data in CLI

Fixes:

• The "Query timeout" text box in the Configuration tab under the Options form should not accept negative value
• Sorting in the header row in the main grid cannot be saved
• The "Application error" occurs in the "Columns" tab when there are no columns for selecting and using options from popup menu
• Columns in the "Manage data" form are not auto-sized
• The "Auto size" button does not work
• Fixed error when deleting created watch when two or more watch are in grid
• Error when deleting created lookup when two or more lookups are in grid
• The 'column doesn't exist' error is reported in case a column with multiple words is added for auditing via CLI
• The "application error" occur because of the negative value in the "Query timeout" text box in the Configuration tab under the Options form
• The application cannot work if the font size settings is set to 120% and more
• It is not possible to add different/single triggers via CLI
• It is not possible to save/update project via CLI
• It is not possible to remove and re-add triggers in the same command via CLI
• The “Changed” field in main grid will remain checked even the trigger is recreated after the schema change is detected
• Connection form closes when trying to connect with invalid credentials
• Copied content from the Script editor is pasted as double content using keyboard shortcuts
• Deselecting any if the insert/update/delete heck box for already audited table and creating the new trigger, will not remove the trigger for that operation

Changes:

• The application now requires Microsoft .NET Framework 4.5.2
• Windows Server 2003 is no longer supported

Known issue:

• Server list doesn't show local servers

Enhancements:

• The application now supports DDL changes auditing and reporting

Fixes:

• The installation process continues even after clicking the "No" button, when prompted for continuing the installation
• Modified date value is not shown at all in the exported .xls report
• The /archinstall switch in the CLI does not analyze stored procedure when used with the [z] argument
• Triggers will not be set if there is no editor selected
• An informative message about the missing architecture does not stay on top when switching to another application
• "Object reference not set to an instance of an object." error is encountered when applying a custom filter with wrong syntax
• After installing the new version of the application, an old version is still present
• "Object reference not set to an instance of an object." error is encountered when applying options in the "Aggregate" report
• "'Year' does not belong to underlying table." error is encountered when applying options in the "Aggregate" report after changing the "Group by" date and removing a column from the "Filter" results grid using the "Select columns" option
• "Method 'ApexSql.Trigger.Properties.CliStrings.CreateDescription' not found" error is encountered when using the /? switch in the CLI
• The project file switch /pr asks for server and database specification
• "Object reference not set to an instance of an object." error is encountered when trying to use any of the "Check" button in the "Objects" part of the "Home" tab, when canceling the process after triggers script is created
• If the trigger that has the same name as the one that the application creates it will be overridden
• After canceling the refresh process, the main grid remains blank
• "Could not load the project from the supplied file" error is encountered when opening a project file from different machine
• The "Refresh" button does not work in the "Manage triggers" form, when the triggers are managed from SQL Server Management Studio
• The "Uncheck columns" buttons unchecks both columns and tables
• Inconsistent behavior between manual unchecking of columns and using the "Uncheck columns" button
• Inappropriate message when creating a SQL job for deleting the audited data, when auditing Azure database
• After closing the "Install architecture" dialog, the main grid is refreshed even if there were no changes to the architecture
• The "Check all" option in the “Manage triggers” window is enabled even if there are no triggers present
• The "Job history" form opens even when the job did not run and there is no history to show
• Deleting triggers and the architecture is allowed even if they are not installed
• Buttons in the "Manage triggers" form are not disabled when there are no triggers installed
• Missing arguments for TXT and DOC file formats for the Output file format switch in the CLI
• The application prints out verbose messages even if the /v switch is not specified
• The "Reset" and "Export" buttons are enabled even if filters are not selected when the report form is initiated
• Missing drop down lists in the filter row, when filtering audited data in the report's grid
• Renamed column will not be properly presented in the "Schema changes" form
• Missing informative message that SQL Agent Job service is not running when scheduling data deletion job
• The "Table schema script" cannot be excluded from the architecture
• The table/column selection will not be remembered if the option to save/view a trigger script outside the application is canceled
• An exception error is encountered when running a script with errors in the template editor
• The application will be blocked if switched to another window when it is maximized, after checking for schema changes
• The filter selection from the first filter box on the main window grid is barely visible
• No consistency in the default file name for the report when exporting report after clicking on the Export button
• The application fails to preview database objects in the main grid, if the Cumulative update 7 for SQL Server 212 Service pack 2 is installed

Changes:

• The "Schema changes" button is moved from "Reports" group to "Objects" group in the main ribbon
• The "DDL" button is added to the "Reports" group in the main ribbon
• The "DDL" section is added in the "Manage triggers" section
• The "DDL reporting stored procedures" is added in the "Manage architecture" and "Install" sections

Enhancements:

• The application now supports Azure SQL Database V12

Fixes:

• Standard reports with more than 100000 rows are causing the application to become unresponsive
• Missing prompt message when saving a project with already existing name
• The application fails to audit database if there are tables with the same names but different schema
• Architecture file path is not active in the "Manage architecture" window
• Analyzing the architecture results show that some scripts are missing
• Missing options in the "Checked items" command from the main grid context menu
• Items selection in the main grid is not remembered after applying a command from the right-click menu
• "An error occurred while loading the DynamicSyntaxLanguage 'VBScript'" error is encountered when clicking the "Edit template" button
• The application fails to preview created triggers in the triggers section
• The application saves project on incorrect location
• The application creates inappropriate folder for the license file
• The "Architecture check error: Could not find stored procedure 'dbo.AUDIT_prc_Analyze'. error is encountered when excluding the analyze script from the architecture
• The "Check fields" option from the "All items" context menu option in the main grid, does not check boxes for tables
• If the main application form is moved to a secondary monitor, maximizing the manage architecture window will make it to disappear and freezes the application
• The "Prepared" column in the main grid is not checked properly
• The "Template editor" window fails to maximize when the application is used on secondary monitor
• The "Clear" and "Edit" options can be applied on already unchecked item in the trigger architecture installation wizard
• The state of the "Test" button, and the "Browse" icon in the "Options" dialog are not correctly set, when the application is started
• No triggers shown in the "Manage triggers" window, even if they are correctly installed
• The "Install data tables" statement is repeated twice in the CLI when installing the architecture
• Running the analyze script will give the incorrect info
• The "System out of memory exception" error is encountered on attempt to create auditing triggers on a database with large number of tables
• "job syspolicy_purge_history' unknown results. please, make sure SQLAgent is running" error is encountered when successfully performing the delete job
• Standard report output preview does nod display the correct length of the file
• "Help URL 'Main_grid/Audit_grid.htm' is not valid." error is encountered when initiating help via F1 key in the main window
• The application cannot detect the installed named instances of SQL Server on local machine if SQL Server Browser is not active
• The "Lookup" feature creates audit entries even if the old and new value are the same
• Sorting records by date in the "Aggregate report" grid is not sorting correctly when the "Group by date" is enabled with the "Hour" option
• "ApexSql.Audit.New.Gui.Controls.Report.ReportException" error is encountered when trying to create report for specific database
• "System.NullReferenceException"' error is encountered when filtering with wrong format of custom filter during creation standard report
• Main form can not reopen project due to error "ApexSql.Audit.New.Gui.Forms.MainForm.a" when older architecture database is installed
• The application can be uninstalled while it is still running
• Inappropriate message is shown when trying to activate the application with outdated key
• User password for SQL Server Authentication is not encrypted in the saved project file
• Incorrect default location for saving projects
• Script triggers shows wrong info if there are no triggers created in Triggers management dialog

Changes:

• The application name is changed from ApexSQL Audit to ApexSQL Trigger

Fixes:

• Pressing F1 for help throws exception in the template editor
• The “Delete data wizard” option is displayed as a link instead of a button in the “Manage Audit data” window
• The value of the “Change date” column in the “Database structure changes” window displays current date instead the date of the actual change
• Drop down list buttons for the “Watch field name” and “Audit field name” columns in the “Watches” panel are not visible
• Missing icons in the “Output” drop down list of the “Standard” and “Aggregate” report windows
• The trigger description values are missing in the "Trigger details" section of the "Manage triggers" window
• The “Lookup” feature creates audit entries even if the old and the new values are the same
• Missing icons in the context menu of the Audit grid in the application main window
• The application can be uninstalled even if it is still running
• Incorrect default location for saving projects
• User password for SQL Server Authentication is not encrypted in the saved project file
• Sorting records by date in the “Aggregate report” grid is not sorting correctly when the “Group by date” option is enabled and the “Hour” option is checked
• Inconsistency between the buttons in the ribbon (Row filter) and the grid (Filter Row)
• The application architecture files saved in an older application version (2013 and older) cannot be opened in the new application version (2014 R1)

Known limitations:

• Standard reports with more than 100,000 rows may cause the application to become unresponsive

Enhancements:

• The application now fully supports SQL Server 2014

Fixes:

• The "Activate" button is disabled
• The "Schema changes" feature doesn't work on unsaved projects and it reports that there are no schema changes even if the changes were made
• The application exports all in-application available columns from the report grid, instead of the ones that are shown only
• The "Activate" button is clickable after the activation process is completed
• A reference to a non-default audit architecture is not saved within a project file
• Auditing does not work if the TableID value is incorrect in a project file
• Saving the audit architecture to a file using the "Template editor" dialog is not working properly and the saved file must be corrected manually

Changes:

• New user interface that follows Metro UI style
• Windows XP is no longer supported

Fixes:

• When installing, the application checks for .NET framework 2.0 instead of .NET framework 3.5
• Changes made using the "Template editor" to a custom audit architecture which has been set as the default, are not saved unless the custom architecture is explicitly loaded

Enhancements:

• The application is now FIPS compliant
• The application now supports auditing SQL Azure databases
• Enabling or disabling triggers is now up to 50% faster
• Include (.inc) files can now be edited via the Template editor

Fixes:

• Updating the 2008 version of the application to the 2011 version and then reinstalling the 2011 version results in the application attempting to load the architecture file from the in the wrong location and showing the message "Arhitecture file: C:\Program Files (x86)\ApexSQL\ApexSQLAudit2011\ApexSQL2049.audx doesn't exists"
• Selecting one of the "Check insert trigger(s)", "Check delete trigger(s)" or "Check update trigger(s)" options in both the "All items" and "Checked items" submenus of the "Main" grid's context menu doesn't result in automatically selecting the appropriate check boxes in the "Main" grid
• The application starts the auditing process even if a non-existing project has been specified via the CLI without properly notifying the user about the missing project
• Using the spacebar to select or deselect the checkboxes in the "Custom row key" panel doesn't result in the intended selection
• Schema changes for non-audited tables are reported even if the "Report schema changes for non-audited tables" option is set to false
• 10.0 is displayed in the "Status" bar for SQL Server 2012 instead of 11.0
• An asterisk is displayed in the title bare as the name of a new, unnamed project
• The auditing SQL tables are locked while generating a standard report
• Unicode characters in audited data are shown as "?" in the generated reports
• Changes made to the position and size of the "Edit key for table" dialog are lost upon its closing
• An incorrect application version is displayed in the Add/Remove programs applet of the Windows Control Panel
• Renaming any SQL table results in the "Check for schema changes" feature reporting that a SQL table, named with the original name of the renamed SQL table, has been dropped, and that a new SQL table, named with the new name of the renamed SQL table, has been created
• The "Template editor" lacks a horizontal scroll bar
• The icon used for the "Training" button located in the "Resources" tab of the ribbon differs from the icon used for the same button in other ApexSQL applications
• Updating the application to the latest version results in failure to create the auditing SQL triggers due to missing columns in the auditing SQL tables
• The "System.ComponentModel.Win32Exception" error is encountered when attempting to open a report in PDF format if no third party application is associated with PDF files
• The "Modified date" column in the application's standard report doesn't display the time of the change
• Attempting to generate any of the auditing reports puts the application in an unresponsive state when auditing more than 200 SQL tables with more than 1000 row each
• Using the "Remove this column" option in any report doesn't remove the column from the report
• The title of the "Delete data wizard dialog" is spelled incorrectly
• Schema changes are not reported automatically when opening a saved project
• 'Select All'/Deselect All' in Standard report's filter criteria 'Table name' results in selecting/deselecting only the visible part of the drop-down list
• ArgumentOutOfRangeException exception is encountered when using '/purge' switch for purging data via the CLI
• 'Invalid switch definition' error message is encountered when using the '/older' switch for purging data via the CLI
• ArgumentOutOfRangeException exception is encountered when using the '/maxrows' switch for purging data via the CLI
• Changes made to row keys, watches and lookups aren't saved with the project
• 'Checked', 'Audited', 'Changed' and 'Prepared' main grid columns cannot be filtered due to the empty drop-down filter row
• Save changes dialog is displayed when closing the application if project changes were already saved manually
• Save command doesn't save changes for previously saved and reopened project

Enhancements:

• SQL Server 2012 databases are supported for auditing now
• Progress dialogs have been redesigned across the application for improved accuracy and usability
• A new Office 2007 style interface with ribbon bar, quick access toolbar and ApexSQL Audit button has been introduced
• A new Resources ribbon bar has been introduced for quick access to Help page, Support forum, Training page, FAQs, Knowledge base, Troubleshooting, About and Get Updates dialog boxes
• A new Project Management dialog has been introduced
• The Project Management dialog now shows all projects as well as recently used ones
• Projects can be pinned/unpinned to the Recent Projects list in the Project Management dialog
• The project description can be edited directly from the Project Management dialog
• 'Show on Startup' option has been added to the Project Management dialog
• Startup Action options group has been added to the Options dialog to control the behavior of the Project Management dialog. The following options are available: 'Show Project Management dialog', 'Show last opened project' and 'None'
• The application now has 3 color schemes: Blue, Silver and Black
• The Options dialog has been redesigned with new the Office 2007 button bar
• Manage Data form has been redesigned for improved usability
• Tooltips have been implemented for all options in Options and Install Architecture forms
• Standard and Aggregate Report forms now detect if there is no available data to report
• The application doesn't require administrative permissions to start on Windows Vista and later anymore
• The following connection options have been added to Project form: 'Execution timeout' and 'Encrypt connection'
• A grid toolbar has been implemented in Manage Audit Triggers, Standard and Aggregate Report forms
• Standard and Aggregate Reports can now be exported to PDF
• Standard Report CSV export performance has been improved
• Standard and Aggregate Report forms are now more responsive when working with large data sets (more than 10,000 operations)
• The following new arguments have been implemented for /architect_install CLI switch:
• All [a] – install entire architecture

Fixes:

• Lookup data is captured on any audited column change not just the one the lookup was created for
• Trigger creation script is auto deleted on application close if its size exceeds 3 MB
• Application stops responding when connecting to a database without a project
• Number of audited fields instead of transactions occurred is shown in Aggregate Reporting form grid
• Auditing Triggers can be installed before Auditing Architecture
• Changes to float columns are audited with precision loss to 2 digits after dot
• 'Delete Data by Log Size' criteria is considered even if not selected when deleting data criteria-based in Manage Data form
• Watches cannot be removed after clicking empty area in Watches list
• Tables cannot be checked with Space button in main grid
• Main form is not maximized at application startup
• Template Editor Description and Legal fields are not updatable
• Standard and Aggregate Reporting forms don't show the resize indicator in the right bottom corner
• 'Old value' and 'New value' columns in Standard Reporting form grid expand to fit the entire value that may cause them to grow too large
• Varbinary(max) values longer than 8,000 characters are shown truncated in Standard Reporting form grid
• "Undefined data" error is encountered when selecting a database containing Fulltext Stoplists
• False schema changes get detected if Auditing Triggers generation was cancelled
• Auditing Triggers cannot be created for new Tables and columns in CLI
• Table isn't auto selected for auditing when its columns are selected
• Last used folders aren't remembered within a session
• Checking/unchecking Auditing Trigger in Manage Triggers form grid expands all groups in the grid
• Default button on Edit Key for Table form when clicked disables Primary Key edit
• Save changes prompt is shown regardless of project state when auditing triggers generation is initiated from main grid context menu
• Scrolling a grid and checking a row not shown originally moves selection back to the first row in a number of places including Fields for pane, Manage Triggers form, etc.
• Connect to SQL Server form is shown system modal
• NULL values in varbinary columns are shown as '0x' instead of 'NULL' in Standard Reporting form grid
• Recent projects list in File menu is not working
• Query Timeout option default value cannot be changed
• Refreshing main grid clears all column filters but leaves the grid filtered
• Columns of a new Table aren't auto selected for auditing when 'Automatically Check All New Fields' option is ON

Changes:

• Undo Transactions feature has been deprecated
• Auditing architecture functionality has been moved to a newly implemented toolbar in the Manage Architecture form
• Main menu and toolbar have been removed from Standard and Aggregate Report forms
• 'Export to Excel' export item has been renamed to 'Output to CSV' on Standard and Aggregate Report forms
• The /profile switch has been deprecated and removed from the CLI
• The short name of the /project CLI switch is /pr now
• Default extension for project files has been changed from .axad to .axap
• /addtrigger CLI switch now requires a list of tables and columns to create auditing triggers for
• /remtrigger CLI switch now requires a list of tables to remove auditing triggers from

Enhancements:

• Added support for auditing MS SQL Server 2008 tables
• Added support for new MS SQL Server 2008 data types (date, time, datetime2, datetimeoffset, geometry, geography, hierarchyid, filestream)
• Improved Project Creation form

Fixes:

• Error appeared during syntax check after triggers generating for a specific db
• Switching between default script editor options doesn't trigger Apply button
• Jobs show up without names
• Save Project button doesn't get enabled whatever you do inside the project
• Open Existing Project opens "Open file" dialog instead Manage projects form
• Edit Project button in the toolbar opens the Manage Projects dialog
• Project Name which displayed in the Project grid is incorrect
• Text fields are audited incorrectly
• Insert and Update triggers are not installed on table with text field only
• The application stopped working when executed on Win2008 x86 server
• CLI: /test switch does not show the list of parsed switches
• Exception at app startup if a project from the project history is corrupted
• Exception when using an empty project file
• Values format of Float and Real type do not correspond to initial ones from DB
• Standard report shows smalldatetime type similar to datetime
• Can't rename project in Wizard's grid
• Grouping item in context menu of recent projects in Project wizard has wrong state after reopen
• Master sys db appears in the database field by default
• Values of time, datetime and related data types have different format in reports

Changes:

• Using Web help file instead of local CHM