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

Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • in reply to: Proper Executable Version Identification #32025
    ruirib
    Member
    'peterlaursen' wrote:

    Issue confirmed. Actually there are similar issues with sja.exe and some dll's.

    My theory is that it happened when we started using Visual Studio 2010, but we will check this.

    Yes, that would seem a likely cause.

    Thank you for your reply :).

    in reply to: Problems With Data Import #30809
    ruirib
    Member
    'Rohit' wrote on '02:

    This is very strange. We don't have a similar report elsewhere

    Can you try the same import with an old copy of SQLyog? From you description it looks like the problem has cropped up recently.

    Anything else you can do to help us reproduce the problem? Can you attach some sample cases by creating a private ticket at http://www.webyog.com/support

    In the meantime, we will try to reproduce your problem in a similar environment.

    Can you tell me the following info?

    1) Size of the SQL dump

    2) Structure of the target tables

    3) Target MySQL version

    4) Innodb or MyISAM tables (Insert on Innodb is sometimes slower than MyISAM)

    If we can reproduce the problem, we guarantee a fix within 72 hours.

    Hi,

    Thank you for your reply.

    I was very surprised with this, as I have transferred a few databases and some with sizes of up to 1 GB and never felt this was too slow. This was with a dump file with just 40 MB and it took a lot of time. Also, these were MyISAM tables.

    Anyway, I found a solution – I started using the Compressed Protocol. Surprisingly, something that was taking hours, took less than 3 minutes! Have tried a few times afterwards and it's always been that fast. Also, I have tried one of the biggest tables in the problematic database and was able to transfer it to another server very fast, without using the compressed protocol.

    So, whatever it was, was related to the server I was uploading to and the compressed protocol resulted in amazingly fast transfers. I don't know why the help about compressed protocol advises against its use (well, almost). I used it as a last resort!!!! Seems I will be using it a lot more.

    Anyway, problem solved.

    Thanks for a great product smile.gif.

    Regards

    in reply to: Configuration File Lost #30528
    ruirib
    Member
    in reply to: Mysql Yog Through Proxy #23120
    ruirib
    Member

    Thank you.

    in reply to: Mysql Yog Through Proxy #23118
    ruirib
    Member

    I'll wait 🙄 .

    Thank you.

    in reply to: Mysql Yog Through Proxy #23116
    ruirib
    Member
    peterlaursen wrote on Dec 20 2006, 02:11 PM:
    No there is nothing to 'enable' if I understand your question right. No configuration on the host/network where the MySQL is, is required.

    Technically (from a programmer's perspective) it is almost the same wheter you connect to a HTP server on a remote host/network (and connct to a MySQL server from here) or whether you connect to a Proxy server on your local network and connect to a MySQL server from here. That is why we have arranged this where it is.

    The easiest would be to try!

    I've tried it, but didn't upload SQLYogTunnel.php to the server. My question is, this upload is still needed? Or, putting it differently, the tunnelling option needs to be checked, right?

    Speed wise, how does HTTP tunneling behave? Is a slowdown very noticeable?

    Thx for your replies.

    in reply to: Mysql Yog Through Proxy #23114
    ruirib
    Member

    Yes, but doesn't tunneling need to be enabled to use proxies too?

Viewing 7 posts - 1 through 7 (of 7 total)