Fixed Issues:- Installing recent versions on top of 1.1 or earlier could disable connection to the OS (not to MySQL) of servers already registered (this bug was introduced when we started supporting key authentication with 1.5).
- Alert icons (red and yellow circles) were disappearing from the group in 'Show All' interface if the user clicked the next group.
Fixed Issues:- Adding a server with notification enabled was storing wrong information in the 'connection.data' configuration file. After a restart of the SQL DM for MySQL service the wrong information that was read from that file would cause notifications to stop working. Note that if a connection was configured in 'two steps' where notification settings were added to an existing connection there was no error.
- Fixed a memory leak occurring with public/private key authentication when connection was unsuccessful (server not available, invalid key pair etc.).
- The shortcuts installed by SQL DM for MySQL installers now point directly to '127.0.0.1' (and not 'localhost'). This solves an issue with Firefox on Windows Vista where resolution of the URL 'localhost' was very slow.
Fixed Issues:- Adding a server with notification enabled was storing wrong information in the 'connection.data' configuration file. After a restart of the SQL DM for MySQL service the wrong information that was read from that file would cause notifications to stop working. Note that if a connection was configured in 'two steps' where notification settings were added to an existing connection there was no error.
- Fixed a memory leak occurring with public/private key authentication when connection was unsuccessful (server not available, invalid key pair etc.).
- The shortcuts installed by SQL DM for MySQL installers now point directly to '127.0.0.1' (and not 'localhost'). This solves an issue with Firefox on Windows Vista where resolution of the URL 'localhost' was very slow.
New Features:- Major speed improvements (in both data collection and as regards browser responsiveness).
- Private/Public key authentication is now supported with SSH connection to remote hosts. Key format must be OpenSSH standard key format - special formats (like the one used by the 'Putty' program) are not supported.
- Added security-related counters and advisors.
- Added counters and advisors for schema and table operations.
- PROCESSLIST display will not by default 'filter out'. A button has been added in the 'Change Filter' dialog to switch between a non-filtered result and the (old) filtered result for the PROCESSLIST page.
- PROCESSLIST can be paused/resumed.
- Default SSH timeout (3 minutes) was replaced with 30 seconds.
Fixed Issues:- Fixed some small memory leaks.
- Deleting a connection did not remove all the files belonging to that connection.
- Fixed a rare issue where browser could report that the page cannot be displayed while saving/editing server details or connection (IE issue only).
- Fixed an issue with system counters where 100% CPU usage erroneously could be reported when SQL DM for MySQL started.
Fixed Issues:- HTML formatting of queries in the PROCESSLIST tab was not correct. As a result display of queries could be truncated.
New Features:- Support for SHOW FULL PROCESSLIST - SQL DM for MySQL monitor processes on the servers in real time. Various filtering options for PROCESSLIST are available. Further displays, copy and EXPLAIN (EXTENDED) a running query from inside SQL DM for MySQL.
- Documentation was updated - including information about the PROCESSLIST feature, up-to-date screenshots etc.
- Counters and Advisors - Small adjustments!
- Debug DUMP facility - SQL DM for MySQL (Windows version) has an ability to store crash-dumps fit for debugging similar to SQLyog as explained here:
| Newtab2 |
|---|
| alias | Debug facility |
|---|
| url | http://faq.webyog.com/content/32/145/en/explanation-of-the-sqlyog-debug-facility.html |
|---|
|
. - Menu rearrangement etc. - or clarity we have decreased the number of menus displaying. Those that 'went away' are available as links or submenus.
New Features:- Improved counters and advisors.
- Customize page now will show the .js-components that user changed with a red * (star). Note that existing .js-components will be overwritten when you upgrade. The red star will help you to see what you need to back up before upgrading.
- Default port is now 5555. With certain names used for the connections there was a conflict with a standard 'rule' of Norton Internet Security when port 9999 was used.
- The option to display graphs from the 'monitors/advisors... custom timeframe' interface was temporarily removed.
Fixed Issues:- Fixed a crashing bug in mailing section if a .js-component was corrupted.
- Adding the option to send mail after registering a server required SQL DM for MySQL service to be restarted.
New Features:- A BELL icon displays in the 'Monitors/Advisors' page for alertable counters.
- Various small GUI improvements.
- Documentation updated with details about system Objects + various small corrections.
Fixed Issues:- %age of queries doing full table scan metric was incorrect.
- With very small mail interval setting it could occur that selected servers became deselected.
- Fixed a bug in the calculation of full table scans.
Fixed Issues:- Fixes an issue in previous 1.x releases that may result in too early expiry of the TRIAL.
Fixed Issues:- Replication counters did not display in LINUX builds (both .rpm and .tar.gz).
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: - Windows 2K/XP/2003: {System_drive}:\Documents and Settings\All Users\ApplicationData\Webyog\MONyog\Data
- Windows Vista:{System_drive}:\ProgramData\Webyog\MONyog\Data
... 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: - Windows 2K/XP/2003: {System_drive}:\Documents and Settings\All Users\ApplicationData\Webyog\MONyog
- Windows Vista:{System_drive}:\ProgramData\Webyog\MONyog
Users upgrading from 0.9 who want to use existing data must after installing this version: - Stop SQL DM for MySQL service.
- Copy the folders containing databases named with a number like "0001" or "0002".
- Start SQL DM for MySQL service.
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. New Features:- Installs and runs on Windows 2000.
- Every counter is available in every timeframe.
- User can specify where the embedded database is stored.
Fixed Issues:- Retrieval of memory information from Linux servers was broken in 1.0 RC.
- Windows version: Solved an issue with a dependency on a .dll file that was reported missing on some systems.
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: - Windows 2K/XP/2003: {System_drive}:\Documents and Settings\All Users\ApplicationData\Webyog\MONyog\Data
- Windows Vista:{System_drive}:\ProgramData\Webyog\MONyog\Data
... 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: - Windows 2K/XP/2003: {System_drive}:\Documents and Settings\All Users\ApplicationData\Webyog\MONyog
- Windows Vista:{System_drive}:\ProgramData\Webyog\MONyog
Users upgrading from 0.9 who want to use existing data must after installing this version.
1. Stop SQL DM for MySQL service.
2. Copy the folders containing databases named with a number like "0001" or "0002".
3. Start SQL DM for MySQL service. 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. |