This topic provides answers to common questions about working with Snowflake native Experimentation.
Before you begin setting up the Snowflake integration, read the Snowflake data requirements. Then, follow the setup instructions in Setting up the Snowflake integration.
If you have further questions about the integration, read the sections below.
The role permissions include:
ACCOUNTADMIN role in SnowflakeYou must add to your allow list the following outbound IP addresses:
For a full list of LaunchDarkly’s public IP addresses, read Public IP list.
If you have configured your setup correctly, you will observe your Snowflake dynamic tables being populated with data under the LD_EXPERIMENTATION database and RESULTS_<project_env_key> schema within the next few hours.
Snowflake Data Export runs an hourly job, on the hour, that publishes raw LaunchDarkly data in your Snowflake account. You can expect the new data to be available in your Snowflake account within 10-15 minutes after the hour.
After your integration is set up, you cannot make further edits to it, and you cannot create a second integration using the same project/environment key. If you need to update any fields as part of the integration, you must delete the existing integration and start a new one.
Before you delete an existing integration, stop any running experiments that use warehouse native metrics that are using data from the integration.
When you delete an existing integration the service disconnects from your Snowflake account. However, LaunchDarkly does not delete any stored event data. The LaunchDarkly user interface (UI) will still display related event data in places like the event explorer, the event selection dropdown when creating a metric, and other areas where metric events are visible.
If you want to set up additional integrations for additional LaunchDarkly projects and environments, follow the same setup instructions for the additional integrations, including: