Snowflake Data Clean Rooms updates and legacy connector removals

Use cases

Imagine that you manage secure data collaboration environments and need to track your API version and ensure the latest features are active. Changes include:

• API version update to 18.2.
• Removal of legacy identity and activation connectors from the web interface.
• General bug fixes and performance improvements.

How to use

To check the current API environment version in your account, run the following SQL command:

SELECT * FROM SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.ADMIN.VERSION;

What happens in this code:

1. Queries the version table located in the local application database.
2. Returns the current version number of the installed API environment.

If you manage updates manually and need to apply a patch, run the following commands:

USE ROLE SAMOOHA_APP_ROLE;
CALL SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.library.apply_patch();

What happens in this code:

1. Sets the application administrative role.
2. Calls the stored procedure to manually apply the latest patch.

If you prefer to enable automatic updates to avoid manual intervention, run:

USE ROLE SAMOOHA_APP_ROLE;
CALL SAMOOHA_BY_SNOWFLAKE_LOCAL_DB.library.enable_local_db_auto_upgrades();

What happens in this code:

1. Sets the application administrative role.
2. Enables automatic updates so new versions apply without manual effort.

Limitations and requirements

• Existing configurations for the removed connectors are not deleted from your account.
• Web UI users must log out and log back into their session to apply updates.
• Accounts on version 12.3 or earlier require manually re-running the mount procedure before re-enabling automatic upgrades.