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 …

Jet Profiler for MySQL 2.0 is now available!Multi-language SupportWe are pleased to announce that multi-language support is now available via this release, responding to feedback and user requests. Support is now available in three languages including English, German and Swedish. If you would like Jet Profiler translated into your language, please let us know. And if you feel you can help us with translation, even better!Adjustable data retention timeframeAdjustable data retention timeframe is another exciting feature. The feature itself allows you to specify how long the application will keep the data before discarding it. This feature enables extended profiling over days or weeks without sacrificing a great deal in performance or disk space. You can access this setting via the recording settings dialog.Top IP statisticsAnother powerful feature in this release is Top IPs. This new feature …

ScaleBase is happy to sponsor the Percona Live London MySQL Conference. If you plan to attend, you can catch our booth on the expo floor or attend Liran’s session – “The Benefits of Database Sharding” at 2PM, October 25th at the Bishopsgate Suite.

In the previous post of this series (which can be found here) I discussed how to identify tables that can serve as good candidates for sharding.

Once you have decided which tables should be sharded (all the rest should be global tables), the choice of sharding keys is rather straightforward, as most will use the table primary key as the shard key. Of course, if multiple tables are sharded, and there is a foreign key relationship between these tables, then the foreign key will serve as the shard key for some tables.

Many people attempt to shard based on customer_id or a resource id, but I have seen how this usually fails in production environments. It is very hard to know in advance which customers belong together in the same database, and since customers can suddenly increase their traffic, this might create an unbalanced situation in which some …

Yeah, we know it’s 6 month from now – but we’ll give a lecture titled “Database Sharding on MySQL” at the Boston MySQL Meetup. Register here.