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

Forum Replies Created

Viewing 15 posts - 31 through 45 (of 78 total)
  • Author
    Posts
  • in reply to: Sqlyog Crashes When Trying Show Table Data #23852
    adarsh
    Member

    Hello,

    We are not able to reproduce here.

    Please attach the table structure with some sample data.

    Thanks

    Adarsh

    in reply to: Wrong Handling Of Ampersand #23847
    adarsh
    Member

    Hello,

    Issue is fixed in our development tree.

    Adarsh

    in reply to: Sqlyog V6.0 Beta 4 #23824
    adarsh
    Member

    Hello,

    Thank you for reporting.

    The column width resizing issue is confirmed and we will fix this in next beta.

    This is a first beta for query builder later we planned to add more features and we will consider your suggestions and features also.

    Thanks

    Adarsh

    in reply to: Query Builder In Community Version? #23812
    adarsh
    Member

    Hello,

    Query builder is not available for community version it is available only in Enterprise and Enterprise Trial versions

    Adarsh

    in reply to: Sqlyog Crash #23796
    adarsh
    Member

    Hi,

    We have identified the problem.

    If you enable the “Log Queries in history tab” SQLyog adds every query in the history tab that you execute during the batch process.

    But if you have more and more queries, the history tab size also increase and gradually reaches the point of saturation and crashes.

    In your case too, the SQL dump is pretty big and so the history tab memory usage increases with every query thats get executed by the batch process and eventually crash at some point of time.

    If you uncheck the 'Log Query(s) in History Tab during batch process' option in the Preferences I think it will work smoothly.

    So try doing that and let us know the details.

    Between, we are also trying to come up with a solution for the same.

    Adarsh

    in reply to: Sqlyog Crash #23795
    adarsh
    Member

    Hi,

    Thank you for reporting.

    Finally we are able to reproduce it.

    We will fix this issue in our next release.

    Thanks

    Adarsh

    in reply to: Umlaut-problem With Beta 3 #23797
    adarsh
    Member

    Hi,

    Thank you for reporting.

    Issue is confirmed we will fix this in beta4.

    Adarsh

    in reply to: Sqlyog Crash #23792
    adarsh
    Member

    Hi,

    Please attach the sample sql dump of the database which is crashing.

    And also attach the SQLyog crash dump (saved in SQLyog installed folder) so that we can analyze that crash dump and we can find reason for crash.

    Quote:
    I'll give you the download link.

    SDB for TBC 3478

    This link is not working there is no sdb.sql file in this link.

    Thanks

    Adarsh

    in reply to: Feature Wishes And Possible Bug In "migration Toolkit" #23784
    adarsh
    Member

    Hi,

    To uncheck the import index option from adcvance properties first you should disable the import foreign keys option and then you can disable the import indexes optiion.

    in reply to: Remote Ssh Tunnel Remote And Local Issue #23772
    adarsh
    Member

    Hi,

    Quote:
    REMOTE CONNECT

    MySQL TAB:

    MySQL Host Address localhost

    User Name root

    Port 3306 Default Charset [default]

    SSH TAB:

    Username root SSH Port 22

    SSH Host xchg.com Local Port 3306

    LOCAL CONNECTION

    MySQL Host Address localhost

    User Name root

    Port 3306 Default Charset [default]

    I think I got the issue. You are using port 3306 as “local” port in SSH tab. Pls. use a different value than 3306.

    That is the reason why you are not able to access MySQL after starting SQLyog. MySQL is no longer able to “listen” on Port 3306.

    All Webyog products come with a 90 day money back guarantee. If you are a registered Enterprise user, you should use the ticket system for priority support.

    http://www.webyog.com/CustomerArea

    in reply to: 6.0 Beta 2 – Massive Cpu Load While Idle #23775
    adarsh
    Member

    Hi,

    We fixed this issue in SQLyog6.0 beta3 and we released today.

    http://www.webyog.com/forums//index.php?showtopic=3169

    Thanks

    in reply to: Remote Ssh Tunnel Remote And Local Issue #23767
    adarsh
    Member

    Hi,

    Which version of SQLyog are you using? Have you tried the latest 5.29?

    Adarsh

    adarsh
    Member

    Hi,

    We have installed that Data Direct ODBC driver and we tried to import we got same error, it is importing tables without keys.

    After this we tried using ASE 15.0 ODBC driver it is importing all the tables with keys.

    So this is a driver issue, please try to find someother driver or you can do one thing, you install that ASE 15.0 in your Win2k system with ODBC driver through custom install and then create a DSN it will work.

    Adarsh

    in reply to: Select 1 Returns Wrong Results? #23736
    adarsh
    Member

    @Donna:

    I checked with your test case.

    Both MySQL client and SQLyog return an empty result set. In case of SQLyog, it returns the column headers even for an empty result set. MySQL client does not return column headers for an empty result set.

    So the “1” that you see is the column header – the resultset is empty.

    in reply to: Primary Key Or Constraints Problem #23666
    adarsh
    Member

    Are you using ASE 12.0 server with ASE 15.0 driver?

    If you don't want to uninstall that ASE 12.0 server then please install ASE 15.0 server with driver in another machine and then try. In windows i tried it is working fine.

Viewing 15 posts - 31 through 45 (of 78 total)