Page History
...
15. What are the major differences between other major MySQL Monitoring Tool and SQL DM for MySQL?
A: They have similarities (in which they both differ from server-side scripts used for monitoring): they both make use of a HTTP service, a database and both use a web-browser for reporting. Important differences are however,
...
16. Can I trust the expertise of SQL DM for MySQL developers?
A: SQL DM for MySQL is developed by the Webyog Softworks that also created the most popular GUI for data management with the MySQL server - SQLyog Enterprise. We have more than 10 years of experience with designing MySQL related software. We have expanded our team with highly qualified developers ever since we started. We are devoted to constantly extending our knowledge and understanding of MySQL internals. What more would you expect?
...
17. How does SQL DM for MySQL connect to MySQL?
A: SQL DM for MySQL uses the most proved and most efficient way of connecting: the native MariaDB Connector/C that is compiled into SQL DM for MySQL. Nothing else required: no separate client instance, no database abstraction layer (like ODBC/JDBC/ADO/.NET) and no webserver extensions (like PHP). Additionally, the connection can be 'wrapped' in a SSH tunnel. Also, SQL DM for MySQL implementation for this does not involve any other program (like Putty) running.
...
18. Windows warns after installation that SQL DM for MySQL may not have installed properly.
A: This may happen on some versions of Windows (Vista and higher) if you install a recent version of SQL DM for MySQL on top of an older version. The reason for this is that recent versions of Windows include a software called "Program Compatibility Assistant" (PCA) which tries to detect if an installer is running. It warns the user that the software might not have been correctly installed if the installer does not register a new uninstaller. The PCA is unable to detect changes made to an existing, registered uninstaller, which is what the new SQL DM for MySQL installers do. And thus, the warning is displayed. You can safely ignore this warning, but if it bothers you, you may just uninstall SQL DM for MySQL before upgrading to 3.5+. All collected data in the SQL DM for MySQL's data folder will still be available after reinstall. However, you should -
...
19. I would like to use SSH-tunnel, but my Windows server does not support it. Can that be fixed?
A: Yes, SSH support can be installed on Windows. You may install a complete Cygwin (Unix command line implementation for Windows). Alternatively, there are small packages available that support only a small subset of Cygwin (like SSH packages). Installation details depends on the exact Windows version.
...
20. SQL DM for MySQL throws an error when trying to connect to MySQL.
A: Please go through Error when trying to connect to MySQL. The same as here applies to SQL DM for MySQL as the client code is exactly the same in both programs. Observe however that everything related to HTTP-tunneling with SQLyog is not relevant for SQL DM for MySQL.
...
21. Failed to connect to MySQL: Can't connect to local MySQL server through socket... What can i do about this?
A: Ensure that the host specified resolves to an IP-adress. This error occurs with some Linux distributions (most important Debian) when specifying 'lcoalhost'. The system will map this to a Unix SOCKET file. SQL DM for MySQL connects through TCP and not to SOCKET. Try the ip '127.0.0.1' instead.
...
22. SQL DM for MySQL is taking up too much of system resources with the PROCESSLIST-based sniffer.
A: You may have noticed that, while using the PROCESSLIST-based sniffer, SQL DM for MySQL increases the load on the CPU as well as the I/O subsystem of the system on which it is installed - even when the MySQL server is idle. Don't panic: it's normal. When using the PROCESSLIST-based sniffer, SQL DM for MySQL continually queries the MySQL server at the end of each time interval, which can be specified by you. It then retrieves the results and stores them in an internal sniffer database before displaying the results back to you. Now, if you set a very short time interval, one that almost approaches 0, then in actuality SQL DM for MySQL will almost be stuck in an infinite loop! Consequently, the load on the CPU and I/O subsystem will increase exponentially. We generally recommend an interval of not more than 0.1sec times the number of servers for which Processlist-based sniffers are enabled. However, if you're worried that you may miss out on some important queries running on the MySQL server, use the Performance Schem or MySQL Proxy mode. The LUA script supplied with SQL DM for MySQL should handle the task for MySQL proxy. For more information on using MySQL Proxy with SQL DM for MySQL, click here.
...
23. Why is display of queries truncated in Query Analyzer?
A: When using Query Analyzer feature, you may notice that sometimes queries displayed in output are incomplete. This may be due to one of the two known causes:
...
24. The servers that I have registered do not display. What is wrong?
A: Check if the server is filtered based on a particular state, change your server filter to All Servers and now you will be able to see your server amongst the servers if you had successfully registered it. You can also use the search bar next to the server filter to search for your server name or tag name to get to your server.
...