search

Azure / Azure-TDSP-Utilities

Utilities and scripts developed as part of Microsoft's Team Data Science Process for productive data science
Creative Commons Attribution 4.0 International
373 stars 275 forks source link

IDEAR's Server param #12

Closed robmccan closed 7 years ago

robmccan commented 7 years ago

Sorry if this is a silly issue... I'm trying to apply IDEAR on some data I have in a local SQL Server 2016 instance (everything is running on the same box, an Azure VM). I followed your directions for creating a .yaml but I must be messing up on the Server parameter. When I run IDEAR and select the .yaml, IDEAR keeps returning "Error: first argument is not an open RODBC channel".

So, what exactly should my argument be for the default SQL Server on the local box? My various attempts at using localhost didn't work.

I can query the DB just fine from SSMS, so the DB is alive and functional. I can also run IDEAR on your example datasets (para-adult.yaml and para-bike-rental.yaml), so the R/IDEAR side is also functional.

Any help would be appreciated, thanks.

xibingaomsft commented 7 years ago

Rob, if you follow the parameter setting from the instructions, you should be able to connect to SQL Server/DW data source. The second table from the doc above has the required params and example values.

gopitk commented 7 years ago

Rob, Is this still an issue? Usually the problem you may be trying to connect over TCP in RODBC and TCP protocol is disabled on SQL Server (by default). SSMS can use TCP or named pipes. To confirm this you can go to the SQL 2016 configuration utility and check the protocols enabled.

hangzh-msft commented 7 years ago

Closed this issue since the customer did not respond. Will reopen as needed.