I cannot browse Azure Data Explorer (Kusto) tables, etc. with LINQPad 6
Note: this works fine in LINQPad 5. Is there planned support for this in LINQPad 6 or am I doing something wrong?
- Select Add connection.
- Set Build data context automatically.
- Set Default (LINQ to SQL), the LINQPad driver.
- Set SQL Azure.
- For the server, specify the name of the Azure Data Explorer cluster: help.kusto.windows.net
- Set Active Directory - Integrated, for signing in.
- Select Test to verify connectivity.
- Select OK. The browser window displays the tree view with the databases.
I should be able to browse through the databases, tables, and columns at this point, but it failed for me. When I attempt to expand the "Samples" database, I get the following error:
Comments
In LINQPad 5, could you please connect to the database and run the following SQL query:
select SERVERPROPERTY('productversion'), SERVERPROPERTY('EngineEdition')
and let me know the results.
Here's what I got, @JoeAlbahari. I hope it's helpful!
Rob
@JoeAlbahari I am having the same issue, with the exact same productversion and EngineEdition as @RobertBernstein. Although, I am very happy to know that this at least works with LINQPad 5 for the time being.
Thanks for the info. In the next beta build, I'll add an explicit check for that metadata table being present before querying. In the meantime, you can work around it by unchecking the "Include stored procedures and functions" checkbox in the connection properties dialog.
That didn't solve it, @JoeAlbahari. I now get a different error.
I'm not sure the best way to deal with this. It's masquerading as a normal instance of SQL Server, but doesn't support SQL Server's functions.
I’m surprised that it works in v5 and not v6.
LINQPad 6 needs schema that can also feed the EF Core context generator, and this requires extra metadata.
I've added an exception-handling test to determine whether the server implements object_definition. Try the latest LINQPad 6 beta and let me know how you get along.
I just tried with LINQPad 6 Beta and can confirm that it still doesn't work (using help.kusto.windows.net) - I've noticed that you can still make SQL queries in LINQPad 6, but you can't use Linq-To-Sql
Everything works fine in LINQPad 5 though.
Thanks for looking into it.
Based on that error, Data Explorer must then be a fork of SQL 2005. I'll lower the version again in the next build.
Try now
Now it's complaining about another table
Is it possible to create an instance of Data Explorer that I can connect to?
I just tried it again using the latest LINQpad 6 beta and got the same response as @ambrose. I'm not sure what you're asking for in terms of an instance of Data Explorer to connect to, @JoeAlbahari. Do you mean other than this sample cluster/database?
I need a sample connection string that can reproduce the problem. I've tried setting up Data Explorer myself in the Azure portal, but without success.
@JoeAlbahari, can you browse to this address?
https://dataexplorer.azure.com/clusters/help/databases/Samples
I'm not sure how you get a connection string from there, but hopefully you can browse to this.
Also, try this link if that one doesn't work:
https://dataexplorer.azure.com/clusters/help/databases/Samples?query=H4sIAAAAAAAAAwsuyS/KdS1LzSsp5qpRKM4vKlFIqlQILkksKgnJzE1VSEktTgZKlCRmpyoYGgAAl2udPi4AAAA=
I've gone to that address but can't find a way to get a connection string that I can use in LINQPad.
I’m not sure how to help from here.
The latest beta includes a fix for the latest reported issue. Let me know whether it works - or whether you get the same or a different error.
I was seeing the same as Robert, but it seems to be working with the Beta version I just tried. Thanks!