Recommendations to others considering SQLyog:
If you're not using an SQL editor yet, give this a try. It's easy to set up and I found it very useful while working with large amounts of data. Review collected by and hosted on G2.com.
What problems is SQLyog solving and how is that benefiting you?
While working on a statistic analysis package for Southampton FC, the engineers on my team had to parse all of the player football statistics for every player in the Premier League. They managed to refine it into a subsection of stats that were most useful and it was up to me to write the queries that would investigate those statistics and represent them as histograms, donut charts and spider graphs within a bespoke piece of software that we were writing.
As a designer, I wasn't the most suited to writing complex SQL queries, but nevertheless it was my job. So I used MySQL to help visualise the queries I was writing, to test their results and to see where things were going astray. For example, if my query was supposed to return an image of a player and that image wasn't showing up in the editor, I would debug and find out exactly what was being returned. It helped me find the bugs quicker than if I used a traditional editor.
On top of that, since a lot of these bugs stemmed from similar origins, I was able to make great use of saved queries and also to mimic the data ingestion process by running batches of more complicated queries, thereby simulating the running environment. This saved me hours upon hours of mind numbing repetition. Life saver. Review collected by and hosted on G2.com.