Query your data in Snowflake

If you have created Snowflake resources by following this guide and deployed the pipeline using the default or secure, you will have a Snowflake database where all of your enriched data is stored.

Since Snowflake Loader only allows to load enriched data to Snowflake, your Snowflake database will contain only atomic schema that contains your rich, high quality data. It will not contain atomic_bad schema, unlike Postgres variant.

To query the good data in atomic.events, you will first need to connect to your Snowflake database.

There is two different ways to connect to Snowflake database:
Use snowflake_loader_user that is output by Snowflake Terraform module. The password for this user is the password you've passed as snowflake_loader_password to Snowflake Terraform module.
Grant snowflake_loader_role that is output by Snowflake Terraform module to a Snowflake user you have access and connect to database with credentials of this user.
Either Snowflake dashboard or SnowSQL can be used to connect to Snowflake database and query data in there.
Run a query against your atomic.events table to take a look at the page view event that you generated in the previous step (where event_name = ‘page_view’). You can understand more about each field in the canonical event here.
SELECT * FROM atomic.events WHERE event_name = 'page_view';

By default, there are 5 enrichments enabled, as listed below. These enrichments add extra properties and values to your events in real time as they are being processed by the Enrich application.

Some enrichments are legacy and therefore populate your atomic columns. From the above list, these are the campaign attribution, referer parser and event fingerprint enrichments. The UA parser and YAUAA enrichment also add a separate entity to each event (these are also referred to as contexts since they add additional context to the events). The contexts are loaded into separate columns:

contexts_com_snowplowanalytics_snowplow_ua_parser_context_1
contexts_nl_basjes_yauaa_context_1