I've found some old threads talking about the difficulty connecting to a MySQL and I was wondering if it's even possible to connect to MySQL directly in ArcGIS Pro these days.
I've created a data source on my computer, but when I go to add an OLE DB connection in ArcGIS Pro, I don't even have the option to select the MySQL ODBC driver.
Is there a setting or plugin/addon I'm missing that would let me do this? I would really rather not have to migrate our database to PostgreSQL if I can avoid it.
If you follow this link you'll not see mySql as a supported database. I have used stand alone python to connect to a mySql db and with arcpy copy various tables into an ArcGIS file geodatabase.
Yeah, I was just hoping there was some sort of workaround. Looks like we'll be moving to PostgreSQL. Not a big deal as there are really good migration tools out there but it would be nice if Esri supported MySQL as well. I feel like it's common enough to warrant compatibility.
Do you currently connect ArcMap to MySQL via an ODBC connection and you're trying to migrate that workflow to Pro? Or is this a new setup just in Pro?
I was actually able to find a way to make this work!
I had completely misunderstood what the Microsoft OLE DB Provider for ODBC Drivers was for. If I choose that option and select the MySQL data source that I made through MySQL's OLE DB connection it all works.
I guess that option is like a wrapper or whatever to allow connections to other types of database. So if you're in my situation and need to connect to a MySQL server, try the "Microsoft OLE DB Provider for ODBC Drivers" option!
Great Tip @KieranClark ! Thanks!
@KieranClark : I followed your advice as well as post from @KenGalliher1 and I've established a MySQL connection through ArcGIS Pro (2.7.1) but I get an error when I try to add a table to my ArcGIS Pro session:
I can get to this data base (which is web hosted) using WorkBench without any problem.
Any ideas?
how can I add OLE DB connection in Arc GIS Pro 2.4 ?? any methods??
any add-ins or arcpy packages?
If anyone is still following this post or comes across it, the problem I describe is now a listed as a bug when connecting to MySql ver8.
BUG-000141014