Spilling occurs when an operation cannot keep all required intermediate data in warehouse memory.
Snowflake first spills data to local storage and can spill additional data to remote storage. Storage access is slower than memory access, so substantial spilling can increase query duration.
Increasing the warehouse size provides more compute resources and more memory per execution cluster. This can reduce or eliminate spilling for a memory-intensive query.
Adding clusters to a multi-cluster warehouse primarily improves concurrency by allowing more queries to execute simultaneously. It generally does not assign multiple clusters to accelerate one individual query.
Warehouse auto-suspend does not terminate an actively running query. Auto-suspend occurs after the warehouse has been inactive for the configured period.
References:
Snowflake Documentation - Query Profile: https://docs.snowflake.com/en/user-guide/ui-query-profile Snowflake Documentation - Optimizing warehouses for performance: https://docs.snowflake.com/en/user- guide/performance-query-warehouse
==

A directory table is a special Snowflake-managed table that stores metadata about unstructured data files (such as images, videos) in a stage.
* It supports automatic metadata refresh .
* It enables listing and querying file-level details .
Reference:
Snowflake Docs: Directory Tables

In a CREATE PIPE ... AS COPY ... FROM (....) statement, the supported transformations include filtering data using an optional WHERE clause and omitting columns. The WHERE clause allows for the specification of conditions to filter the data that is being loaded, ensuring only relevant data is inserted into the table.
Omitting columns enables the exclusion of certain columns from the data load, which can be useful when the incoming data contains more columns than are needed for the target table.
References:
[ COF-C03 ] SnowPro Core Certification Exam Study Guide
Simple Transformations During a Load1

When a Snowflake user wants to share a newly created object in a database with consumers, the correct action to take is to use theGRANTprivilege ... TO SHARE command to grant the necessary privileges for the object to be shared. This approach allows the object owner or a user with the appropriate privileges to share database objects such as tables, secure views, and streams with other Snowflake accounts by granting access to a named share.
TheGRANTstatement specifies which privileges are granted on the object to the share. The object remains in its original location; sharing does not duplicate or move the object. Instead, it allows the specified share to access the object according to the granted privileges.
For example, to share a table, the command would be:
GRANTSELECTONTABLEnew_tableTOSHARE consumer_share;
This command grants the SELECT privilege on a table namednew_tableto a share namedconsumer_share, enabling the consumers of the share to query the table.
Automatic sharing, dropping and re-adding the object, or recreating the object with a different name are not required or recommended practices for sharing objects in Snowflake. The use of theGRANTstatement to a share is the direct and intended method for this purpose.
Reference: Snowflake Documentation on Sharing Data (https://docs.snowflake.com/en/user-guide/data- sharing-intro.html)