Skip to content

Snowflake

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.

Grade B · dataset: SQL (DDL and rows in the engine’s dialect) · type snowflake

What it is

A Snowflake account. In the test estate it holds the sales model: SKU and customer dimensions and an order-line fact table in QUILLMERE.SALES. The connector reference is SQL warehouses and databases.

Grade

B. The download holds the model. The platform itself needs a vendor account or trial. A Snowflake trial is enough.

See the grade table for all 32 types.

Settings and credentials

From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.

Names
Typesnowflake
Settingsaccount, warehouse, database, schema, username, role, compute_pool, image_repository, runner_image, network_rule, external_access_integration
Credentialspassword

The test connection

Quillmere sales (Snowflake)

SettingTest value
accountquillmere-demo
warehouseFACE_WH
databaseQUILLMERE
schemaSALES
usernameFACE_READER
roleFACE_READ

Credentials: password. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.

Stand up the test system

The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.

  1. Download snowflake.zip and unzip it. It holds snowflake/01_schema.sql, snowflake/02_data.sql and snowflake/expected.json, in the engine’s own dialect.
  2. Run 01_schema.sql, then 02_data.sql, in a worksheet in a Snowflake trial account, or snowsql -f.
  3. Add the connection with the settings above, pointed at your own account.

What FACE finds

Against a real account, FACE reads INFORMATION_SCHEMA. There is no local engine, so the expected model is what that read returns for this dataset.

FACE also reads object tags and masking and row access policies from SNOWFLAKE.ACCOUNT_USAGE.TAG_REFERENCES and POLICY_REFERENCES. It runs two bounded queries per discovery. To allow them, grant the connection’s role IMPORTED PRIVILEGES on the SNOWFLAKE database, or the SNOWFLAKE.OBJECT_VIEWER and SNOWFLAKE.GOVERNANCE_VIEWER database roles. Without that grant, discovery still works and reports tags and policies as not readable. These views lag by up to two hours. The quickstart dataset declares no tags or policies.

DatasetKindDomainPrimary keyRowsFields
SALES.DIM_SKUtableproduct_catalogSKU_ID188
SALES.DIM_CUSTOMERtablecustomersCUSTOMER_ID63
SALES.FACT_ORDER_LINEtableordersORDER_ID, LINE_NO478

Declared foreign keys:

  • SALES.FACT_ORDER_LINE (SKU_ID) references SALES.DIM_SKU (SKU_ID)
  • SALES.FACT_ORDER_LINE (CUSTOMER_ID) references SALES.DIM_CUSTOMER (CUSTOMER_ID)

expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.

How it joins the Quillmere universe

This source carries 4 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.

Universe entityFields hereAlso in
customerDIM_CUSTOMER.CUSTOMER_ID, FACT_ORDER_LINE.CUSTOMER_IDfiles, hubspot, kafka, oms, postgres, redshift, salesforce, sap
customer_poFACT_ORDER_LINE.CUSTOMER_POfiles, hubspot, kafka, oms, postgres
orderFACT_ORDER_LINE.ORDER_IDdocument, files, hubspot, kafka, oms, postgres, sap
skuDIM_SKU.SKU_ID, FACT_ORDER_LINE.SKU_IDims, inventory, logisticsapi, oms, postgres, sap

It holds no evidence for the six planted anomalies. It is context: it makes the shared keys resolve.

See all connectors at once for the walkthrough across every source.

Download

This is one of 25 zips: the 7 streaming types ship as replay recordings instead.

What is in the zip
  • snowflake/01_schema.sql
  • snowflake/02_data.sql
  • snowflake/expected.json

The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.