October 8, 2009 at 8:23 am
Hello all
This is a first-time post from a regular reader!
I have set up a linked server from SQL Server 2005 to a MySQL database at a client site. I have used the ODBC 5.1.5 connector, and everything seems fine as far as the actual connection is concerned. From SQL Server, I can see all the individual databases in the MySQL server, but I am unable to see the contents - no tables and no views are visible. In each case, I can see a folder called 'System Tables' or 'System Views', but no objects within the folder structure.
Oddly, I am able to query the linked server, and I get a result set!
Any ideas - I have found numerous similar issues posted around the place, but no solution as yet.
Many thanks from a forum newbie!
October 7, 2010 at 3:50 am
To get around this issue I just use the MySQL workbench which is a free download from the MySQL website. It doesn't address the why of your question above, but it does give you visibility into the structures within the MySQL database
February 22, 2011 at 9:48 pm
I was wondering if you ever found any resolution to this problem. I have the same problem on more than one linked server to a MySQL database.
Using the MySQL Workbench works well enough, but I can't help but think a simple configuration change somewhere would solve the problem.
Steven
February 23, 2011 at 2:19 am
Hi there - what a surprise to get a response on this thread after all this time!
The earlier reply didn't address the issue, unfortunately, as I could get visibility of the contents of the MySQL database any number of other ways - the specific issue was setting up the linked server in SQL Server, which I needed to do in order to incorporate the MySQL data into some management reports.
I was unable to find anything free or open source that would work, but there is a driver available from EasySoft which appears to work. Unfortunately, it isn't cheap, but if the issue is big enough there will be a business case for paying out. EasySoft do a whole range of drivers and bridges, including an ODBC/JDBC Bridge, which I have used on another project where it was necessary to integrate a SQL Server backend into a MySQL website database.
As it happens, the original problem went away because the client decided to go with an open source reporting solution, which was quite happy talking to both MySQL and SQL Server!
February 23, 2011 at 7:22 am
Thanks for your quick response. My problem is really no more than a nuisance at this time.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply