Creating a linked server ´MySQL to MSSQL´(query the MySQL database without openquery function)

In addition to my previous linked server tutorials, I decided it is time to add MySQL to the linked server series.
In order to have the bug tracking application, Mantis migrated from linux and have it run on a windows environment, I wanted to create a replication between SQL2008 and MySQL, but then I thought, why not try out a virtual linked server again first, to test Mantis isntallation on a Windows based installation, since the online promise of Mantis on a MSSQl environment is not very promising. So today we will create a linked server from MySQl to MSSQL on a windows 2008R 64 bit environment.

Create DNS for MySQL

In order to do so, We first need to install the correct drivers in order to create a ODBC DSN, Just download the drivers from Mysql developers site and install them to your database server. DriversIf we see the listed drivers, it means we can create a new DSN, so open up the System DSN tab and ADD a new DSN, you must fill in the correct credentials, for example:ODBC_Connector

Data Source Name: Enter a describing name, so you can see what it does, you might have more linked servers or other connectors running on the same server.
Description: this isnt maditory, but if you want to be more specific, be my guest.
Server: in my case,it’s localhost, as this is a test server and MSSQL and MySQl are on the same server.
Insert username and password, when this is done. The database will display the possible databases you can connect to, in the dropdown.

Click OK and as you can see the System DSN has been added to ODBC.

Create new Linked Server

When this is done, it’s time to open up the MSSQl server and add a new linked server to the Server Objects.4_create_LInkedsname your linked server, I give it the same name as the SystemDSN. And choose the correct provider: Microsoft OLE DB Provider for ODBC Drivers. and datasource equels DSN name.
You need to fill in all the credentials for the provider string, for example:

DRIVER=(MySQL ODBC 5.2 ANSI Driver);SERVER=localhost;PORT=3306;DATABASE=mantisbt; USER=user;PASSWORD=password;OPTION=3;

Note: meaning of OPTION=3 in the MySQL connection string:
Option=1 FLAG_FIELD_LENGHT: Do not Optimize Column Width
Option=2 FLAG_FOUND_ROWS: Return matching rows
Option=3 option 1 and 2 together

Now click OK, this is always the most fun part to me! when it says connection tot the linked server succeeded!

In addition to this, you can enable provider options on the SQLOLEDB, In my case I select the Dynamic Parameter and Allow inprocess.

Now, lets run the test and see if it connects with the databases, as you can see, it connects all the databases available on the MySQL server.

Connection test

But, most important, we can query it directly. Wheeee!

Linked server without OpenQuery function (Tip!)

Maybe you have read other MySQL linked server tutorials before this one and found out that you could only query the mysql database using the openquery() function or maybe that IS  the reason it brought you to this site. Extra, as in extra work, is never fun! With the correct ODBC driver and the right provider options, you can query the MySQl database, just like any other MSSQL database on your MSSQL server. Just follow the tutorial above and don’t forget to  enable the correct provider options. Cheers!

Total cloud control together with Oracle and Microsoft


Total cloud control – “Reduce downtime” and “pluggable database”


This is what the new oracle rdbms 12c is all about; It’s a business driven enterprise cloud management solution.

Two features highlighted:

Pdb pluggable database features: one instance for multiple databases saves lots of memory and you can upgrade multiple database instances at once.

Multitenancy* (the key ingredient for the cloud)  the pro’s of the  shared server technology is it’s efficiency with the guarantee of data isolation and discrete tenant performance management. db admins can discretely manage service levels and define resource  allocation and priority.

Oracle also promises 12c’s database disk I/O is reduced and uses fair memory usage which was not really the case with the absorbing powers of current popular oracle 11g, which only works well on a powerful x64.

The multitenancy* refers to the already growing SAAS community (software as a service) where many customers share the same application instance, but with separated data. Oracle pushes this approach from the application to the database!

So whats the fuzz about?

Oracle and Microsoft announced their partnerships along with some other (saas) companies today with software vendors that will, I quote “Reshape the cloud and reshape the perception of oracle technology in the cloud”.

Partnerships are no big news in the ever changing IT world, but Microsoft and Oracle being database competitors for a long time, this is big news. This could not only bring together the best of both worlds. But will this change the way we think an work with databases? Will oracle’s 12c become the big force behind the SQl Azure cloud services? I can’t wait to hear more about this!

I’m curious to hear your thoughts on this partnership.