I don't have the rights to do this at work, but you might. Open a SQL Server Management Studio session and try to create a SQL Server Auth following this guide:
Well, again though, Tableau can authenticate you into your MS SQL Server from a Mac in case of Windows Auth.
Which tells me it the mission is not impossible and is only dependent on the capabilities of the software.
Sorry for the confusion, I usually refer to the paid-for products as Pro products, because that's usually part of their name. If you have a licence for any of our commercial (paid-for) products, you are able to download and use the database drivers we provide.
Thanks Edgar @edgararuiz!
I was (and still am) confused by this phrase on the RStudio Professional Drivers page:
If you are using RStudio Server Pro, RStudio Connect, or Shiny Server Pro, then you can download and use RStudio Professional Drivers at no additional charge.
It doesn't list RStudio Commercial (the $995/user/year one), unless I'm confusing the product names.
Right, you're referring to the RStudio Commercial Desktop license (https://www.rstudio.com/products/). That is one of the valid products that gives you access to the drivers, I verified that yesterday. We probably need to update the page.
I'm glad you got it going! I'm not having such luck, however:
Error: nanodbc/nanodbc.cpp:950: 01000: [unixODBC][Driver Manager]Can't open lib 'Simba SQL Server ODBC Driver' : file not found
ODBC on Mac is such an infuriating mess, IMO. At this point I seriously have no idea which incarnation of unixODBC my RStudio install is picking up. Is the Anaconda one? The xcode one? One from Mars? And I could probably figure it out eventually... given enough random slaps against the keyboard... but the very thought is demoralizing.
First off, you might want to first try seeing if the odbc package can even see that driver on your machine by using the command from this page, as I would suspect that it most likely is not: sort(unique(odbcListDrivers()[[1]])) https://db.rstudio.com/getting-started/connect-to-database
I think I see what is going on here....your error is stating that the unixODBC can't point to (or find) where the "Simba SQL Server ODBC Driver" is on your local machine. I think @taras's solution essentially tried to setup these files for your automatically, which seems like it did not work. The error is definitely a bit cryptic if you have never had to manually modify configuration files to make things connect and work properly. This page goes in more depth on how to configure it: https://db.rstudio.com/best-practices/drivers/
This is a good example of how to configure the file necessary for your specific issue:
Let me know if this helps or not.
@edgararuiz it might be helpful for newcomers to outline from the ground up on this page: http://db.rstudio.com/getting-started/connect-to-database/
how to create and configure these files from the start, as I think most people would have a hard time setting up these files to work properly, and getting the odbc package to verify the driver is being picked up.
I remember I needed to mess with odbc.ini (or whatchamacallit? actually it's the other one with the driver list: odbcinst.ini i think) files to make RStudio "see" my freshly installed ODBC drivers from Microsoft. I had to edit a few files to get it to work. I found several .ini files, some blank, some semi-complete. I guess RStudio saw one but not the other
Simba drivers, however, were recognized instantly.
unixodbc is needed. You can find the location of the correct ini files with odbcinst -j command line tool
Environment variable ODBCSYSINI can be used to change the default location of system files
You can have local ini files: ~/.odbc.ini for datasource connexion and ~/.odbcinst.ini for drivers locations - useful for testing quickly without admin rights. (WARNING : there is a dot in local ini file name that is not present in system ini file name.)
It is very helpful to set up those files to simplify connection string afterward (you can juste use the DSN name). However, they are not required - you can pass all argument at the connection but:
There could be a lot
You need to know the exact location of the drivers on your system
You need to know all the connection information for the database