I know this is a well trodden path, but my review of SO posts around this yielded no results. So this is a fresh installation of MySQL and Visual Studio 2019 on my dev machine - like both literally vanilla tonight. I used the Development installation for MySQL:
So I can connect to a test database just fine with Server Explorer. I can also Add Connection fine (that is it sees the remote database), but when I come to click next on Choose your data connection, I get this error:
I come across this problem every time I try to set up MySql and VS together. On this occation, I'm working with the latest MySQL version and thus have gone for the latest MySql binaries. As I say, I've reviewed all of the historic SO posts, but cant apply them to this. Does anyone have any ideas? (I had to downgrade to VS2019 because there's no MySql for VS 2022).
Why when I want to open design view of table in MySQL database It every time throws error
I can view data, edit data, manage data but can't edit table definition. I use Visual Studio 2015 Community, MarriaDB 10.1.9 and MySQL for Visual Studio 1.2.6.
I was able to fix this problem by uninstalling Connector 6.9.9 and installing 6.9.8 - https://downloads.mysql.com/archives/c-net/
You need to install the Dot Net Connector.
http://dev.mysql.com/downloads/connector/net/
It's 2018 now, just thought I'd throw one out there. After several hours of trying random variations I got it to work using other people's answers.
I actually got the development download and it works but only with:
MySQL for Visual Studios 2.0.5
Connector/NET 6.9.8
Visual Studio 2017
Compatibility Reference:
https://dev.mysql.com/doc/visual-studio/en/visual-studio-install.html
Connector Archive (originally shared by Christopher Hustman):
https://downloads.mysql.com/archives/c-net/
I've been reading about mySQL DataSource and the ability to use mySQL with Entity Framework, but I can't really generate EF with mySQL without the use of the DataSource Dialog
How can I add mySQL Database to such dialog?
This is what I have done so far:
Installed mySQL Connector v.6.5.4
Restarted n-times my Windows 7 machine
Read all about how well mySQL Connector works on previous versions of Visual Studio
I have just read from mySQL Forums that mySQL will ship Visual Studio 2012 integration with mySQL Connector v.6.5.5
We'll be adding support for VS 2012 in Connector/NET 6.5.5 and later 6.6.x version
http://forums.mysql.com/read.php?38,546265,564533#msg-564533
and give a link to test a trick
http://social.technet.microsoft.com/wiki/pt-br/contents/articles/10476.instalando-mysql-connector-no-visual-studio-2011-beta.aspx
and here is the vsix file if you follow the tutorial (In Portuguese)
Microsoft Visual Studio Extension for mySQL: http://cl.ly/JqXO
just download and double click...
then, you will get all to work
Using Visual Studio 2012 Professional
One clarification: Visual Studio Express DOES NOT support MySQL .NET Connector as extension.
You still may use it adding reference to MySql.Data.dll file that you may find in MySQL Connector installation folder (for me it was W:\Program Files\MySQL\Connector NET 6.5.4\Assemblies\v4.0).
After that you may use it like this:
using MySql.Data.MySqlClient;
...
var mycon = new MySqlConnection();
According to this page: http://dev.mysql.com/downloads/connector/net/
"Starting with version 6.7, Connector/Net will no longer include the MySQL for Visual Studio integration. That functionality is now available in a separate product called MySQL for Visual Studio available using the MySQL Installer for Windows (see http://dev.mysql.com/tech-resources/articles/mysql-installer-for-windows.html)."
Visual Studio 2012 is not yet supported by MySQL Connector v.6.5.4. You can't add a connection to MySQL in the Server Explorer to begin with.
According on this post, support will be added on MySQL Connector v.6.5.5
Connector/NET 6.5.5 does not support VS2012, but Connector/NEt 6.6.x does.
However Visual Studio Express editions are not supported, hence the only way to work in Entity Framework and Visual Studio Express and MySql (or other database different than SQL Server for that matter) is using code first.
It wouldn't matter if you had the MySQL driver showing as far as I can tell. I'm running VS 2012.3 and if I try to create a Data Connection in VS Server Browser, I can get as far as selecting the MySQL driver and no more. If I try typing a servername/username/password (any of the fields), the window just disappears and YES, it's only when the MySQL driver is being used so NO it's not vs (not exclusively) causing the problem. Go ahead and say that it's my environment but you'd not be able to justify that even remotely compared to the FACT of what is happening. ALL my other software/extentions/add-in/libraries work just fine. No surprise either seeing how buggy the "3 minute" Windows Installer was. Had to uninstall/reinstall a server instance to get to the configuration wizard and there is no other apparent way to configure an instance without it. I'd rather have the old setup. /rant
Downloaded and install Download MySQL for Visual Studio http://dev.mysql.com/downloads/windows/visualstudio/1.1.html
I've been reading about mySQL DataSource and the ability to use mySQL with Entity Framework, but I can't really generate EF with mySQL without the use of the DataSource Dialog
How can I add mySQL Database to such dialog?
This is what I have done so far:
Installed mySQL Connector v.6.5.4
Restarted n-times my Windows 7 machine
Read all about how well mySQL Connector works on previous versions of Visual Studio
I have just read from mySQL Forums that mySQL will ship Visual Studio 2012 integration with mySQL Connector v.6.5.5
We'll be adding support for VS 2012 in Connector/NET 6.5.5 and later 6.6.x version
http://forums.mysql.com/read.php?38,546265,564533#msg-564533
and give a link to test a trick
http://social.technet.microsoft.com/wiki/pt-br/contents/articles/10476.instalando-mysql-connector-no-visual-studio-2011-beta.aspx
and here is the vsix file if you follow the tutorial (In Portuguese)
Microsoft Visual Studio Extension for mySQL: http://cl.ly/JqXO
just download and double click...
then, you will get all to work
Using Visual Studio 2012 Professional
One clarification: Visual Studio Express DOES NOT support MySQL .NET Connector as extension.
You still may use it adding reference to MySql.Data.dll file that you may find in MySQL Connector installation folder (for me it was W:\Program Files\MySQL\Connector NET 6.5.4\Assemblies\v4.0).
After that you may use it like this:
using MySql.Data.MySqlClient;
...
var mycon = new MySqlConnection();
According to this page: http://dev.mysql.com/downloads/connector/net/
"Starting with version 6.7, Connector/Net will no longer include the MySQL for Visual Studio integration. That functionality is now available in a separate product called MySQL for Visual Studio available using the MySQL Installer for Windows (see http://dev.mysql.com/tech-resources/articles/mysql-installer-for-windows.html)."
Visual Studio 2012 is not yet supported by MySQL Connector v.6.5.4. You can't add a connection to MySQL in the Server Explorer to begin with.
According on this post, support will be added on MySQL Connector v.6.5.5
Connector/NET 6.5.5 does not support VS2012, but Connector/NEt 6.6.x does.
However Visual Studio Express editions are not supported, hence the only way to work in Entity Framework and Visual Studio Express and MySql (or other database different than SQL Server for that matter) is using code first.
It wouldn't matter if you had the MySQL driver showing as far as I can tell. I'm running VS 2012.3 and if I try to create a Data Connection in VS Server Browser, I can get as far as selecting the MySQL driver and no more. If I try typing a servername/username/password (any of the fields), the window just disappears and YES, it's only when the MySQL driver is being used so NO it's not vs (not exclusively) causing the problem. Go ahead and say that it's my environment but you'd not be able to justify that even remotely compared to the FACT of what is happening. ALL my other software/extentions/add-in/libraries work just fine. No surprise either seeing how buggy the "3 minute" Windows Installer was. Had to uninstall/reinstall a server instance to get to the configuration wizard and there is no other apparent way to configure an instance without it. I'd rather have the old setup. /rant
Downloaded and install Download MySQL for Visual Studio http://dev.mysql.com/downloads/windows/visualstudio/1.1.html
I'm being driven to insanity trying to figure out why Intellisense just fails to work at all. The server I'm using is local and is 2008, the database is set to 2008 compatibility, Intellisense is on in every menu I can find, and yet no member list will pop up even with a CTRL-J.
Has anyone experienced something like this and found a way to fix it? I really can't bring myself to start work unless I have Intellisense working.
I understand this post is old but if anybody is still searching and has not found a solution to the intellisense issue even after re-installing, applying the cumulative updates, or other methods, then I hope I may be of assistance.
I have Applied SQL 2008 R2 Service Pack 1 which you can download here
http://www.microsoft.com/download/en/details.aspx?id=26727
32 Bit:
SQLServer2008R2SP1-KB2528583-x86-ENU.exe
64 Bit:
SQLServer2008R2SP1-KB2528583-x64-ENU.exe
I have applied this SP1 and now my intellisense works again.
Visual Studio 2010 SP1 breaks SSMS 2008 R2's IntelliSense. There is a connect about that, and fortunately there is also a fix for that.
(In short, you will need to install Cumulative Update package 7 for SQL Server 2008 R2 by requesting
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x86or
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x64
from this hotfix request page.)
EDIT: As #Paul Lemke noted, one might need to get the latest CU package. This blog contains the SQL server releases. (As of this writing, the latest is CU14)
For SQL Server 2008 R2, installing Cumulative Update 7 will fix the problem. The file you need is
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x86
or
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x64
I also had to uninstall and re-install SQL Server 2008 first (which didn't fix it, but the CU did).
No need to reinstall.
Click on the setup file. Then go to maintenance and click on Repair. This should correct the intellisense problem.
I just the had same problem. I figured out that Intellisense stopped working after I took some databases offline and doing an Intellisense refresh (Ctrl-Shift-R). I brought the offline databases back online, did a refresh (Ctl-Shft-R) again and VOILA! Intellisense is working again.
What a crappy design. Maybe the population of Intellisense's lists chokes when a database exists but is offline. Thanks Microsoft.
I don't want to suggest a product out of turn, since getting Intellisense running is probably the best option, but I've struggled with the accursed no intellisense on Management Studio for months. Reinstallation, CU7 update, refreshing caches, sacrificing chickens to pagan gods; nothing has helped.
I was about to pay for RedGate's SqlPrompt (pretty damned pricey, $195 US), when I found SqlComplete.
http://www.devart.com/dbforge/sql/sqlcomplete/?gclid=CN2xs_Lw7akCFcYZHAodpicXXw
There is a free version which does the basics, and the full version is only $50!
I'm a database architect, and while I can remember the commands, auto complete saves me heaps of time. If you're stuck and can't get Intellisense to work, try SqlComplete. It saved me hours of hassle.
I recently wrote a tip about troubleshooting IntelliSense. The title says SQL Server 2012 but most of the techniques can be applied to earlier versions of Management Studio as well.
Troubleshooting IntelliSense in SQL Server Management Studio
I ended up fixing it by reinstalling SQL Server 2008. This wasn't at all optimal, but if someone comes across a similar problem be sure to know this route will probably work.
I tried all the fixes - taking databases offline and then bringing them online, installed Cumulative update 10, repaired SQL Server Installation, refreshed local cache, made changes to the required settings on SQL Server Management Studio but everything was in vain. Finally installing the correct service pack (SP1) did the trick for me !
Follow the link below, and download SQLServer2008R2SP1-KB2528583-x86-ENU.exe (or the x64 file for a x64 bit instance of SQL Server)
http://www.microsoft.com/download/en/details.aspx?id=26727
Finally i have Intellisense enabled !
I'm posting this here as I am sure more people will be comeing across this issue. I installed Security Update for microsoft Visual Studio 2010 Service Pack 1 (KB2565057) and lost Intellisense in SQL Server Management studio 2008 (not R2).
An uninstall of the SP restored Intellisense .. Don't you just love Microsoft????
After finding this thread, I discovered that my Intellisense only broke after taking a database offline, and any offline database(s) on the instance would kill Intellisense.
In this thread, explaining that in order to restore Intellisense, you must
take the necessary databases offline, then
restart the server instance, and finally
refresh the Intellisense cache.
This procedure has worked for me and Intellisense is now working again.
I've had the same problem too. Searched everywhere online and can't find a solution. I did install Redgate's SQL Prompt which functions similarly to Intellisense, so maybe there was a conflict. I've since stopped the Prompt from running, but now no intellisense at all. Using SQL Server 2008 will SQLCMD mode off, no luck at all. This has happened before, a reinstall of SQL Server was the only thing that I could get to work.
Same problem, but just re-installing SQL Management Studio 2008 R2 Service Pack 1 worked for me. I left my DB engine alone. The DB engine is not the problem, just SQL Management Studio getting hosed by Visual Studio SP1.
Installers here...
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26727
I installed SQLManagementStudio_x86_ENU.exe (32 bit for my machine).
When trying the accepted answer, I was getting an installation error: A failure was detected for a previous installation, patch, or repair blah, blah, blah...
To fix this, in my registry, I changed all DWORD values to 1 in the following Keys: (As always be careful modifying the registry and create a backup of the key before changing anything)
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\100\ConfigurationState
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\ConfigurationState
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\ConfigurationState
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.SQLEXPRESS\ConfigurationState
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\ConfigurationState
See my full post about Fixing Intellisense issue in SSMS.
Here is the official word on this from MS.
http://support.microsoft.com/kb/2531482
Their solution is the same as above, install the SQL Server 2008 R2 updates with the version 10.50.1777.0.
http://support.microsoft.com/kb/2507770
I did all of the above and ultimately gave up. Then one last resort was a third part SQL Intellisense add-on I found SQL Complete Express by devArt.
It's Intellisense plus more. Intellisense is back and all is well.
Supports SSMS 2005 - 2012 also includes Visual Studio Add-In.
SQL Complete
For SQL Server 2008 R2, installing Cumulative Update 7 will fix the problem. The file you need is
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x86
or
SQLServer2008R2_RTM_CU7_2507770_10_50_1777_x64
I also had to uninstall and re-install SQL Server 2008 first (which didn't fix it, but the CU did).
this is Direct Link From MS that i was got it Hot Fix