Friday, November 16, 2012 5:28 PM
First I am not totally sure where to ask this question so I figured I would start here.
I am designing a few reports using SQL Server 2012 SSRS. I have a few MySQL databases that need to be reported on.
I installed the 5.1 32 and 64 bit drivers (This was the only way I could create it as a data source and get visual studio to use it when creating the datasource).
What happens is when I create a new report and get to the query builder if I add one of the bad tables it crashes visual studio. I have 18 tables and 5 of them cause the issue.
Also if I manually try to do the query at the query builder it fails and gives me errors.
For example putting this query in the query builder and trying to execute it crashes visual studio
BUT if I enter this query in the field for Query string (Not going into the query builder). I can build a report with it and it works.
So it appears as if the connection is working but query builder doesn't know how to handle some of the tables I have.
customer_quotas is a simple table
ucstID INT(11) PK
It is referenced in one other table.
There is another table that fails that is as simple as you can get. The table name is innodb_monitor and it has one field that is not a PK called a of type INT(11). This table doesn't touch anything, it is actually empty.
Is there a fix to the problem? Using query builder is nice and I would like to continue using it.
Monday, November 19, 2012 6:39 AMModerator
Based on the current information, to narrow down whether the issue is related to the Visual Studio or not, I suggest that you check the issue with Query Designer in Report Builder.
If the issue doesn't happen with Report Builder, it should be related to the Visual Studio itself. In this condition, I suggest that you follow the steps below:
1. Click Start -> Visual Studio 2010 -> Visual Studio tools -> Visual Studio Command Prompt to start the command line tool.
2. Run the command to see whether the issue occurs in Visual Studio Safe Mode:
3. If it can run properly, please run the following command lines and run the Visual studio again to see whether it can solve this issue:
If the issue also occurs with Report Builder, I suggest that you check the issue on other servers to see if it is related to the SSRS installation.
TechNet Community Support
- Marked As Answer by Mike YinMicrosoft Contingent Staff, Moderator Sunday, November 25, 2012 4:49 PM