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

Forum Replies Created

Viewing 15 posts - 2,461 through 2,475 (of 7,398 total)
  • Author
    Posts
  • in reply to: #27800
    peterlaursen
    Participant

    We will not discuss private details in a public Forum. Please create a support ticket here: http://www.webyog.com/support and we will sort things out.

    My best guess is that you have used two different emails for purchasing the original and the upgrade (and now are checking with the email used for the oldest purchase!). We can (and should) merge the two accounts if this is it.

    So let's continues in support ticket system, please!

    BTW: Mike is on Holdiday for a couple of weeks (he is marrying actually).

    in reply to: #27789
    peterlaursen
    Participant

    PLEASE attach a test case (two small dumps + a jobfile). We need to *reproduce it exactly*. WORDS won't bring us anywhere!

    in reply to: #27787
    peterlaursen
    Participant

    OK!

    In your first post you wrote “This same job file works with sja 6.56.”

    Is there a MySQL 3.x or 4.0 server involved? Data sync with SQLyog/SJA 7.x requires MySQL servers 4.1 or higher! The speed improvements in 7.x require server functionalities now existing in those early server versions. For those you need to continue using 6.56. But you also tell it works with other tables, so I am not sure it is the issue! But please tell what versions are servers (both source and target) ?

    If it is not the problem with the server version we need a test case (as we already requested in our first reply). A single table with a few rows of dummy data will do! Please create such case and zip into one file and attach here – more words will not bring us further.

    in reply to: #27696
    peterlaursen
    Participant

    We have fixed this now. It was our mistake.

    Unles you require a fix with priority we will only include in next release (whether this will be 7.13 or 7.5 beta1) in order not to trouble other users with it. Estimated timeframe about 2 weeks for this. But tell if you need the fix – we can then either give a private build or release 7.13 with this fix only.

    in reply to: #27738
    peterlaursen
    Participant

    Issue with sftp_read() function in SSH library confirmed on 32bit Linux (Windows and 64 bit Linux not affected). I understand that we are also close to fixing it.

    in reply to: #27780
    peterlaursen
    Participant

    The messagebox popping up should tell the filename and path!

    But it is in the SQLyog 'AppData' folder (where also the sqlyog.ini is)

    in reply to: #27785
    peterlaursen
    Participant
    Quote:
    “Isn't there some way to get the SQL query logged”

    yes .. use the option to generate sync script instead of syncing directly! In XML joblfie you specify this after tag like

    Code:

    C:UsersPeterDesktopsyncscript.sql

    (use Windows or Unix file syntax depending on the OS for tag)

    in reply to: #27778
    peterlaursen
    Participant

    No .. if you kill the sqlyog process there is no crash dump. Only if some exception occurs in our code or in linked libraries there is.

    We will try to reproduce this 'hang'. Also the recovery option we will discuss of course.

    in reply to: #27776
    peterlaursen
    Participant

    if you encounter a crash please always report it like this:

    1) tell steps you were performing

    2) attach the crash-dump that was generated

    in reply to: #27766
    peterlaursen
    Participant

    I do not believe SJA will use socket. It will use TCP only. Try using host '127.0.0.1´and not 'localhost'.

    Maybe same problem as described here:

    http://webyog.com/faq/content/23/36/en/i-g…t-connect-.html

    in reply to: #27763
    peterlaursen
    Participant

    I am not sure why your example does not work. Maybe the empty line in your file or some details with a tag. I will ask the SQLyog team to check!

    But this works for me and your table example (but of course you must adjust hosts, user and database names etc.).

    Code:






    localhost
    root ******* 3306 syncsource


    localhost
    root ******* 3306 synctarget

    `auth`




    In this example you see tags introduced in 6.5 and 7.0. If you run with a SJA version that does not know those, they will be ignored. If you omit them defaults will be used. And that is what we should document basically: what tags apply and not at least what tag defaults are (but tag defaults for recent versions are chosen so that recent versions are backwards compatible with early versions). And besides the wizard should generate database names that are `backticked` .. and the exampes shipped with the program should be updated (in particular for Data Sync)! SSL parameters do not apply with SJA for Linux and were omitted in the above example (but as told they are – or should be – ignored if they are there).

    You can download SQLyog ENTERPRISE TRIAL (works on Windows and Wine) and build your own collection of SJA templates with the wizard!

    in reply to: #27715
    peterlaursen
    Participant

    We believe we have fixed this in 7.12 just released. Can you verify?

    in reply to: #27772
    peterlaursen
    Participant

    hmmm .. are you aware that you can open multiple query tabs? (Ctrl+T)

    Won't it solve to open two query tabs and execute one query in each? Note that the result set(s) for each query tab are 'sticky' – so the result tab(s) for every query tab displays with the query tab.

    in reply to: #27771
    peterlaursen
    Participant

    How long did you wait?

    Please try to wait very long time (like 10-15 minutes) once. We have reports that (reported with specific wireless routers) it happens that connection is interrupted after some period of inactvity. That is normally no big problem (though an incorrect behaviour of such systems), because SQLyog will then reconnect — but also we have a few reports that then the reconnect takes minutes. If this is what is happening then HISTORY will have a record like “SQLyog reconnected”.

    You can also check by executing SHOW FULL PROCESSLIST before and after if the old connection thread is still running in server.

    And finally check the returns of SHOW VARIABLES LIKE 'wait_timeout'. If this is low then it may be the server that terminates the connection, but should still be now problem if immediate reconnect was possible.

    Finally if you have an option to try from somewhere else/using another network connection/equipment, please try. Also check for firmware upgrades to routers, modems etc. (if that is the problem).

    in reply to: #27770
    peterlaursen
    Participant

    yes .. jobfiles are interchangable across platforms with the exceptions listed here:

    http://webyog.com/faq/content/15/47/en/is-…or-windows.html

Viewing 15 posts - 2,461 through 2,475 (of 7,398 total)