Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 15 posts - 46 through 60 (of 110 total)
  • Author
    Posts
  • in reply to: Setup – Ssh Server Details – Linux Specifically? #24594
    Rohit
    Member

    We will be providing “official” support for other Operating Systems soon

    in reply to: Rc1 Bugs And Suggestions #24596
    Rohit
    Member
    brashquido wrote on Jul 31 2007, 07:09 PM:
    Hi guys,

    Very impressed with 1.0 RC1, I especially like the email feature that details problem areas with MySQL and emails them to you at set intervals. Genius!

    Thanks!

    brashquido wrote on Jul 31 2007, 07:09 PM:
    1) Missing DLL on W2K3 Server. I can't remember the name now, but there was a missing DLL file reported during installation when the command window is displayed. I'll post the DLL name when I get home tonight.

    We have tested it extensively on Win2K3 but will test it again on Win2K3. What is the Service Pack version? The DLL name would be very helpful.

    brashquido wrote on Jul 31 2007, 07:09 PM:
    2) Ability to use existing webserver to view details from an existing webserver (IIS, Apache, etc)? I would like to be able to intergrate MonYog with my exisitng IIS server so that I can view the status of my MySQL server from anywhere, as well as have greater control on access an be able to secure it with SSL.

    No plans right now – but interesting idea. You can still view your MySQL server from “anywhere” using MONyog web-server. We decided to write our own HTTP server from scratch to make the installation dead-simple! Other monitoring tools install Apache, Tomcat, PHP, JDK and ask 40 questions before getting started 😉

    brashquido wrote on Jul 31 2007, 07:09 PM:
    3) Analysis of log files. At the moment MonYog looks at only the live status of a MySQL server. Inparticular I am thinking about the slow query log, especially when logging tables with no indexes option is set. The problem I have (and I'm sure any other server environment with multiple web apps and databases) with scanning my logs for slow/non indexed queries is that there are literally tens of thousands of entries, and at present I am using a few scripts to try and collate that so that I only see each slow/non indexed query once with a count of how many times that query has occured. Would it be possible to be able to put some basic log parsing into MonYog so that it could so something like this?

    Already working on this! Pls. wait for Version 2.

    brashquido wrote on Jul 31 2007, 07:09 PM:
    4) When opening MonYog you have to select a server every time. Would it be possible to be able to select a default server that MonYog connects to when starting up?

    We do retain the selected servers across sessions. Am I missing something? You can directly go to “Show All”, “Dashboard”, etc.

    in reply to: Very Nice Program #23428
    Rohit
    Member

    Thank you!

    sqletom wrote on Jul 31 2007, 05:12 PM:
    Clearly there are some things you still need to add, but this is a great first step.

    Could you point us to those “missing” things?

    in reply to: Sja For Linux — Http Tunneling #24556
    Rohit
    Member

    Workaround:

    How about using ssh for port forwarding? You can create a shell script that makes the connection just before you start sja.

    in reply to: Tunneling ? #24491
    Rohit
    Member

    Yes, you are right.

    MONyog does not support SSH tunneling out of the box. We are going to build it soon.

    As a workaround, you have to use a 3rd party app like Putty for tunneling.

    in reply to: Sql Server – Blob Issue #24356
    Rohit
    Member

    Can you try 6.03? We have actually fixed a blog issue recently.

    in reply to: Illegal Mix Of Collations #23888
    Rohit
    Member

    I think Ron wants to avoid typing “SELECT * FROM..”

    in reply to: Illegal Mix Of Collations #23886
    Rohit
    Member

    @ronjeremy_69

    I tried the following workaround and it worked great for me!

    1. Enable “Show results in Text”

    2. Select the table and press Ctrl+Shift+S

    3. Press F5

    This was quite fast for me!

    Am I missing something?

    in reply to: Illegal Mix Of Collations #23883
    Rohit
    Member

    @ronjeremy_69

    You persistence is amazing!

    I will speak to the SQLyog team to find out the effort required.

    in reply to: Got The Stats…now What #24289
    Rohit
    Member

    We are planning to improve the documentation/advice before going GA.

    Rohit
    Member

    I think Peter wants you to try 6.03 and not 5.03 🙄

    in reply to: Thanks Sqlyog – I M Now Using Sidu #24228
    Rohit
    Member

    Congratulations!

    It is a great compliment for us to know that you are getting “inspired” by SQLyog 🙄

    BTW, SQLyog runs great on Ubuntu and thousands of users are using it. We are also planning to link it with a custom build of Wine – just like Picassa for Linux.

    Check this out:

    http://www.flamingspork.com/blog/2006/09/12/sqlyog-on-wine/

    http://www.opensourcetutor.com/2007/06/01/…sty-fawn-theme/

    in reply to: Sja Crashes… #24074
    Rohit
    Member

    1. Did you start facing this issue only after upgrading to SQLyog Enterprise 6? If not, which version of SQLyog Enterprise were you using before 6.0?

    2. Are you using a shared hosting environment? Are you sure that the server is not restricting resources after serving a certain amount of load?

    3. Lets start using the Ticket System at http://www.webyog.com/support. Pls. create a new ticket and attach the log and dump files after zipping them.

    in reply to: Problem With Utf8 #23902
    Rohit
    Member

    The new RC(RC1) has fixed this issue.

    Please confirm!

    in reply to: Slow Query Log; Full Table Scans #24022
    Rohit
    Member

    log_slow_queries is a MySQL system variable that defines whether slow queries should be logged. More info is available at http://dev.mysql.com/doc/refman/5.1/en/slow-query-log.html.

    MONyog.MySQL.GlobalVariables.* is just a read-only encapsulation of MySQL system variables. So you cannot change the value from MONyog. To change the value of log_slow_queries, you have to change the corresponding my.ini or my.cnf.

    The metric displayed for full table scans is obtained by parsing the results from “SHOW GLOBAL STATUS”. You can see the exact formula used for calculation by bringing the mouser over “Percentage of Full Table Scans”. We are using the Handler_* system variables to find out the total number of rows read via full table scans compared to the sum of Handler_* variables which denote all row accesses

    We are not parsing the slow query log yet. So MONyog does not give you an interface to identify the slow queries. We are working on that and the next major release will have a slow query log parser.

Viewing 15 posts - 46 through 60 (of 110 total)