Snowflake

Snowflake is a cloud-hosted relational database for building data warehouse.

Configure the following details for Snowflake data source:

Register data source
Field	Description
Display name	Enter the data source name to be displayed on the screen.
Database name	Enter the name of your database.
Account name	Enter your Snowflake Account name. This may include region information (For example, account_name.region_id). If you do not have region information, use the account name that is provided by your Snowflake administrator.
Warehouse name	Enter the Warehouse name.
Username	Enter the username.
Password	Enter the password.
Test connection	Click the Test connection link to test the database connection. If the database connection is successful, a success message appears.
Associate catalog	Select the checkbox to associate the catalog.
Catalog name	Enter the name of the catalog. This catalog is automatically associated with your data source and serves as your query interface with the data stored within.
Create	Click Create to create the data source.

Limitations for SQL statements

CREATE TABLE AS is also supported for CREATE TABLE statement.
DROP TABLE statement only when enabled in the catalog.
For data source-based catalogs the CREATE SCHEMA, CREATE TABLE, DROP SCHEMA, DROP TABLE, DELETE, DROP VIEW, ALTER TABLE, and ALTER SCHEMA statements are not available in the Data Manager UI.

BLOB and CLOB data types support SELECT statement but do not support operations such as equal, like, and in.
The data that is shown from the UI for BLOB data type is in Base64 format, while the result from presto-cli is in hexadecimal format.
BINARY data type supports only SELECT statement.
When the fields of data type REAL have 6 digits or more in the decimal part with the digits being predominately zero, the values when queried are rounded off. It is observed that the rounding off occurs differently based on the precision of the values. For example, a decimal number 1.654 when rounded to 3-digits after the decimal point are the same. Another example is 10.890009 and 10.89000. It is noticed that 10.89000 is rounded to 10.89, whereas 10.89009 is not rounded off. This is an inherent issue because of the representational limitations of binary floating point formats. This might have a significant impact when querying involves sorting.