[Ritesh]

mhsa wrote on Jun 19 2003, 01:35 PM:

Using version 3.5…

When I 'Execute Batch File', three things *don't* happen that I expect, and I'm not sure whether that is by design or not. They are:

• Statements are not logged to 'History' tab. The only exception I've found so far occurs when the script includes a 'use xxx;' statement. Those are logged to History as 'select database()' (internal SQLyog method?). I expected the individual statements to be logged to History.
• MySQL output is not logged to 'Messages' tab.
• Dataset(s) not displayed in the 'Results' tab.

Is there any effort to integrate the 'Execute Batch File' with the query window, etc.?

Thanks!

Zack

All the three points are by design only. The Execute Batch File… option is used primarily to restore your database which is stored in SQL Scripts. The size of the file is limited by OS that can go in GBs, and SQLyog will execute all the SQL in the file without any performance penalty.

If you want to get all the message(s), result(s) etc. then you can open the file in the editor using File->Open… and execute all the queries by using Shift+F5 option.

HTH

[Ritesh]

Data sync is in the TO-DO list of SQLyog Max

[Ritesh]

Thanks.

[Ritesh]

Use Tools->Execute Batch File… option 😀

HTH

[Ritesh]

Use Tools->Execute Batch File… option 😀

HTH

[Ritesh]

From the MySQL Docs –

Quote:

For the moment, OPTIMIZE TABLE works only on MyISAM and BDB tables. For BDB tables, OPTIMIZE TABLE is currently mapped to ANALYZE TABLE. See section 4.5.2 ANALYZE TABLE Syntax.

You can get OPTIMIZE TABLE to work on other table types by starting mysqld with –skip-new or –safe-mode, but in this case OPTIMIZE TABLE is just mapped to ALTER TABLE.

Guess…thats the problem 😀

[Ritesh]

Please send a mail to [email protected] with your requirements ( no. of licenses etc. )

[Ritesh]

Which version of MySQL are you running? Can you paste the SQL from the History Window out here?

[Ritesh]

If you want to just change the Table Handler, select the Table in the Object Browser and select Change Table Type To -> InnoDB from the popup menu.

HTH

[Ritesh]

Greetings

We are coming out with SQLyog 3.5 very soon which is completely 3.22 compatible. Keep checking Our Site for more news.

[Ritesh]

Quote:

when a try make de change

What type of change do you mean?

[Ritesh]

This is a MySQL Error.

SQLyog logs all the query that it uses in the History Tab. SQLyog will stop executing queries when it faces an Error while dropping a relationship. Check out the History Tab for a series of Queries that SQLyog has executed and you will be able to point out the query that is causing the error.

HTH

[Ritesh]

The Database Synchronization Tool ( DST ) generates SQL statements, to bring the strtucture of table(s) for a database ( i.e. columns, indexes etc. ) completely in sync with another.

Data Sync is not supported as of now but it is in the TO-DO list of SQLyog Max

HTH

[Ritesh]

This feature is in the TO-DO list for SQLyog Max 😀

HTH

[Ritesh]

We are coming out with a new version of SQLyog i.e. SQLyog 3.5 later this week 😀

HTH

[Author]

Posts