The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Recommended

Setting up zero-copy V2 between Salesforce Data Cloud and Snowflake (opens in a new tab)

You will learn the setup steps for the Zero-Copy V2 connector, including the enrollment code handoff, consumer grants and legacy schema aliases.

Why read this

You will also see where change tracking via streams failed in one test.

  1. Create connector and get Enrollment ID
  2. Create Snowflake V2 target in Salesforce
  3. Link Data Share to the target
  4. Mount shared data and grant access
The V2 setup runs between the Snowflake admin and the Salesforce admin in four steps

The author revisits connecting Salesforce data to Snowflake and reports that the V2 connector simplifies setup. The enrollment code replaces manual credential configuration, authentication uses OpenID Connect, and friendly names reduce SQL cleanup. Legacy schema aliases and grant comparisons before and after migration help keep existing access intact.

The walkthrough covers creating the connector and retrieving the Enrollment ID, then the Salesforce-side steps: creating a Snowflake V2 Data Share target, linking a Data Share to it, and mounting the shares in Snowflake as a linked database. It also covers granting usage and select privileges on existing and future views to the consuming role, and the choice between legacy and friendly naming.

The author’s incremental test did not work. A stream on an exposed view failed with a change tracking error involving unmanaged Iceberg tables, so current-state queries worked but change feeds did not through that path. The author recommends confirming the supported source object and stream setup, then testing inserts, updates and deletes end to end before relying on downstream history.

Read the original at dev.to (opens in a new tab)

Worth reading?