Move data shares that are linked to a legacy Snowflake data share target to a Snowflake V2 data share target. Verify that data sharing works before you unlink the legacy target.
Required Editions
Important Don’t unlink an existing data share from its legacy Snowflake data
share target until you verify that the Snowflake V2 connection works. Downstream processes
in Snowflake can refer to the database that was created using the legacy target.
| Available in: All Editions supported by Data 360. See Data 360 edition availability. |
| User Permissions Needed | |
|---|---|
| To link or unlink data shares: | Data Cloud Architect permission set |
Snowflake V2 data share targets replace legacy Snowflake data share targets. Migrate each data share that’s linked to a legacy Snowflake data share target to a Snowflake V2 data share target.
- In Data 360, go to the Data Shares tab.
- Select a data share that’s linked to a legacy Snowflake data share target.
-
Link the data share to a Snowflake V2 data share target.
For more information, see Link or Unlink Data Shares and Data Share Targets.
Note If you see an error stating that you can link only to data share targets of the same type, ignore it. This is a known issue and doesn't block the migration. Click Save to continue. - On the data share’s record home page, confirm that the Snowflake V2 data share target is linked. Then, in Snowflake, confirm that the Snowflake V2 database contains the same objects and data as the legacy database.
-
In Snowflake, swap the Snowflake V2 database into the name used by your existing
pipelines and dashboards.
This swap keeps downstream references working. For the automated skill and the SQL function, see Snowflake documentation.
- On the data share’s record home page, click Link/Unlink Data Share Target.
-
Deselect the legacy Snowflake data share target.
When you unlink the legacy target, you will see a warning to delete the database in the data share target account before you unlink it. For this migration, don’t delete the database. You already swapped the Snowflake V2 database into the existing database name, so you can ignore the warning and click Continue.
- Click Save.