Author name: Abhay

Yesterday you mastered getting data into Snowflake with COPY INTO <table>. Today we flip the direction: getting data out. The COPY INTO <location> command unloads data from tables (or query results) into files on a stage or directly into cloud storage. Here’s what most people don’t expect: by default, Snowflake splits your output into multiple […]

Yesterday you learned where files land before loading — stages. Today you learn how the data actually gets from those files into a table. Two pieces work together: file formats tell Snowflake how to interpret your files (CSV delimiters, JSON nesting, Parquet columns), and COPY INTO <table> is the command that moves the data. Here’s

Welcome to Domain 3 — Data Loading & Connectivity. This domain is 18% of the COF-C03 exam, and it starts with a concept that underpins everything else in data loading: stages. Before a file can be loaded into a Snowflake table, it has to land somewhere first — that “somewhere” is a stage. Think of

That’s Domain 2 in the bag. Over the past seven days (Days 16-22), you’ve covered RBAC, DAC, system-defined roles, authentication methods, network policies, dynamic data masking, row access policies, object tagging, data classification, encryption, replication, failover, and cost management with resource monitors. Domain 2 is worth 20% of the COF-C03 exam — roughly 12-13 questions

Yesterday we wrapped up the security side of governance — encryption keys, replication, failover, and data lineage. Today we’re switching to the money side: how Snowflake charges for compute, how you control spending with resource monitors, and where to find the cost data the exam expects you to know. Here’s the thing that trips people