Our Partnership with Snowflake

• Yes, Snowflake supports stored procedures. A stored procedure is similar to a function; as such, it’s created once and used many times. Using the CREATE PROCEDURE command, you can make it, and with a CALL command, you can execute it. Snowflake storage procedures are written in JavaScript API (in the form of JavaScript methods and objects). 

• Snowflake is a cloud-based Data Warehouse solution presented as a Saas (Software-as-a-Service) with full support for ANSI SQL.

• The Snowflake Time Travel tool provides us with access to past data at any time during the specified period. This enables us to see which data we can edit or delete. This tool is used to accomplish the following tasks:

1. Restore objects associated with data that may have unintentionally been lost.
2. To examine data usage and data changes within a given period.
3. Duplication and backup of data from the most important points of history.

• A virtual warehouse is one or more clusters that approve users for carrying out operations such as data loading, queries, and other DML operations. Virtual warehouses endorse users with the required resources such as CPU, temporary storage to perform various snowflake operations.

• Snowpipe is a constant and cost-effective service that we use to load the data into Snowflake. Systematically Snowpipe loads the file data as soon as it is feasible on the stage. 

• It is an implementation that enables us to create a copy of tables, schemas, and databases without actually copying the data. For performing zero-copy in Snowflake, we must use a keyword named CLONE. This option allows you to obtain real-time data from production and carry out several actions.

• A Snowflake stream keeps track of DML changes to a table. You can use Snowflake streams to:

1. Emulate triggers in Snowflake (unlike triggers, streams don’t fire immediately)
2. Gather changes in a staging table and update some other tables based on those changes at some frequency.

ACCOUNT ADMIN :

• This is the highest level role in Snowflake. It should be heavily limited in access and encapsulate SYSADMIN and security admin

SECURITYADMIN :

• This role is used for managing any object grant globally, and therefore is granted the MANAGE GRANTS privilege by default. This role also inherits the USERADMIN role
• USER ADMIN :
  This role is dedicated to user/role management. By default, this role can create/modify users and their respective roles (assuming those roles/users haven’t been transferred to another role).
• SYSADMIN :
  This role is dedicated to system object management. It is recommended by Snowflake to assign all custom roles to the SYSADMIN role, so this role can grant these privileges to other roles.
• PUBLIC :
  This is a pseudo role that every user/role in the account gets.