It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
domgrief: Your best bet, honestly, is to download a whole bunch of them and see which one makes the most sense to you. The user interfaces for DB tools vary widely, and each different tool reflects to some extent the mindset of its developers. One of them will probably "feel right" to you more than the others.
Thank you very much for answer. Well, I am aware that every application can be different and it'll be hard to find the right one. On the other hand, installing and testing "everything on the web" will leave probably some nice amount of leftovers after uninstallations as this is not the perfect functionality of programs in most of cases. I am trying to find the best option by also trying minimize number of applications to test to 2 max.

avatar
domgrief: As well as Workbench, Quest Software's Toad for MySQL is free, and is popular with some of my colleagues, though it has more of a "toolkit" type approach than most of the other tools.
What I've heard/read about Toad is that it can be slow with bigger databases and I'm going to have such one.
Is someone able to tell me:
- what is the difference between HeidiSQL setup / portable versions? is the only one method of installation (installer exe / unpack zip)? can I still use latest exe build with portable?
- the same question about exe / zip for Workbench? also, as zipped version is not marked as portable: does it do any changes in registry?
- do character encoding problems in HeidiSQL still exist? or were they in some older versions?
Post edited January 13, 2012 by Lexor
Found the answer for my first question here:
How does HeidiSQL portable exactly work?
r3201 implements additional code into heidisql.exe, which checks for a "portable_settings.txt" file in the same directory. If present, heidisql.exe will read any settings from this file into a unique registry key, without interfering any running Heidi process or even other running portables. When you close the main window, settings will be written to the above mentioned text file and the registry key gets removed.

This way, the user is able to create its own portable with any build (ok, any later than r3201), just by placing an empty textfile into the same directory.
Very clever, I must say.

Still looking for answers for my two others questions.
avatar
domgrief: As well as Workbench, Quest Software's Toad for MySQL is free, and is popular with some of my colleagues, though it has more of a "toolkit" type approach than most of the other tools.
avatar
Lexor: What I've heard/read about Toad is that it can be slow with bigger databases and I'm going to have such one.
This really depends on what you're trying to do.

If you're looking for the tool which has the best "open this table with 1,000,000 records for editing, similar to the behaviour of an Access database" feature, you may be able to post a specific question about that on the MySQL Community forums and get a pretty good answer.

If you're using SQL and set theory to manipulate your data:

SELECT * FROM MyTable WHERE DATE_CREATED BETWEEN '2012-01-01 00:00:00' AND '2012-01-31 23:59:59' AND IS_ACTIVE = 1 LIMIT 10000

UPDATE MyCustomer SET DISCOUNT_PCT = 10 WHERE EXISTS (SELECT SUM(Subtotal) FROM MyCustomerHistory WHERE MyCustomer.CustID = MyCustomerHistory.CustID HAVING SUM(Subtotal) > 10000)

(My SQL may be crappy but please cut me some slack as I am making it up on the spot)

Then you're letting the database server doing all of the work. A query that returns 1,000 rows will feel exactly the same in Toad, MySQL Workbench, HeidiSQL, etc., whether the query is running against a 10MB database or a 1TB behemoth.
avatar
domgrief: This really depends on what you're trying to do.
Yes, of course. This article I was reading was mentioning about Toad in relation to backup or moving data to other database. During test, author of text noticed that Toad had some problems with over 40MB file of sql backup. As my current backup of "relatively" small forum has already nearly 30MB it is kind of useful comparison. I'm rather not going to use SQL windows front very often, more like to maintenance data or to test new www queries, but I still would like to have tool with no such troubles (just in case when I'll suddenly need that).