...
| Table of Contents |
|---|
| minLevel | 3 |
|---|
| indent | 50 |
|---|
| style | none |
|---|
|
1. SQL DM for MySQL is licensed per server. Does that mean SQL DM for MySQL servers or MySQL servers?
It means MySQL servers. You may install as many instances of SQL DM for MySQL as you like as long as the total number of MySQL servers monitored does not exceed your license.
TOP
2. Do I need to install SQL DM for MySQL on the same host as MySQL?
MySQL servers, SQL DM for MySQL server(s) and Clients (browser) can be installed independently everywhere where a TCP connection (like an Internet/Intranet connection) is available. Available TCP connections is all what is required. Put one on the Moon if you like (but don't ask us to pay for the connection!). Regarding installing SQL DM for MySQL on the same host as MySQL then SQL DM for MySQL Connects to/Monitors MySQL running on any platform.
TOP
3. What operating system does SQL DM for MySQL require?
Currently we support Windows (do not support Windows 2003) and Linux operating systems. Those are the Operating Systems where SQL DM for MySQL itself will have to be installed. The SQL DM for MySQL client functionalities only require an Internet browser and any platform (including platforms for handheld devices like mobile phone, PDA, tablet PC etc.) will do. There are also no restriction as regards the platforms the MySQL servers that SQL DM for MySQL connect to - it can be any. Additionally, SQL DM for MySQL is able to retrieve OS data from Linux Operation Systems.
TOP
4. How do I upgrade SQL DM for MySQL?
This is actually a license-related question and a technical question as well.
...
| Note |
|---|
|
Don't forget to backup whatever JavaScript you have edited,as they will be overwritten when you upgrade. You can take a back-up of Counters.def and Udo.def located inside SQL DM for MySQL folder: MONyog for this. Alternatively, you can directly upgrade, after upgrade you will get your JS changes as a conflict in SQL DM for MySQL UI, you can resolve those and keep your changes. |
TOP
5. Why should I upgrade?
Every new release adds features, fixes bugs, improves performance, stability, the GUI interface etc. Why should you NOT upgrade? Refer to Version History for details.
TOP
6. I have installed SQL DM for MySQL. What now? How do I get the reports?
What you installed was the MONyog(SQL DM for MySQL) service. This service is basically a webserver program. You connect to the service with an Internet browser by specifying the host where it is installed and the port that was specified when installing.
TOP
7. How can SQL DM for MySQL 'know all what it does'?
SQL DM for MySQL queries the MySQL servers about almost anything the server 'knows' except for data stored on those servers. The MySQL servers themselves store and maintain records of server configuration, users, history and much more. SQL DM for MySQL retrieves this information, organizes it, calculates on it and reports.
TOP
8. Where does SQL DM for MySQL store data?
...
The data folder specified above is the default settings only. You can store in any position on any mapped/mounted drive that is writeable.
TOP
9. How does SQL DM for MySQL store its data?
...
These features have all been requested by users. SQL DM for MySQL development has always been and will continue to be very attentive to user requests. We will update information here when plans for future developments have been decided.
TOP
35. How do I get help and report problems?
Four ways:
- Website Intercom http://www.webyog.com
- Post in our Forums http://www.webyog.com/forums
- Create ticket: support@webyog.com
- SQL DM for MySQL UI intercom
TOP
SQL DM for MySQL does not support the key generated from PuTTY for SSH connection. However, there is a workaround for it that you can use, you can convert the private key generated from "PuTTY key generator" into an open SSH key, and then you can use this key in SQL DM for MySQL to connect to the server. Here are the steps to follow:
...
- Copy the public key generated under the "Key" space to the authorized_keys file, which is located in the .ssh directory on the remote host that you want to connect to.
- Go to "Conversions" in PuTTY key generator and click on "Export openssh key" and save the new converted private key in a file.
- Now open the file containing the converted OpenSSH private key, copy this key and paste in the "Private key" field in SQL DM for MySQL (Edit server -> SSH settings -> Private key).
TOP
37. Steps to auto-start MONyog(SQL DM for MySQL) service with OS reboot in Ubuntu and Debian systems.
Users can make use of the "MONyog" script shipped with the Monyog(SQL DM for MySQL) package to auto-start MONyog(SQL DM for MySQL) service with OS reboot. The SQL DM for MySQL script is located at " /MONyog/bin/". Please follow the below steps:
- Copy the 'Monyog' to "/etc/init.d/" from " /MONyog/bin/"
- Open the 'Monyog' script located at "/etc/init.d/" and edit the variable "curdir" (line number 15) and set it to the path of bin. After editing, it should look like this: curdir="/home/Users/Downloads/MONyog/bin/"
- Make the script executable by 'chmod +x /etc/init.d/MONyog'
- Use debian utility update-rc.d to install the script: update- rc .d MONyog defaults
TOP
38. How to upgrade SQL DM for MySQL without losing your data or configuration?
The SQL DM for MySQL binaries are shipped in 3 packages: .tar, .rpm and .exe. The upgrade process is simple and depends on your package. The below steps will help you upgrade to the latest SQL DM for MySQL version without a hassle:
...
You can resolve these conflicts from the “Settings -> Manage changes” page, herein you get 2 options for all the listed conflicts: Use your changes/Discard your changes. 1- Use your changes will restore the local modifications which you had made in the previous version. 2- Discard your changes, will replace your changes with the default values.
TOP
39. How to maintain High Availability of SQL DM for MySQL?
Monit tool monitors the server process and can be used to maintain HA for SQL DM for MySQL.
...