snowflake-connector-net | Snowflake Connector for .NET | SQL Database library

I'm using https://github.com/snowflakedb/snowflake-connector-net to connect to and query our Snowflake instance. We currently have a vanity url setup for Snowflake so that we can go to https://X.snowflakecomputing.com/ to access the Console. I have been using X.snowflakecomputing.com as the Host part of my connection string (https://github.com/snowflakedb/snowflake-connector-net#create-a-connection).

Does anyone know if this is okay or should I always be using the full {account}.{region}.snowflakecomputing.com as my Host?

Regarding the snowflake .NET connector: https://github.com/snowflakedb/snowflake-connector-net, I can find nothing in the documentation or source code to suggest that connection pooling is supported, and because the connection itself is backed by HttpClient, and we know that HttpClient should be reused rather than created/disposed constantly, what's the best way to use the snowflake .NET connector when you'll be making many queries across threads?

Note: I'm not planning on changing any properties of the connection once it's created (schema, database, etc.).

For example:

I'm using SSRS (SQL Server reporting services) to display reports, my datasource is Snowflake

I have installed the ODBC snowflake driver and configured it properly Click here to view the ODBC configuration

I have created a shared datasource on the SSRS server (via Report manager) and put in my own credentials and the connection works fine Click here to view the connection on the SSRS Server

I'm able to build the SSRS report without any issues, when I run the report, everything works fine, I can publish the report on the server and the report renders perfectly fine on the browser

The issue is when i go back to the report the next day, i'm presented with an error:

An error has occurred during report processing. (rsProcessingAborted) Query execution failed for dataset 'insert_name_of_my_dataset_here'. (rsErrorExecutingCommand)

ERROR [57P03] No active warehouse selected in the current session. Select an active warehouse with the 'use warehouse' command.

So, this also means that the following doesn't work neither:

• Subscriptions
• Cache refresh
• Snapshots

The only thing that works is if I open my report in SSRS Report builder, I right-click EACH of my datasets ("each" is very important, it doesn't work if i don't do all of them), I run the queries manually for each of them, and then the "connection" or "session" is "re-activated" and the report runs fine, both locally AND on the server...note i do not have to re-publish the report on the server for it to run

Click here to view screenshots of my process

Steps I have taken to addresss the issue (that didn't yield any resolution):

• I have tried putting the "use warehouse WAREHOUSE_NAME;" command before each dataset's SQL script, but Snowflake's API doesn't allow multiple SQL commands to be sent, so I already saw that this functionality was in the development pipeline for Snowflake and found this link: https://github.com/snowflakedb/snowflake-connector-net/issues/33 - this work was started in 2018 and the last update dates from Apr 2019 that says they are starting to address the JDBC driver...no mention for the ODBC driver yet
• I have set the snowflake parameter client-session-keep-alive to true (https://docs.snowflake.com/en/sql-reference/parameters.html#client-session-keep-alive), but according to the community portal: A similar "keep alive" parameter is not currently available for the ODBC driver. Instead, you could issue a dummy query every few hours to keep the connection alive. (https://community.snowflake.com/s/article/faq-how-long-can-my-jdbcodbc-connection-remain-idle)
• List item
• I have tried to create a cache refresh plan or a snapshot schedule that creates a snapshot or caches the report every 3 hours, and it works for the first schedule, but fails with the error for the other ones
• The only thing I didn't try is to have snowflake never close the connection and keep the warehouse in the "started" state indefinitely...but this would increase my cost, and i'm pretty sure it won't work since the session would end anyways after 4 hours...

Any assistance is welcome!

Thanks

Specs:

• SSRS 2014
• Snowflake X-small
• ODBC-64 bit driver, installed from the snowflake driver repository (tested with 32-bit also, but 64-bit is the one that is visible to SSRS)

I am working on a new Project and requirement of the project is to design an API endpoint that connects with Snowflake using .NET Core

As I am new to the Snowflake, I referred to the sample application provided by Microsoft in GitHub Link. As per the link, Snowflake is supported only in VS2017 and .NET Framework version. Will t supports in .NET Core as well?

I am trying to connect to Snowflake using HttpClient as below:

I am trying to connect to Snowflake via azure function app. Following is the code snippet (ref: https://github.com/snowflakedb/snowflake-connector-net#create-a-connection ) I am using: