mysql key_buffer_size not limited to 4GB on 64Bit systems

Even though originally, key_buffer_size (The MyISAM index buffer) should have been limited to 4GBs on 32 and 64 bit operating systems, the limit did not apply any more for whatever reason the designer wanted to set this limit, and therefore, there is no 4GB limit on the  key buffer size for MyISAM tables.

The 4GB limit stays for join_buffer_size, sort_buffer_size, and myisam_sort_buffer_size, But even those had the 4GB limit removed on 5.1.23/5.2.6
In any case, all the literature on the internet stating that there is a 4GB limit on the key_buffer_size are either outdated, or based on outdated literature.
Settings for read_buffer_size and read_rnd_buffer_size
are limited to 2GB on all platforms.

MySQL Windows VS MySQL on Linux

Comming across Robin Schumacher’s “MySQL on Windows? Absolutely!” i have some stuff to say

First, I absolutly LOVE windows on my Desktop, and i LOVE Linux on my servers, and i have nothing against windows servers or Linux Desktops, i like Operating systems that get the Job done faster and with least effort, so what suits a job suits me, having never used a mac, i would jump to a mac if they tell me it can help you develop application X faster, why not, but the article here does not seem to make sense to me. Here is why

In the comparison of number of downloads, it clearly reads that windows has 600K downloads VS linux that has 200K downloads, but are you serious ?

On Linux, MySQL is hardly if ever downloaded from , while on Windows it is always downloaded from MySQL.COM and therefore i beg an explanation on why you say this statistic tells anything, Also, most developers are like me, they use the Windows edition for development on there development PCs, and then deploy the actual application on a Linux server.

For example, on a debian system i would simply issue

apt-get install mysql-client mysql-server

this will get MySQL binaries from Debian, not from MySQL, and therefore making the statistic not available to you.

Then the article talks about how insignificant the differences between the Linux and Windows edition is, to tell you the truth, this is not the case at least for me, here are SOME examples

Most of my applications can not make good use of RAID because RAID does not help with disk seek time (And therefore latency), My answer to this is usually separating tables to more than 1 hard disk , and although having databases moved to other hard drives is supported in windows by creating a text file, moving individual tables on windows is not, On linux, i simply create a symbolic link to the MYD file, and one to the MYI file, i can even split a single table to 2 hard drives with the indexes on 1 drive and the actual data on the other.

Clustering anyone ??

For a longer list check out , this is certainly is inferior to the Linux counterpart for something like a shared hosting environment (See number of open files and connection timeouts etc..)

Now to add more to that, Linux is a free OS, you install and upgrade it for free, and MySQL is also free, if your business uses many many MySQL servers, your savings on Windows Server licenses can be significant.

The bottom line is, when a company like Oracle (Since it has acquired SUN) gets hold of an open source database engine, you can rest assured objectivity will still be there only when it supports the paying product.

Thanks for listening.

Linking Windows Plesk to external Database

So, I setup Windows in a VM with that old version of windows i had on the shelf for some time. (Thanks XEN HVM), Installed .NET 3.5 SP1 and the KB959209 , Setup MSSQL Express 2008

Things that got setup

Management Tools
SQL Client Connectivity
ms sync framework

From the SQL SERVER CONFIGURATION MANAGER, i enabled TCP/IP from protocols for SQL express

Opened a hole in the firewall for both MSSQLBinnsqlservr.exe and 90Sharedsqlbrowser.exe

and then from within Plesk i added the server

Server Host:

Admin User: sa

Admin Pass: Same pass i entered in Mixed authentication for the sa user !

Done, Plesk thinks this is a great thing i have done and accepts the thing instantly

MS advises that i read Understanding Surface Area – In setup help Minimize SQL Server 2008 surface Area