Page History
...
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:
|
Scroll pdf ignore | ||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SQL Diagnostic Manager for MySQL agentless and cost-effective performance monitoring for MySQL and MariaDB. IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal Newtabfooter |
Newtabfooter |
Newtabfooter |
Newtabfooter |
Newtabfooter |
Newtabfooter |
Newtabfooter |
| |||||||||||||||||||||||||||||||||||||||||||
Newtabfooter | ||||||||||||||||||||||||||||||||||||||||||||||||||
|