ApexSQL BI Monitor enhances SQL Server Analysis Service monitoring in multiple SQL Server instances.
Features
New in ApexSQL BI Monitor 2018.02
- Monitor the most important Microsoft SQL Server Analysis Service Multidimensional databases performance metrics in multiple SQL Server instances.
- Monitor the most important Microsoft SQL Server Analysis Service cube and object performance metrics in multiple SQL Server instances.
- Monitor the ratio between two predefined metrics.
Fixes
Fixes in ApexSQL BI Monitor 2018.02
- A new SMTP server does not retain settings when created via the "Add email profile" panel.
- The application's installer uses the user entered Windows credential password for the LDF data file path, thus fully exposing the readable user-entered password in the application log file when LDF data file path ends with "\" char.
- The "Internal server error" error is encountered when only a single metric value is collected for the alert details page chart.
- The SQL Server Integration Service's metrics are not enabled and monitored after adding the service for monitoring.
- The SQL Server Integration Service's metrics cannot be enabled by directly selecting one or multiple metrics after adding the service.
- When evaluation trial is expired, the user can still add a SQL Server service instance for monitoring.
- The context menu shows "Enable monitoring" option for all enabled services after disabling monitoring for one SQL Server service via the group dashboard panel.
- The context menu does not open via the dashboard panel manage button if the panel is rotated to its backside.
- The repository index rebuild operation executes automatically each time the repository data purge operation is completed.
- The data purge operation purges data in every chunk using the time at the moment the chunk data purge stars instead of the time the purge operation is started.
- The baseline calculated for seven days exactly doesn’t calculate per day of the week.
- The baseline calculation for seven days takes too long time and often do not complete at all.
- The baseline calculation doesn’t validate that at least one metric is selected.
- No indication that specific alert is read or unread in the "Alerts" page.
- The charts are missing the zoom indicator.
- The missing drill-down link in panel charts.
- The application triggers an excessive number of alerts for several metrics even the metric value state is not changed.
- The "Operating system" information doesn't show correct information for remote SQL servers.
- The repository database log file shrinks after every data purge execution.
- The default configuration applies to every new SQL Server added for monitoring, even if new configuration is previously applied to all monitored instances via All instances parent group.
- The special characters are not supported in the repository database name.
- The "Edit" button does not work in the "Edit alert action profile" page.
- Email profiles cannot be created using the "Add alert action profile” page.
- Drill down via the "Availability" section alert number hyperlink in the dashboard panel displays all alerts for that service instead of the availability related ones only.
- Unchecking all severity in the "Alerts" page displays all alerts.
- Every system alert is shown three times in the "Alerts" page if all types of SQL Server services are being monitored.
- The dropdown menus are pulled back immediately after the mouse click in Mozilla Firefox browser.
- Clicking on one checkbox in the "Alerts" page checks another alert.
- Missing filtering alerts by SQL Server service and measurement groups.
- Cannot reset the applied filter in the group dashboard panels after opening the service management menu in the dashboard panel.
- Adding SQL Server services is taking a long time because the devices cannot be added via the background process.
- Long SQL Server service names are cut off in dashboard panels.
- The created custom report misses metric names and units for all chart.
- There is no warning message that data will be lost when navigating out from the "Configuration" page if changes are made.
- Missing info about the category, type and metric values for custom metrics in the "Activity log".
- The bar graph indicator in the SQL Server service instance dashboard cannot be used to drill down.
- The alert page does not display all alerts indicated in the instance dashboard alert indicator when the indicator is used to drill down.
- Downloading image of a graph does not offer the proper name.
- Navigating to a new tab or window displays the blank page in the Internet Explorer browser.
- The "Page not found" error is encountered when clicking on the "Help" link in "Resources" page.
- The monitored SQL Server service dashboard page does not open when the browser back function is used.
Fixes in ApexSQL Defrag 2018.02
- "Server not found" error is encountered when the policies that process indexes on SQL Server 2012 and earlier versions are executed.
Fixes in ApexSQL VM Monitor 2018.02
- Monitoring of virtual machines cannot be re-enabled after is disabled in the Group dashboard
- The special characters cannot be used for repository database name
- The blank page is displayed after switching from subsystem details (Chart details) page to any dashboard page
- The Configuration page is blank when switching from another page and virtual machine is selected in the tree view
- High alerts for virtual machine availability cannot be opened
- The memory available metric and other memory metrics charts do not have any values for Hyper-V hypervisors
- The purge operation automatically triggers the repository index rebuild operation
- Custom metrics, for "Memory" category, are not being measured
- Existing custom metrics are not saved after being edited
- Missing alerts read/unread indication on the Alerts page
- The blank page is displayed when the "Back" button is clicked on under a web browser, in case when previous page is the Dashboard
- The repository log file shrinks when the purge functionality is performed
- Virtual machine cannot be excluded from monitoring under the Virtual machines configuration page
- Hypervisor severity and alert summary number in Group dashboard table view are not correctly calculated
- The application excessively triggers alerts for availability even when the availability state has not been changed
- Baselines can be calculated for period shorter than 7 days
- The manual port test in the setup dialog does not check for unsafe port numbers when HTTP and HTTPS ports are tested