ADO.NET Provider for Snowflake does not show tables/views in Analysis Services Data Source View dialog

Live Connectivity CData Drivers
, , ,
1

I am test driving the ADO.NET provider for Snowflake to connect to data in Snowflake from Analysis Services in Multidimensional Mode. 
I follow the descriptions in the article.

Connection to Snowflake succeeds but when I try to add tables to the Data Source View there are no tables/views shown. The dialog is completely empty. Compare section “Creating a Data Source View” point 4 in the article where tables are visible.
(Remark: I am also sure that tables are available in my Snowflake database)

I have set logging level to 5 and inspected the logs. The connection requests seem to work fine. But when calling ADOConnectionImpl.GetDataSourceInformation() it seems not to find the system table sys_sqlinfo.

What am I doing wrong? What is the root cause for not seeing any tables/views?

2025-10-15T17:50:11.184+02:00 5 [   29|    0|    1] [META|Schema] ADOConnectionImpl.GetDataSourceInformation()2025-10-15T17:50:11.184+02:00 2 [   29| Q-Id|    1] [EXEC|Parsed] Executing query: [SELECT VALUE FROM sys_sqlinfo WHERE NAME = ‘IDENTIFIER_QUOTE_OPEN_CHAR’]2025-10-15T17:50:11.184+02:00 2 [   29|    0|    1] [EXEC|Normlz] Normalized query: [SELECT [VALUE] FROM [sys_sqlinfo] WHERE [NAME] = ‘IDENTIFIER_QUOTE_OPEN_CHAR’]2025-10-15T17:50:11.184+02:00 2 [   29|    0|    1] [EXEC|Normlz] Normalized query: [SELECT [sys_sqlinfo].[VALUE], [sys_sqlinfo].[NAME] FROM [sys_sqlinfo] WHERE [NAME] = ‘IDENTIFIER_QUOTE_OPEN_CHAR’]2025-10-15T17:50:11.184+02:00 5 [   29|    0|    1] [META|Schema] Engine Invalid object name 'sys_sqlinfo’2025-10-15T17:50:11.184+02:00 3 [   29|   38|    1] [EXEC|Normlz] Executing query: [SELECT [sys_sqlinfo].[VALUE], [sys_sqlinfo].[NAME] FROM [sys_sqlinfo] AS [sys_sqlinfo] WHERE [NAME] = ‘IDENTIFIER_QUOTE_OPEN_CHAR’]2025-10-15T17:50:11.184+02:00 2 [   29| Q-Id|    1] [EXEC|Messag] Executed query: [SELECT VALUE FROM sys_sqlinfo WHERE NAME = ‘IDENTIFIER_QUOTE_OPEN_CHAR’] Success: (0 ms)2025-10-15T17:50:11.184+02:00 2 [   29| Q-Id|    1] [EXEC|Parsed] Executing query: [SELECT VALUE FROM sys_sqlinfo WHERE NAME = ‘IDENTIFIER_QUOTE_CLOSE_CHAR’]2025-10-15T17:50:11.184+02:00 2 [   29|    0|    1] [EXEC|Normlz] Normalized query: [SELECT [VALUE] FROM [sys_sqlinfo] WHERE [NAME] = ‘IDENTIFIER_QUOTE_CLOSE_CHAR’]2025-10-15T17:50:11.184+02:00 2 [   29|    0|    1] [EXEC|Normlz] Normalized query: [SELECT [sys_sqlinfo].[VALUE], [sys_sqlinfo].[NAME] FROM [sys_sqlinfo] WHERE [NAME] = ‘IDENTIFIER_QUOTE_CLOSE_CHAR’]2025-10-15T17:50:11.184+02:00 5 [   29|    0|    1] [META|Schema] Engine Invalid object name 'sys_sqlinfo’2025-10-15T17:50:11.184+02:00 3 [   29|   39|    1] [EXEC|Normlz] Executing query: [SELECT [sys_sqlinfo].[VALUE], [sys_sqlinfo].[NAME] FROM [sys_sqlinfo] AS [sys_sqlinfo] WHERE [NAME] = ‘IDENTIFIER_QUOTE_CLOSE_CHAR’]2025-10-15T17:50:11.184+02:00 2 [   29| Q-Id|    1] [EXEC|Messag] Executed query: [SELECT VALUE FROM sys_sqlinfo WHERE NAME = ‘IDENTIFIER_QUOTE_CLOSE_CHAR’] Success: (0 ms)2025-10-15T17:50:14.684+02:00 5 [   29|    0|    1] [META|Schema] Engine Invalid object name 'sys_disconnect’2025-10-15T17:50:14.684+02:00 4 [   29| Q-Id|    1] [INFO|Connec] Executed sys_disconnect: Success: (0 ms)2025-10-15T17:50:14.684+02:00 1 [   29| Q-Id|    1] [INFO|Connec] Closed Snowflake connection2025-10-15T18:07:35.367+02:00 5 [   21|    0|    2] [META|Schema] Engine Invalid object name 'sys_disconnect’2025-10-15T18:07:35.367+02:00 4 [   21| Q-Id|    2] [INFO|Connec] Executed sys_disconnect: Success: (0 ms)2025-10-15T18:07:35.367+02:00 1 [   21| Q-Id|    2] [INFO|Connec] Closed Snowflake connection

2

Hi ​ @kde84

The portion of the log file you shared doesn’t provide enough information for us to confirm whether the Database and Schema connection settings are configured properly. Can you confirm you have set these properties in the connection configuration?

Also, note that Snowflake is case-sensitive, so please ensure you’re using the correct casing for the Database and Schema connection properties, as incorrect casing can cause similar issues.

Please check the above, and if you’re still experiencing issues, I’d recommend raising a support ticket here and including the full log file so one of our support specialists can help you troubleshoot further .