On the download page you will find the executable for each SVN commit in the HeidiSQL repository. The executables are processed in conjunction with a SVN post commit hook. I just extended this process so it also creates the installer with that executable, using a InnoSetup command line. This way, users who need a full installer and also want to use the latest build can do that in one download.

Thanks to Jordan Russell for that excellent, free InnoSetup.

There are several ways to implement sharding in your application. The first and by far the most popular, is to implement it inside your application. It can be implemented as part of your own Data Access Layer, database driver, or an ORM extension. However, there are many limitations with such implementation, which drove us, at ScaleBase, to look for an alternative architecture.

As the above diagram shows, ScaleBase is implemented as a standalone proxy. There are several benefits to using such an architecture.

First and foremost, since the sharding logic is not embedded inside the application, third party applications can be used, be it MySQL Workbench, MySQL command line interface or any other third party product. This translates to a huge saving in the day-to-day costs of both developers and system administrators.

Backup can be executed via the proxy, and so allows users to consistently backup a sharded environment – not …

Update: Thank you all for making this campaign a colossal success. We are extending this offer till Dec 2nd, 23:59 PST. Many corporate users requested us to extend the offer as they require time to get official approval. Pick your copy right now! Use coupon code blkfrdy11 to get 50% off.

–

Happy Thanksgiving!

Black Friday is back with a bang. Get a flat 50% discount on all Webyog products. Yes, you read it right, a flat fifty percent discount. Hurry, this offer expires Nov 28th Dec 2nd, 23:59 PST. Use coupon code blkfrdy11 to avail the discount on any purchase. Buy Now.

Still using SQLyog Community Edition?

Upgrade to the feature rich SQLyog Professional/Enterprise/Ultimate Edition. This offer is literally too good to pass up. …

MySQL Workbench 5.2.36 is now out and brings a lot of improvements across the board, with special focus on the Query Editor. We’ll cover some of that here:

Redesigned Query Editor

• • The log of executed commands and server responses is now always visible while resultset grids and the query editor can be resized according to your needs. Resultsets are also grouped in the same tab as the query editor that generated them.
  • SELECT queries are now analyzed as in the old MySQL Query Browser tool and, if possible, its resultset can be edited in the grid. If the resultset cannot be edited, you can place the mouse over the ReadOnly label and view the reason.

• Improved snippets manager and editor, allows having snippets list always at hand, while editing can be done without disrupting work on the main query area.

Users of MS SQL servers may find it useful to connect to their server via Windows authentication. The login dialog disables username + password in that case, as these are not required (indeed ignored by the server). The old option "Prompt for credentials" is now mutually exclusive to the new checkbox option "Windows authentication". Makes no sense to prompt for user+pass which then are ignored by the server. The connection dialog has grown a bit in its minimum height, as now the mentioned two checkboxes need vertical space. Well, features need space.



For MySQL sessions this checkbox is disabled. Although there is a MySQL server plugin which allows Windows authentication, the difference to MS SQL is that MySQL still asks for a username - only the password can be blank in that …

Users of MS SQL servers may find it useful to connect to their server via Windows authentication. The login dialog disables username + password in that case, as these are not required (indeed ignored by the server). The old option "Prompt for credentials" is now mutually exclusive to the new checkbox option "Windows authentication". Makes no sense to prompt for user+pass which then are ignored by the server. The connection dialog has grown a bit in its minimum height, as now the mentioned two checkboxes need vertical space. Well, features need space.



For MySQL sessions this checkbox is disabled. Although there is a MySQL server plugin which allows Windows authentication, the difference to MS SQL is that MySQL still asks for a username - only the password can be blank in that …

Wine users reported this a couple of times in HeidiSQL's bug tracker, and also on WineHQ there were several reports for the same thing found: black color on icon areas which should be transparent. Cosmetic though quite annoying for a GUI which provides important buttons on a main toolbar. Wine 1.3.33 says this is fixed now, as stated on WineHQ.

This is the third blog post in a series designed to assist companies who wish to migrate their code from Oracle to MySQL. You can read the previous post here.

I went over some of the difficult topics you’ll face when migrating from Oracle to MySQL. However, I left out the topic of database scalability (after all – this is a ScaleBase blog).

Oracle users are used to having a very clear scalability path. You start with an Oracle Standard edition, and if your budget allows, you increase hardware (memory, CPU), improve your storage speed, buy Oracle Enterprise edition and use portioning. If all that fails, you move to a distributed RAC environment. If you’re really on the high end, you buy ExaData2. This is where your journey ends. There is nothing “better”.

That’s great for enterprise …

This is the second blog post in a series designed to assist companies who wish to migrate their code from Oracle to MySQL.

In the first post of the series I tried to explain why you would like your web platform to run on a MySQL database, and not on an Oracle database. In this post, I’ll try to focus on the changes that you need to plan for when migrating from an Oracle environment.

Code

Probably the most obvious change is in code. There is no way around it – you’ll have to change your code.

1. SQL statements.
   While ANSI SQL 92 is a standard, Oracle offers extensions to the spec – and those are used by most developers, sometimes without their being aware of it.
   Of course, when moving to MySQL, those SQL statements will need to change. Some will require only minor …

This is the first blog post in a series designed to assist companies who wish to migrate their code from Oracle to MySQL.

During the World War II “Battle of the Bulge”, General McAuliffe said to the German forces who asked for his surrender: “Nuts!” The rest is history – he won the battle, and the allied forces won the war.

Some things are like that. So absurd that “Nuts” is the only possible reaction. And frankly – running your web infrastructure on an Oracle database is one of those things.

Now, the pricing issue is very well covered. Just see here. And for most people, this should be enough. We had a customer migrating from a 7M USD environment to a 200K yearly environment (licensing and support) – definitely worth the migration hassle!

But it’s not …