Snowflake for Workflows is currently in preview release and is available to selected customers only. If you would like to share feedback or ideas, join the preview by signing up via the Request access to Snowflake Workflow Connector form or contacting your Customer Success Manager.
For more information, see preview releases.
After you join the preview program for Snowflake for Workflows, we'll provide Hub subscription details. With those subscription details, follow the Add Hub subscriptions procedure to you activate the capability.
Learn how to execute a statement on the Snowflake database and store its results in Grail using the Snowflake for Workflows. You will create a simple workflow that uses the Store Statement Result action.
Have a basic knowledge of Dynatrace Workflows. For more information, see Workflows quick start.
Verify that you configured Snowflake for Workflows setup.
Create a workflow with a single Store Statement Result action.
Go to Workflows and select
Workflow.
In the Select a trigger panel, select one of the available triggers.
On the trigger node, select Add task to browse available actions.
In the Choose action panel, either search for snowflake
or scroll to the Snowflake for Workflows section.
Select the Store Statement Result action.
Select a Connection.
Enter the Statement you want to execute on Snowflake. Keep in mind that the result of this statement will be stored in Grail. For this example, the following SQL query will be executed:
WITH test_data as (SELECTCURRENT_DATE() as date,'true'::boolean as boolean,RANDOM()::number as number,? as unnamed_parameter,:parameter1 as named_parameter)select * from test_data
Please also provide values for the binding parameters used in the query:
1
REAL
0.33
parameter1
TEXT
the value of the named parameter
optional You can also provide more parameters, if needed. You can find the documentation describing all fields in Snowflake for Workflows actions.
Select Run.
Select the Result tab of the executed Store Statement Result action to see how to find your bizevents using the DQL query. For example, the following result:
{"requestId": "some-random-request-id-for-this-specific-execution","event.type": "snowflake_connector","event.provider": "data_connector"}
could be used to find bizevents loaded during this specific execution:
fetch bizevents| filter event.type == "snowflake_connector"| filter requestId == "some-random-request-id-for-this-specific-execution"
It might take a few minutes after the action finishes before the events are visible in Grail.