At this point, you can test connection to your SQL Server. Click “Test Data Source…”. If things go well, you will see following popup saying “TESTS COMPLETED SUCCESSFULLY!”.
thank you for this tutorial. I did create an ADBC datasource with Trusted_Connection= Yes (delegating the security aspects to the underlying Windows framework). However, when adding the connection to Exploratory, I can test the connection successfully; but at the time of finalizing the connection and clicking the Add button, Exploratory will keep asking for a username and prevent me from going any further.
Is there any other way I could go around this limitation?
Hi Emmanuel,
Thank you for reporting this issue.
Let us try building a version that would not require username for ODBC connection.
I will get back to you shortly with the build.
Are we sure that this bug is still fixed? I am using version 3.5.0.2_WIN and I’ve gotten a similar error:
Error in getDBConnection(“odbc”, NULL, NULL, NULL, username, password, :
argument “username” is missing, with no default
This happens if I create a DSN with the SQL Server Native Client 11.0 and the ODBC Driver 13 for SQL Server, both using Windows Auth.
Interestingly, Exploratory can view the databases and tables, but just not Preview the data. That’s when the error happens.
Note that when I Add a connection in Exporatory and click on “Test Connection”, the green confirmation bar at the top only says “Connect to”. It never says what it is connected to.
(Edit: I also tried a DSN with a SQL Server driver version 6.01…)