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

Forum Replies Created

Viewing 15 posts - 226 through 240 (of 642 total)
  • Author
    Posts
  • in reply to: SJA DB Structure Recomendations #16125
    Shadow
    Member
    Quote:
    about primary keys, does sja have any problem if I define mor than one Primary Key on a Table??

    You cannot define more that one PK per table (error 1068), it is impossible to do so in all RDBMs, as a PK uniquely identifies a record. But a PK may have multiple fields, and sja will handle those PKs perfectly.

    in reply to: SJA DB Structure Recomendations #16122
    Shadow
    Member

    Sja has only one requirement: primary key must be defined for all tables that you want to sync. The speed of the sync is influenced by the structure of tables, but there is no sja specific recommendation as sja uses standard SQL commands to retrieve and manipulate data.

    Therefore in case of InnoDB tables sja honors the foreign key restrictions (in fact, it is not sja, the InnoDB table handler does the job), but sja can be instructed to turn FK checks off while syncing. This is highly recommended as it is difficult to force sja to sync tables in a particular order.

    in reply to: Error 2003 #16117
    Shadow
    Member

    SSL is the root of the problem. Check out this topic!

    in reply to: GUI SQL Query Builder #16120
    Shadow
    Member

    SQLyog MAX is planned to include the suggested developments. Please, check out MAX's roadmap in this forum!

    in reply to: convenient feature suggestion #16119
    Shadow
    Member

    SQLyog MAX will contain completely rewritten data manipulating tools.

    in reply to: Error : MySQL server has gone away #16108
    Shadow
    Member

    You should try increasing max_allowed_packet variable in the config file.

    in reply to: SSH Tunneling??? #16089
    Shadow
    Member

    What if you try, for example, the word 'tunnel'? You'll get what you are looking for…

    I paste this link from one of the found topics.

    in reply to: can sja do this sync? #16102
    Shadow
    Member

    The second method would be truly better, but how do you plan to time the execution of the notification job (how do you detect the completion of the sync job)?

    Quote:
    ja apparently locates the password needed for connecting to the SOURCE MySql in a syncjob in a wrong way. It seems to locate the first psw node with data regardless of the node's relative position…

    I joined a syncjob and a notification job in a single xml file. When SJA parses the file, it apparently takes the value of the first psw node that contains any data (nodeTypedValue<>“”) as the password of the SOURCE db even if that node is located in the other job (notifyjob). Otherwise, it could work… Ritesh, consider this as a feature request!

    in reply to: can sja do this sync? #16099
    Shadow
    Member

    I tried it out and found it impossible to execute a job file containing two different queries successfully. Either only the notification job was executed or the sync job failed saying “Lost connection to MySql server during query” (2013). Sja apparently locates the password needed for connecting to the SOURCE MySql in a syncjob in a wrong way. It seems to locate the first psw node with data regardless of the node's relative position…

    in reply to: can sja do this sync? #16098
    Shadow
    Member

    Well, not directly, but it can be done. All you need to do is to set up two syncronization sessions. One will sync tA to tB and the other one will sync an empty table to tA (since the source table is empty, none of the rows in tA will have a matching record and therefore each row gets deleted). This method is not too fast as the deletion is done row by row. As an alternative, you may use notification service's maintenance query tool to time the execution of a TRUNCATE TABLE statement.

    Ritesh: Is it possible to put two jobs of different type (a data sync and a notification) into one xml file?

    in reply to: Can't connect #16092
    Shadow
    Member

    The error 2003 (10061) has been extensively discussed in this forum several times. It means that MySql client does not find any running MySql server on the target machine.

    in reply to: Column Changes #16095
    Shadow
    Member

    1. Sja updates ALL monitored columns if a change is detected in any of them. Simply check out the binary logs to see what it does to the data.

    2. We used to run updates to 15 remote offices every day over 128Kbit leased lines with sja and it worked fine for us (we switched to Oracle). However, none of the updates ever exceeded 2MBytes.

    in reply to: import problems from sybase ASE #16062
    Shadow
    Member

    benito may have considered MAX's public beta as v4, it does not have ODBC import functions, yet. Unfortunately, I can't repeat an import involving thousands of records…

    in reply to: schedule backup #16084
    Shadow
    Member

    3.11 was designed to work with MySql 3.x and misses some features added when SQLyog turned commercial. Get a 30 day trial and see if it does the required job!

    in reply to: Updating source problem #16080
    Shadow
    Member

    I tested the sync on v4.1.0 and no, the trial version of SQLyog does not have any restriction apart from the time limit. SJA does not have any restrictions either!

Viewing 15 posts - 226 through 240 (of 642 total)