Page History
This page lists all the new features and fixed issues from previous releases for SQL Diagnostic Manager for MySQL:
8.8.0 SQL DM for MySQL (March 2019)
New Features
- SQL DM for MySQL now monitors Google Cloud SQL server Operating System metrics.
- This release includes Google Cloud SQL server file based log monitoring for General query, Slow query, and Error log files.
Note | ||||||
---|---|---|---|---|---|---|
This release includes new registration keys. The new keys are available for registered users from our
|
Fixed Issues
- Regular Expression can now be used for the "Queries Starting with" filter for Processlist based Sniffer.
- The "Flush Status" query was renamed to "Flush Local Status" in the Monitors tab.
- SQL DM for MySQL is no longer displaying the warning message "User does not seem to have PROCESS privileges on this host. Only user's own processes will be displayed".
- The message "No data to display" in the history trend analysis graph for Monitor InnoDB cache>Free Memory is no longer prompting.
- SQL DM for MySQL is no longer displaying the "Undefined" message when hovering over the trend graph with a Monitor value of zero.
- The SQL Query for the CSO Tables_Without_Constraints was modified to excludes the views.
- SQL DM for MySQL now correctly raises SNMP traps/Syslog notifications when a monitor state changes from "Warning" to "Critical".
- The password field value is now correctly shown as a masked value.
- The RDS Log monitoring "Test reading the file" now correctly checks for "DownloadDBLogFilePortion" permissions.
Miscellaneous
- The double quotes can now be used in the email subject format.
- The MOM variable MemAvailable was added. The Javascript function for the RAM Usage monitor is modified to display appropriate value depending on the kernel.
- The MariaDB C/C connector was upgraded.
- SQL DM for MySQL has included an option to show truncated query/full query in the Threads page.
- All the SQL DM for MySQL passwords are stored encrypted in the SQLite database.
8.7.0 SQL DM for MySQL (August 2018)
New Features
No New Features for this version.
Fixed Issues
- In some rare-cases SQL DM displayed connection timeout error in Query Analyzer page.
- SQL DM logged error “too many SQL variables” if the Custom SQL Object query returned more than 500 rows
- Auto-Refresh interval was not getting set in Threads page.
- In Query Analyzer, Sniffer Settings gave console error on saving.
- OS metrics monitoring did not work with Aurora instances when the instance was registered with IP address.
- On killing one thread in the Threads page, 2 extra rows got removed.
- Default notification subject is changed to SQL DM for MySQL | [$ALERT_TYPE] | [$SERVER_NAME] | [$MSG_DETAILS].
- Now separate SNMP traps will be sent for each alertable monitor in one collection. Earlier, a single trap contained all alertable monitors.
- When unix_socket plugin is enabled for a user then all the users were listed under the monitor “Accounts without passwords”.
- Added more information in the Query Details popup in Query Analyzer.
- In pages with multi-server selector, on selecting and deselecting the servers in the selector pop-up, the servers are updated/selected in the server selector field in the background.
- In Query Analyzer and Real-Time, the metric value in the UI and in the downloaded CSV report did not match.
- In Query Analyzer and Real-Time, column names were different in CSV report as compared to UI.
- Diagnostic report showed wrong value for “Read file from” parameter, if log monitoring is disabled.
8.6.0 SQL DM for MySQL (April 2018)
New Features:
- A Galera cluster can now be automatically registered specifying any single node in the cluster.
- Optimized counter migration logic. This reduces the migration conflicts on upgrading SQL DM for MySQL tremendously. Post SQL DM for MySQL-8.6.0, a conflict is raised on upgrade only if any counter definition is modified in the latest release and the user has also customized the same counter.
- Added more columns for Slow Query log (for MariaDB and Percona Server) like full_scan, full_join etc. These values are written to Slow query log when ‘log_slow_verbosity’ is set to “Query_plan”.
- Connection timeout (MySQL, SSH and SSH Tunnel) can now be set for servers individually. The default value is 30 second
Fixed Issues:
- SQL DM for MySQL logged an SQLite error “Udo.def: not an error” on fresh installation.
- “Create User..” and “Create role..” queries were shown as a schema change in audit log.
- Queries containing ‘<’ or ‘>’ were displayed with their HTML-entities ‘<’, ‘>’ in “Threads” page.
- SQL DM for MySQL failed to read the MySQL log files when ‘log_output’ variable was set as both File and Table.
- SQL DM for MySQL failed to connect and displayed “Operations error” when using Active Directory External Authentication.
- In rare cases SQL DM failed to raise alerts for the monitor “Recent entries of type [Error]”.
Miscellaneous:
- If the server’s log query path variable returns a relative path, then SQL DM for MySQL generates the absolute path – required by MONyog – automatically.
- Added the monitor “Most Advanced Node” in the Galera group.
8.5.0 SQL DM for MySQL (March 2018)
New Features:
- SQL DM for MySQL can now analyze MariaDB and MySQL enterprise Audit log.
- Added support for LDAP with StarTLS and SSL.
- The default path for MONyog.log can be changed using the parameter “MONyogLogPath” from the MONyog.ini file.
Fixed Issues:
- SQL DM for MySQL logged bogus SQLite errors on fresh installation.
- SQL DM for MySQL displayed console error if LDAP group name contained inverted comma.
- Changed alert condition for “Seconds behind master” monitor to consider “NULL” as an alertable condition. It considered the value “NULL” stable condition earlier.
- On upgrading, SQL DM for MySQL filled the mail alert field for sniffer with the bogus email id “admin@mydomain.com”.
- On selecting a tag in server selector GUI and then returning back to the main list, the default list of tags disappeared.
Miscellaneous:
- “MySQL server restarted” alert are shown in table format.
- Added option to view locked and locking queries when hovering over the queries in the Real Time
- Upgraded SQLite library to v3.21.0.
8.4.1 SQL DM for MySQL (January 2018)
Fixed Issues:
- The Linux command ‘ps’ failed to identify SQL DM for MySQL process status. This was due to a packaging issue introduced in 8.4.0. Versions before that were not affected.
- The option “Notify when server config change detected” compared in a case-sensitive manner and thus raised false alerts when the value for the MySQL variables changed from lower to upper case and vice versa. This could happen when a MySQL server was upgraded.
8.4.0 SQL DM for MySQL (December 2017)
New Features:
- Added more notification channels (Slack and Pagerduty) for SQL DM for MySQL alerts.
- Option to write SQL DM for MySQL alerts in the Syslog (of the machine where SQL DM for MySQL is installed). This option is only available for Linux.
- Option to edit the subject line for SQL DM for MySQL alerts.
- Added MONyog API to disable notification for a monitor based on a server/tag.
- Complete re-design of the Settings page.
Fixed Issues:
- Export as CSV was downloading sorted based on “Average latency” column, even if sorted based on another column in Query Analyzer.
- Fixed a case where SQL DM for MySQL sent bogus alerts.
- Fixed a bug in reading RDS log files.
- The Query filter “Custom” did not work in “Threads” page.
- In rare cases, SQL DM for MySQL Disk space Monitoring alert gave false alerts.
- The “Table” column returned empty values under “Tables” filter in Real-time.
- SNMPv2 traps were having the same OID for two different objects what caused SNMP alerts failure with SNMPv2 services.
Miscellaneous:
- Increased the length of tag and server names to 2048 characters.
8.3.2 SQL DM for MySQL (November 2017)
Fixed Issues:
- Resolved an issue regarding access to log files on RDS. The issue occurred because the XML response from the RDS REST API has recently changed in some cases. Our XML parsing was improved to handle this.
8.3.1 SQL DM for MySQL (November 2017)
Fixed Issues:
- When monitoring MariaDB servers from version 10.1, bogus alerts were raised for the ‘wsrep_ready’ global status variable, if the server was not a part of a Galera cluster. The wsrep API for Galera is loaded with those servers (with ‘wsrep_ready’ returning “OFF”) even though it is not used at all.
- Edit server MONyog API did not support data directory number of the registered servers for ‘_server’ parameter.
8.3.0 SQL DM for MySQL (October 2017)
New Features:
Option to set a distinct email distribution list for warning and critical alerts: Now you can define a proper demarcation between the users who receives a particular alert based on the alert status. For instance, if you want only your on-call DBAs to receive critical alerts 24/7, this feature handles that easily.
Graph Analysis: You can group one single metric (which you find most important) from different servers into one unified chart. This allows You can group one single metric (which you find most important) from different servers into one unified chart. This allows you to visually analyse a metric across servers at various points in time.
Disk monitoring of the system where SQL DM for MySQL is installed: In case the free space on the system where SQL DM for MySQL is installed goes below the threshold value, SQL DM for MySQL raises an alert.
Filter to exclude unwanted long running queries in Sniffer:
You can tell SQL DM for MySQL to ignore a particular type of query by specifying a regular expression. SQL DM for MySQL neither would kill nor send an alert for such long-running queries.
Option to filter queries based on poor indexes, missing indexes, errors and warnings. This feature is available for PERFORMANCE SCHEMA based sniffer in Query Analyzer and "Show details" page in Dashboard. When you choose a filter, SQL DM for MySQL shows queries based on the criterias set.
Redesigned Server selector
Redesigned Query Analyzer: a more intuitive view of the top 5 queries based on total time.
Added proper Y-axis unit for charts, along with the option to define the units and unit-factors.
Fixed Issues:
SQL DM for MySQL was logging “UNIQUE constraint failed..” errors in MONyog.log
System charts failed to show data for many data collections, when the system metrics was enabled from the Dashboard page.
In some rare cases, real-time page hanged on switching between real-time sessions.
Option to plot values based on data collection in History/Trend analysis (For uptime counters). Only Group by option was available for those counters.
SQL DM for MySQL failed to recognize Aurora instances for OS monitoring. The four required fields for OS monitoring were not displayed.
Email addresses with + in monitor level notification settings was not accepted.
Added ‘DB’ as a column under ‘Manage Columns’ in Dashboard’s ‘show details’ page in ‘Processlist’ mode
SQL DM for MySQL showed the total time and average latency as 0 when the execution time of the query was less than a second for table based slow query log.
Fixed an issue with Custom SQL Object (CSO) - SQL DM for MySQL logged entries like “not an error” in MONyog.log.
8.2.0 SQL DM for MySQL (August 2017)
New Features:
- Added option to have same Y-axis scaling for Dashboard charts across all servers.
Fixed Issues:
- Query count could return negative value in Overview page due to integer overflow.
- The History/Trend analysis chart for the counter “Free disk space” was not rendering properly.
- The Monyog API for enabling System metrics for RDS instances was not working as expected.
- After zooming into the real-time chart, the Query column was not getting sorted.
- History/Trend could show wrong value for some counters – mainly string based counters.
- In case of RDS servers, rebuild of a server’s database, restarting SQL DM for MySQL or using “editserver” API could stop the collection for OS metrics.
- When using cname for RDS servers, SQL DM for MySQL failed to enable system metrics.
Miscellaneous:
- Redesigned Time-selector for all the features.
- Upgraded OpenSSL to current v1.0.2l. The version used before had a few non-critical security issues. Also quite a lot of libraries used internally were updated.
8.1.1 SQL DM for MySQL (July 2017)
Fixed Issues:
- Regression bug introduced in SQL DM for MySQL-8.1.0: SQL DM for MySQL failed to install on Linux machines with no “kernel headers” installed
8.1.0 SQL DM for MySQL (July 2017)
New Features:
- It is now possible to get OS metrics from Amazon RDS/Aurora (but not Azure, where interface for same is disabled).
- Added an option to generate a token in SQL DM for MySQL to be used with the Monyog API as an alternative to SQL DM for MySQL user and password.
- Added an option to define a “seconds_behind_master” setting in Replication page determining if the slave should be considered in sync or not. On some environments, slave is rarely fully in sync and in such cases, the alerting was not really useful before.
- MONyog-bin.pid location on Linux can now be changed from Monyog.ini file.
- Reintroduced the tabular view for Replication overview page. Now, the user can choose between tabular and graphical view.
- Added an option to select the way the server selector should work in SQL DM for MySQL, i.e: same servers across all pages or different across pages.
Fixed Issues:
- Seconds behind master could show wrong value in the chart.
- Export as CSV didn’t work for “Locked and Locking Queries” in Real-Time.
- On HDMI and higher resolution monitors, overview page could display distorted.
- Extra columns added from manage columns in Real-Time were getting reset to default set of columns on moving away from the page.
- In Dashboard the value of min/max/avg displayed as 0 if number of points was larger than 10,000, Also, if the chart was exploded, the chart would display empty.
- Some counters did not show values formatted properly.
- In mail alerts for counters in multi-replication monitor group a newline character in subject could cause the mail to display unformatted in some mail clients – including gmail web interface.
- In “long running query” alert there was a bare line feed character (\n) which could cause reading failures in some environments.
- History trend reports will show date as well in the timestamp if report spans more days.
- Collection and Purging interval was not setting properly while editing a UDO.
Miscellaneous:
- Redesigned the interface for adding new servers.
- It is now possible to display the “Replication Overview” page and set auto-refresh interval similar to SQL DM for MySQL before version 7.0. Different users have different preferences here.
- When installing SQL DM for MySQL on a Linux machine with kernel version less than 2.6.32, an error message will now inform that SQL DM for MySQL needs kernel version 2.6.32 or higher.
8.0.4 SQL DM for MySQL (Jun 2017)
Fixed Issues:
- In rare cases, Replication Overview page failed to load and a console error appeared.
- SQLite files used by Real-time were not always deleted when they should, resulting in unnecessary disk usage.
- Enabling the error log, slow query log and general query logs through the API for RDS server failed.
- Fixed a crash when connected to Azure MySQL-5.7 servers.
- Some columns were not getting sorted properly in Sniffer.
Miscellaneous:
- When stopping SQL DM for MySQL service, all running Real-time sessions will now be saved automatically.
- Upgraded LibSSH and LibCurl to the latest versions (0.7.5 and 7.54.0 respectively).
- SQL DM for MySQL will now only support Linux’es with kernel version equal to or higher than 2.6.32 . This is a consequence of an upgrade of our build environment necessary in order to support recent kernel versions and distributions.
- Upgraded the MariaDB Connector/C to 2.3.3. Due to this the MariaDB auth_gssapi (Kerberos) plugin is now supported.
8.0.3 SQL DM for MySQL (May 2017)
New Features:
- Option to export entire Dashboard charts.
- Option to search tags in Server selectors.
- Completely re-designed Servers page.
Fixed Issues:
- In monitors page, history chart did not plot for some counters.
- In Firefox browser, Servers page hanged with a large number of servers.
- SQL DM for MySQL failed to connect over SSH tunnel for Ubuntu-16.04.
- If ‘show_compatibility_56’ is off for MySQL-5.7 servers “Slave_running” counter gave a false alert. It will display “(n/a)” now.
Miscellaneous:
- API added to change the mode of Real-time Monitoring.
- Enhanced security measures to avoid vulnerabilities like clickjacking, phishing etc.
8.0.2 SQL DM for MySQL (April 2017)
New Features:
- Added Dashboard charts and monitors for the Aria storage engine.
- Performance schema can now be used with RDS Aurora (version 5.6.10).
Fixed Issues:
- SQL DM for MySQL failed to recognize replication topology in cases when “SHOW SLAVE STATUS” returned master host as an alias name while the master server was registered with an IP address in SQL DM for MySQL.
- Also SQL DM for MySQL could fail to recognize replication topology if SSH-tunnel was used to master.
- The replication monitors stopped updating values, when slaves stopped running as slaves.
- When logging in with LDAP group users, the onboarding tool-tips continued to display when no longer needed.
- Threads page stopped updating data once the custom query filter returned empty list.
- SQL DM for MySQL did not show queries starting with “SHOW..” in slow query log in Query Analyzer.
- “Lock time” column was not getting sorted properly for PS based real-time.
- SQL DM for MySQL returned console error for server name containing single quote(s).
- Deleting server registrations in SQL DM for MySQL could result in high CPU-load and IO. This is now reduced.
- SQL DM for MySQL RPM installer script failed to start SQL DM for MySQL in SUSE Linux Enterprise servers.
8.0.1 SQL DM for MySQL (April 2017)
Fixed Issues:
- Servers below MySQL-5.1.15 were shown disconnected even when the servers were connected, due to the absence of information_schema.plugins table.
- In IE 11, servers page gave console error and became unresponsive.
8.0.0 SQL DM for MySQL (March 2017)
New Features:
- Added support for Multi-Source Replication.
- SNMP v2 is now supported.
- Added new Monitors for a number of plugins (Failed to load plugin list, Non mature plugin, Audit log enabled, Audit log load_option FORCE_PLUS_PERMANENT, Password verification enabled).
Fixed Issues:
- The Galera counter “Total number of bytes replicated to other nodes” now uses “wsrep_replicated_bytes” and not “wsrep_replicated” variable as before.
- The Logrotate script shipped with SQL DM for MySQL failed to rotate the SQL DM for MySQL log in some cases.
- In some cases Top-5 tables in Disk Info page were not showing tables sorted based on total size.
Miscellaneous:
- Overview will now show top 10 queries only for the selected servers and not for all the registered servers in SQL DM for MySQL.
- Overview, Dashboard, Monitors, Threads and Server Config (Compare Config) pages will have their own separate server selector.
- Now the maximum no of servers that can be selected in each page is limited. Default is 10, but the number can be configured in Monyog.ini. On most systems we don’t advise raising the value as it may increase the time for loading pages.
Expand | ||
---|---|---|
| ||
7.0.5 SQL DM for MySQL (March 2017)Fixed Issues:
7.0.4 SQL DM for MySQL (February 2017)Fixed Issues:
Miscellaneous:
7.0.3 SQL DM for MySQL (February 2017)New Features:
Fixed Issues:
7.0.2 SQL DM for MySQL (January 2017)New Features:
Fixed Issues:
7.0.1 SQL DM for MySQL (January 2017)Fixed Issues:
7.0 SQL DM for MySQL (January 2017)New Features:
|
Expand | ||
---|---|---|
| ||
6.63 SQL DM for MySQL (October 2016)New Features:
Fixed Issues:
6.62 SQL DM for MySQL (September 2016)New Features:
Fixed Issues:
6.61 SQL DM for MySQL (September 2016)Fixed Issues:
6.6 SQL DM for MySQL (September 2016)New Features:
Fixed Issues:
6.55 SQL DM for MySQL (August 2016)Fixed Issues:
Miscellaneous:
6.54 SQL DM for MySQL (July 2016)Fixed Issues:
Miscellaneous:
6.53 SQL DM for MySQL (April 2016)Fixed Issues:
Miscellaneous:
6.52 SQL DM for MySQL (March 2016)New Features:
Fixed Issues:
Miscellaneous:
6.51 SQL DM for MySQL (December 2015)New Features:
Fixed Issues:
Miscellaneous:
6.5 SQL DM for MySQL (November 2015)New Features:
Fixed Issues:
6.4 SQL DM for MySQL (October 2015)New Features:
Fixed Issues:
6.34 SQL DM for MySQL (September 2015)New Features:
Fixed Issues:
6.33 SQL DM for MySQL (July 2015)New Features:
Fixed Issues:
6.32 SQL DM for MySQL (July 2015)New Features:
Fixed Issues:
6.31 SQL DM for MySQL (June 2015)New Features:
Fixed Issues:
6.3 SQL DM for MySQL (May 2015)New Features:
Fixed Issues:
6.27 SQL DM for MySQL (April 2015)Fixed Issues:
6.26 SQL DM for MySQL (March 2015)Fixed Issues:
Miscellaneous:
6.25 SQL DM for MySQL (February 2015)New Features:
Fixed Issues:
6.24 SQL DM for MySQL (February 2015)Fixed Issues:
Miscellaneous:
6.23 SQL DM for MySQL (January 2015)New Features:
Fixed Issues:
Miscellaneous:
6.22 SQL DM for MySQL (December 2014)New Features:
Fixed Issues:
6.21 SQL DM for MySQL (November 2014)Fixed Issues:
6.2 SQL DM for MySQL (October 2014)New Features:
Fixed Issues:
Miscellaneous:
6.1 SQL DM for MySQL (June 2014)New Features:
Fixed Issues:
Miscellaneous:
6.02 SQL DM for MySQL (June 2014)Fixed Issues:
6.01 SQL DM for MySQL (June 2014)Miscellaneous:
6.0 SQL DM for MySQL (June 2014)New Features:
Fixed Issues:
Miscellaneous:
|
Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
5.72 SQL DM for MySQL (April 2014)Fixed Issues:
Miscellaneous:
5.71 SQL DM for MySQL (March 2014)New Features:
Fixed Issues:
Miscellaneous:
5.7 SQL DM for MySQL (March 2014)Fixed Issues:
Miscellaneous:
5.69 SQL DM for MySQL (February 2014)Fixed Issues:
5.68 SQL DM for MySQL (February 2014)New Features:
Fixed Issues:
5.67 SQL DM for MySQL (February 2014)Fixed Issues:
Miscellaneous:
5.66 SQL DM for MySQL (November 2013)New Features:
Fixed Issues:
Miscellaneous:
5.65 SQL DM for MySQL (November 2013)Fixed Issues:
5.64 SQL DM for MySQL (October 2013)Fixed issues:
5.63 SQL DM for MySQL (September 2013)Fixed Issue:
5.62 SQL DM MySQL (September 2013)New Features:
Fixed Issues:
5.61 SQL DM for MySQL (August 2013)Miscellaneous:
5.6 SQL DM for MySQL (August 2013)New Features:
Fixed Issues:
5.58 SQL DM for MySQL (April 2013)New Features:
Fixed Issues:
5.57 SQL DM for MySQL (March 2013)Fixed Issues:
5.56 SQL DM for MySQL (December 2012)Fixed Issues:
5.55 SQL DM for MySQL (December 2012)Fixed Issues:
5.54 SQL DM for MySQL (November 2012)Fixed Issues:
5.53 SQL DM for MySQL (November 2012)New Features:
Fixed Issues:
5.52 SQL DM for MySQL (October 2012)Fixed Issues:
5.51 SQL DM for MySQL (October 2012)New Features:
Fixed Issues:
5.5 SQL DM for MySQL (September 2012)New Features:
5.3 SQL DM for MySQL (July 2012)New Features:
Fixed Issues:
5.21 SQL DM for MySQL (June 2012)New Features:
Fixed Issues:
Miscellaneous:
5.2 SQL DM for MySQL (May 2012)IMPORTANT note:
New Features:
Fixed Issues:
5.12 SQL DM for MySQL (April 2012)Fixed Issues:
5.11 SQL DM for MySQL (April 2012)IMPORTANT note:
New Features:
Fixed Issues:
Miscellaneous:
5.1 SQL DM for MySQL (March 2012)IMPORTANT note:
New Features:
Fixed Issues:
Miscellaneous:
5.0 SQL DM for MySQL (February 2012)UI Enhancements:
New Features:
Enhancement:
Miscellaneous:
|
Expand | ||
---|---|---|
| ||
4.81 SQL DM for MySQL (January 2012)Fixed Issues:
4.8 SQL DM for MySQL (December 2011)New Features:
Fixed Issues:
4.72 SQL DM for MySQL (October 2011)Fixed Issues:
4.71 SQL DM for MySQL (October 2011)Fixed Issues:
4.7 SQL DM for MySQL (October 2011)New Features:
Fixed Issues:
Miscellaneous:
4.62 SQL DM for MySQL (July 2011)Fixed Issues:
4.61 SQL DM for MySQL (July 2011)Fixed Issues:
4.6 SQL DM for MySQL (June 2011)New Features:
Fixed Issues:
4.51 SQL DM for MySQL (May 2011)New Features:
Fixed Issues:
4.5 SQL DM for MySQL (May 2011)New Features:
Fixed Issues:
4.2 SQL DM for MySQL (January 2011)Fixed Issue:
Miscellaneous:
4.12 SQL DM for MySQL (December 2010)Fixed Issues:
4.11 SQL DM for MySQL (November 2010)Fixed Issues:
4.1 SQL DM for MySQL (November 2010)New Features:
Fixed Issues:
4.02 SQL DM for MySQL (September 2010)Fixed Issues:
4.01 SQL DM for MySQL (August 2010)Fixed Issues:
4.0 SQL DM for MySQL (August 2010)New Features:
Fixed Issues:
Miscellaneous:
|
Expand | ||
---|---|---|
| ||
3.8 SQL DM for MySQL (August 2010)Fixed Issues:
Miscellaneous:
3.77 SQL DM for MySQL (July 2010)Fixed Issues:
3.76 SQL DM for MySQL (May 2010)Miscellaneous:
3.75 SQL DM for MySQL (April 2010)Fixed Issues:
Miscellaneous:
3.74 SQL DM for MySQL (April 2010)Fixed Issues:
3.73 SQL DM for MySQL (March 2010)Fixed Issues:
3.72 SQL DM for MySQL (February 2010)New Features:
Fixed Issues:
3.71 SQL DM for MySQL (February 2010)New Features:
Fixed Issues:
3.7 SQL DM for MySQL (February 2010)New Features:
Fixed Issues:
Miscellaneous:
3.65 SQL DM for MySQL (December 2009)New Features:
Fixed Issues:
3.62 SQL DM for MySQL (December 2009)Fixed Issues:
Miscellaneous:
3.61 SQL DM for MySQL (December 2009)Fixed Issues:
3.6 SQL DM for MySQL (November 2009)New Features:
Fixed Issues:
Miscellaneous:
3.5 SQL DM for MySQL (October 2009)New Features:
Fixed Issues:
3.16 SQL DM for MySQL (September 2009)Fixed Issues:
3.15 SQL DM for MySQL (August 2009)Fixed Issues:
3.14 SQL DM for MySQL (August 2009)Fixed Issues:
3.13 SQL DM for MySQL (August 2009)Fixed Issues:
3.12 SQL DM for MySQL (July 2009)New Features:
Fixed Issues:
Miscellaneous:
3.11 SQL DM for MySQL (June 2009)Fixed Issues:
3.1 SQL DM for MySQL (June 2009)Packaging:
New Features:
Fixed Issues:
Miscellaneous:
3.09 SQL DM for MySQL (June 2009)Fixed Issues:
3.08 SQL DM for MySQL (May 2009)Fixed Issues:
3.07 SQL DM for MySQL (May 2009)Fixed Issues:
3.06 SQL DM for MySQL (April 2009)Fixed Issues:
3.05 SQL DM for MySQL (March 2009)New Features:
Fixed Issues:
3.04 SQL DM for MySQL (March 2009)New Features:
Fixed Issues:
3.02 SQL DM for MySQL (February 2009)Fixed Issues:
3.01 SQL DM for MySQL (February 2009)Fixed Issues:
3.0 SQL DM for MySQL (February 2009)New Features:
Fixed Issues:
Miscellaneous:
|
Expand | ||
---|---|---|
| ||
2.9 SQL DM for MySQL (December 2008)New Features:
Fixed Issues:
2.83 SQL DM for MySQL (November 2008)Fixed Issues:
2.82 SQL DM for MySQL (October 2008)Fixed Issues:
2.81 SQL DM for MySQL (October 2008)Fixed Issues:
2.8 SQL DM for MySQL (September 2008)New Features:
Fixed Issues:
2.72 SQL DM for MySQL (September 2008)Fixed Issues:
2.71 SQL DM for MySQL (September 2008)Fixed Issues:
2.7 SQL DM for MySQL (September 2008)New Features:
Fixed:
Miscellaneous:
2.6 SQL DM for MySQL (August 2008)New Features:
Fixed Issues:
Miscellaneous:
2.51 SQL DM for MySQL (July 2008)Fixed Issues:
2.5 SQL DM for MySQL (July 2008)New Features:
The log analysis component will (whether operating on a 'real log' or a 'sniffer pseudo log') only display identical queries once but print a 'count' for every query. Important information (like execution time, number of instances for this query etc.) will be displayed in a sortable table view. In the log analyzer 'Filter settings' (not to be confused the filter settings of the 'query sniffer') there further is an option to 'replace literals'. The purpose of this option is to eliminate small differences between 'almost identical' queries. Currently 'quoted strings' and numbers are replaced with the dummy string 'XXX' only. We may extend this feature to support more (like special keywords and functions (like NULL, now()), operators etc.) in the next releases. It will depend on the demand for this as compared to the demand for other features. Also note that the current implementation has the 'imperfection' that also numbers that are not values (like the '1' in identifiers like
Fixed Issues:
2.06 SQL DM for MySQL (June 2008)Fixed Issues:
2.05 SQL DM for MySQL (May 2008)Fixed Issues:
2.04 SQL DM for MySQL (May 2008)Performance improvement:
2.03 SQL DM for MySQL (May 2008)Fixed Issues:
2.02 SQL DM for MySQL (April 2008)Fixed Issues:
2.01 SQL DM for MySQL (April 2008)Fixed Issues:
2.0 SQL DM for MySQL (March 2008)New Features:
Fixed Issues:
Miscellaneous:
More details on implementation of SSH-tunneling and History/Trends analysis:
|
Expand | ||
---|---|---|
| ||
1.52 SQL DM for MySQL (February 2008)Fixed Issues:
1.51 SQL DM for MySQL (January 2008)Fixed Issues:
1.51 SQL DM for MySQL (January 2008)Fixed Issues:
1.5 SQL DM for MySQL (December 2007)New Features:
Fixed Issues:
1.11 SQL DM for MySQL (October 2007)Fixed Issues:
1.1 SQL DM for MySQL (October 2007)New Features:
1.04 SQL DM for MySQL (August 2007)New Features:
Fixed Issues:
1.03 SQL DM for MySQL (August 2007)New Features:
Fixed Issues:
1.02 SQL DM for MySQL (August 2007)Fixed Issues:
1.01 SQL DM for MySQL (August 2007)Fixed Issues:
Additional note on file storage positions and upgrading: Version 1.0 RC changed the storage position for various files used by SQL DM for MySQL. This release is in this respect identical to 1.0 RC and 1.0. By default the embedded database is now stored:
... but user can specify another location if for instance she does not want to store on the system disk/partition at all. Also the monyog.ini file and the log file is now no longer stored in 'program files' file tree (or whatever localized name it has). The storage position is:
Users upgrading from 0.9 who want to use existing data must after installing this version:
No such intervention is required when upgrading from version 1.0 RC or 1.0 (unless storage position is changed again, of course!). Upgrading from versions before 0.9 is not possible. These versions must be uninstalled and installation folder deleted or this version must be installed to another folder. 1.0 SQL DM for MySQL (August 2007)New Features:
Fixed Issues:
Additional note on file storage positions: Version 1.0 RC changed the storage position for various files used by SQL DM for MySQL. This release is in this respect identical to 1.0 RC. By default the embedded database is now stored:
... but user can specify another location if for instance she does not want to store on the system disk/partition at all. Also the monyog.ini file and the log file is now no longer stored in 'program files' file tree (or whatever localized name it has). The storage position is:
Users upgrading from 0.9 who want to use existing data must after installing this version. No such intervention is required when upgrading from version 1.0 RC (unless storage position is changed again, of course!). Upgrading from versions before 0.9 is not possible. These versions must be uninstalled and installation folder deleted or this version must be installed to another folder. |
Expand | ||
---|---|---|
| ||
0.9 SQL DM for MySQL Beta1 (July 2007)Note that this release is a TRIAL build. It has the restrictions that,
Before expiry of this beta we plan to release version 1.0 FINAL and publish purchasing and licensing terms. Also notice that the schema of the embedded database has changed compared to previous versions. With this beta we will not provide a database upgrade script. If you have a previous version installed you must either,
New Features:
Known issues:
0.20 SQL DM for MySQL (May 2007)Fixed Issues:
0.16 SQL DM for MySQL (March 2007)Fixed Issues:
|