SnowPro Core RecertificationDemo

Snowsight supports heat grids as a chart type. Dashboards visualize query results using Snowsight charts, so a heat grid can be used in that context.

A Notify & Suspend action notifies account administrators who have enabled notifications and suspends all assigned warehouses only after their currently executing statements have completed. It does not cancel active statements; immediate cancellation is the behavior of Notify & Suspend Immediately.

Snowflake requires the REFERENCE_USAGE privilege on each database referenced by a secure view before the view can be granted to a share. The database containing the secure view instead receives the normal USAGE grant for the share.

Snowflake supports uncorrelated scalar subqueries anywhere a value expression can be used. It also supports EXISTS, ANY / ALL, and IN subqueries in WHERE clauses, whether correlated or uncorrelated.

Virtual-warehouse credits accrue while compute resources are running, with billing based in part on the length of time each cluster runs. Query type, the number of tables or databases queried, and the amount of data stored are not direct determinants of virtual-warehouse compute charges.

Object tags are available to all Snowflake accounts and can be applied to Snowflake objects to track sensitive data and resource usage. Masking policies and row access policies require Enterprise Edition or higher, and the OBJECT_DEPENDENCIES view is also an Enterprise Edition feature.

Transient tables have no Fail-safe period, reducing storage costs for large tables containing transitory data. They are appropriate when the data does not require failure protection and can be reproduced outside Snowflake, while remaining available until explicitly dropped.

Dropping an existing column from a base table suspends every materialized view based on that table, even when the dropped column is not part of the materialized-view definition. The suspended materialized view cannot be used or maintained and must be recreated.

GET_STAGE_LOCATION retrieves the URL for an internal or external named stage from its stage name. The file-URL functions instead generate URLs for staged files and use a stage name plus a relative file path.

Resizing a suspended warehouse does not provision new compute resources immediately. Snowflake provisions the additional compute resources when the warehouse is next resumed.

REST_EVENT_HISTORY returns SCIM REST API requests made to Snowflake during a specified time interval, allowing an administrator to audit identity-provider provisioning activity.

MINS_TO_BYPASS_NETWORK_POLICY is a Snowflake user object property that specifies the temporary period during which a user can access Snowflake without complying with an existing network policy.

Snowsight uses Query History to monitor query activity and Copy History to monitor data-loading activity. These are the two activity-monitoring history pages in the stated navigation area.

Snowflake unloads data from a table or query to an internal or external stage with COPY INTO <location>. COPY INTO @mystage therefore exports data to the named stage; PUT uploads files to a stage and GET downloads files from one.

Initialization measures the time spent setting up query processing.

BUILD_STAGE_FILE_URL generates a Snowflake file URL from a stage name and relative file path. The resulting file URL supports prolonged access and does not expire; access still requires appropriate authorization for the stage.

MIN_DATA_RETENTION_TIME_IN_DAYS is an account-only parameter that establishes the minimum Time Travel retention period for historical data. The effective retention for an applicable object is the greater of DATA_RETENTION_TIME_IN_DAYS and MIN_DATA_RETENTION_TIME_IN_DAYS.

MIN_DATA_RETENTION_TIME_IN_DAYS is an account-level Snowflake parameter and can be set only for an account. It establishes a minimum Time Travel retention period that affects applicable objects.

A scalar function accepts input values and returns exactly one value for each invocation.

The Search Optimization Service creates and maintains search access paths, persistent structures that track which column values might exist in each micro-partition so unnecessary micro-partitions can be skipped during selective lookups.

For an already active session, assigning a user-level network policy whose rules do not match the user’s network location prevents that user from executing any further queries. The policy remains active and does not inherently terminate the session.

For delimited input files, Snowflake expects all records in a file to have the same number of fields. Records with varying lengths produce an error, regardless of the ERROR_ON_COLUMN_COUNT_MISMATCH setting. The field delimiter can be configured, compression is not mandatory, and source files do not universally have to match the target table’s column count.

Snowflake decouples centralized persistent storage from virtual warehouses, which are elastic compute clusters. Compute resources can therefore be independently scaled, including resizing a warehouse up or down, without adding storage. Snowflake key concepts and architecture and Virtual warehouses