Snowflake Native Apps Other

Snowflake Native Apps Other#

Multi-Threading#

Currently, Snowflake does not support multi-threading for Native Apps directly. Melissa Native Apps are designed to run single-threaded request on Snowsight or SnowSQL.

You can explore the following options to achieve multi-threading.

  • Create multiple TASK(s) and schedule them to run at the same time.

  • Use Snowflake driver or connector (such as Snowflake JDBC Driver or Snowflake Python Connector) to create multiple connections with Snowflake.

    See more about its limitation at Transactions and Multi-Threading.

Private Connectivity#

Melissa Native Apps are accessible for AWS, Microsoft Azure PrivateLink with some Known Limitations .

Please see more details at Support for Private Connectivity .

Rate Limiting#

The Native Apps follow the same rate limits as the corresponding API endpoints. Please refer to Cloud API Rate Limiting for more details.

Supporting Regions#

Melissa Native Apps are currently available in the following regions and by request. If you do not see your region listed here, please contact a Melissa Sales Representative at SnowflakeMarketplace@Melissa.com.

North America

Amazon Web Service

Microsoft Azure

US West (N. Virginia)

East US 2 (Virginia)

US East (Ohio)

West US 2 (Washington)

US West (Oregon)

Throughput Performance#

The Native Apps utilize Snowflake’s infrastructure to process input data and manage output data seamlessly within the Snowflake platform. Some latency can be expected due to Snowflake’s security mechanisms, which may result in slightly slower performance compared to direct API requests.

Troubleshooting#

This section provides troubleshooting recommendations for common issues encountered when using the Snowflake Native Apps. If you encounter an issue not listed here, please contact SnowflakeSupport@Melissa.com for assistance.

Insufficient Privileges#

Result Message:

Insufficient privileges

Troubleshooting:

Contact your account admin to check the privileges of your role on objects, such as Warehouse, Database, Schema, Tables, Views, etc.

SQL Compilation error#

Result Message:

Name or service not known

Troubleshooting:

Open the Native App, select Settings > Connections > Details, check the following:

  • The Network Rule name.

  • The External Access Integration name.

The endpoint should match the product name. For example, base service URL of GLOBAL_IP is ‘globalip.melissadata.net’.


Result Message:

Integration 'reference('API')' is not enabled.

Troubleshooting:

Open the Native App, select Settings > Connections > Details, make sure the status of the Connections is Connected.


Result Message:

Integration 'reference('API')' does not exist or not authorized.

Troubleshooting:

  • Check if you are running the SQL script from the correct database and schema. See more at Change the context of a Snowflake worksheet .

  • Ensure the stored procedures is installed in CORE schema of the Native App (Data > Databases > YOUR_NATIVE_APP > CORE).

If you don’t see any stored procedures in the CORE schema, refer to the step-by-step guide of your product documentation to complete the Application Configuration step.

Stored Procedure Calls#

Result Message:

Unknown user-defined function

Troubleshooting:

  • Make sure your SQL script is run from the correct application database and schema.

  • Double check the Native App name.

TransmissionResults field contains GE** Code#

Result Message:

GE** code in TransmissionResults.

Troubleshooting:

The GE** or SE** codes indicates Service Level Errors. This could be due to Transmission Error, invalid input, or other issues. Check the Result Codes page of your product for the specific error message. Below are some common GE** Result Codes:

Result Code

Description

GE05

The License Key is invalid.

GE08

The License Key is invalid for this product or level.

If you get License Key related Result Codes, double check that the License Key should be the License Key Using Credits from your Melissa account.

Contents