-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
04_DataVirtualization - azuredbexternaltable notebook feedback. #148
Comments
Jeroen, Thanks for filing this. Here is my response to your issues: please make it clearer that step 0 needs to be executed against Azure SQL. Step 0 literally says "Create a database in Azure SQL called wwiazure. Execute the following T-SQL to create a table and insert a row in the database". I'm not sure how much more clear I can make this. please make it clearer that step 1 onwards needs to be executed against SQL 2019 The notebook is for Polybase for SQL Server 2019. What other data source would they possibly choose to execute the notebook against? step 3 failed for me with
There is no way to get this error message unless the PB feature is not installed and enabled. When you say this " I had to run the follow command and restart the SQL instance to make the command work.". What command are you referring to. I'm happy to dig into this but I don't know how to reproduce this unless I don't install and enable Polybase |
Hi Bob,
Sorry for all opening all the issues here - I am just going through everything one by one and trying to view things without assumptions and prior knowledge. It might seem as if there are only complaints - but rest assured - I checked everything and these are the only things that I was not sure of. |
No apologies need. I appreciate the comments and the review. |
- Error message Started executing query at Line 17 Msg 46530, Level 16, State 11, Line 1 External data sources are not supported with type GENERIC. Total execution time: 00:00:00
although Polybase was installed and the services were running. I had to run the follow command and restart the SQL instance to make the command work. I know this issue was reported #57 as well, but I am certain in this case Polybase was installed and services were running.
The text was updated successfully, but these errors were encountered: