We wish all our customers, users and partners a Merry Xmas and a Happy New Year.

The year of 2011 has been a terrific year for us.  But first let us have a look at where we started 10 years ago. The first version of SQLyog was released in the spring of 2002 – what will mark our 10 year anniversary as a company early next year. In the period since then we have seen quite a lot of other MySQL clients come and go. We are happy to see most of our existing customers upgrade regularly, to see our user base increase, and we are happy to do our best to provide the solutions requested by users and to keep pace with MySQL development.

And also 4½ years ago we added MONyog to our portfolio. So there will be another important anniversary to celebrate in 2012 as well. MONyog has also proved to be robust and long-lived.

We are …

There is a huge amount of buzz around NOSQL, and we at ScaleBase are happy to see companies making the move to NOSQL. Despite what some people might think, we consider it a blessed change. It is time for applications to stop having a single data store – namely a relational database (probably Oracle) – and start using the best tool for the job.

In the last couple of years, since NOSQL technologies broke into our world, a lot of experience has been gathered on how to use them. Mainly, we see NoSQL technologies used for one of the following scenarios:

• Queries that require a very short response time
• Storing data without a well-defined schema, or storing data with a frequently modified schema

Now, I’m not in any way saying that NOSQL solutions are not used for other scenarios as well; I’m only saying that from our experience here at ScaleBase ,  these are the most common scenarios.

ScaleBase Releases Database DBT2 Performance Results

Technology achieves unprecedented transaction speed for a MySQL database at a low cost

Boston, Mass., December 12, 2011 – ScaleBase, Inc. today announced the results of its MySQL database benchmark, based on the industry-standard DBT-2 test. ScaleBase has achieved an unmatched 180,000 Transactions per Minute – the highest result for a MySQL database – while running on an Amazon RDS environment. Cost per Transaction was reported to be 50 cents, which demonstrates the cost-effectiveness of the ScaleBase solution on the Amazon EC2 cloud. Full details of the benchmark can be found at …

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.