finished adding showLineNumbers to snow docs

Author: quetzalliwrites

src/content/docs/snowflake/features/cross-database-resource-sharing.md

@@ -19,7 +19,7 @@ In this guide, we'll walk through a series of Snowflake SQL statements to create
 
 Create three databases to represent the three different organizations that will share resources. In this example, we'll create databases for `db_name1`, `db_name2`, and `db_name3`.
 
-```sql
+```sql showLineNumbers
 CREATE DATABASE db_name1_actual;
 CREATE DATABASE db_name2_actual;
 CREATE DATABASE db_name3_actual;
@@ -29,7 +29,7 @@ CREATE DATABASE db_name3_actual;
 
 Create a schema in each database to represent the shared resources. In this example, you can create a schema called `sch` in each database.
 
-```sql
+```sql showLineNumbers
 CREATE SCHEMA db_name1_actual.sch;
 CREATE SCHEMA db_name2_actual.sch;
 CREATE SCHEMA db_name3_actual.sch;
@@ -39,7 +39,7 @@ CREATE SCHEMA db_name3_actual.sch;
 
 Create a table in each schema to represent the shared resources. In this example, you can create a table called `table1` in `db_name1_actual.sch`, `table2` in `db_name2_actual.sch`, and `table3` in `db_name3_actual.sch`.
 
-```sql
+```sql showLineNumbers
 CREATE TABLE db_name1_actual.sch.table1 (id INT);
 CREATE TABLE db_name2_actual.sch.table2 (id INT);
 CREATE TABLE db_name3_actual.sch.table3 (id INT);
@@ -49,7 +49,7 @@ CREATE TABLE db_name3_actual.sch.table3 (id INT);
 
 You can now insert data into the tables to represent the shared resources. In this example, we'll insert a single row into each table.
 
-```sql
+```sql showLineNumbers
 INSERT INTO db_name1_actual.sch.table1 (id) VALUES (1);
 INSERT INTO db_name2_actual.sch.table2 (id) VALUES (2);
 INSERT INTO db_name3_actual.sch.table3 (id) VALUES (3);
@@ -67,7 +67,7 @@ CREATE VIEW db_name1_actual.sch.view1 AS SELECT * FROM db_name1_actual.sch.table
 
 You can creates a secure view `view3` in `db_name3_actual.sch` by joining data from different tables.
 
-```sql
+```sql showLineNumbers
 CREATE SECURE VIEW db_name3_actual.sch.view3 AS
 SELECT view1.id AS View1Id, table2.id AS table2id, table3.id AS table3id
 FROM db_name1_actual.sch.view1 view1, db_name2_actual.sch.table2 table2, db_name3_actual.sch.table3 table3;
@@ -77,7 +77,7 @@ FROM db_name1_actual.sch.view1 view1, db_name2_actual.sch.table2 table2, db_name
 
 You can create a share `s_actual` and grant usage permissions on the `db_name3_actual` database and its schema.
 
-```sql
+```sql showLineNumbers
 CREATE SHARE s_actual;
 GRANT USAGE ON DATABASE db_name3_actual TO SHARE s_actual;
 GRANT USAGE ON SCHEMA db_name3_actual.sch TO SHARE s_actual;

src/content/docs/snowflake/features/dynamic-tables.md

@@ -37,7 +37,7 @@ The output should be:
 
 You can create a dynamic table using the `CREATE DYNAMIC TABLE` statement. Run the following query to create a dynamic table:
 
-```sql
+```sql showLineNumbers
 CREATE OR REPLACE DYNAMIC TABLE t_12345
     TARGET_LAG = '1 minute' WAREHOUSE = 'test' REFRESH_MODE = auto INITIALIZE = on_create
     AS SELECT id, name FROM example_table_name;

src/content/docs/snowflake/features/iceberg-tables.md

@@ -27,7 +27,7 @@ $ awslocal s3 mb s3://test-bucket
 
 You can create an external volume using the `CREATE OR REPLACE EXTERNAL VOLUME` statement. The external volume is used to define the location of the files that Iceberg will use to store the table data.
 
-```sql
+```sql showLineNumbers
 CREATE OR REPLACE EXTERNAL VOLUME test_volume
     STORAGE_LOCATIONS = (
     (

src/content/docs/snowflake/features/materialized-views.md

@@ -19,7 +19,7 @@ The following sections guide you through creating materialized views, inserting
 
 To create a materialized view, use the `CREATE MATERIALIZED VIEW` statement. The following example creates a view `order_view` that selects specific columns from the `orders` table.
 
-```sql 
+```sql showLineNumbers
 CREATE TABLE IF NOT EXISTS orders (
   id INT,
   product TEXT,

src/content/docs/snowflake/features/polaris-catalog.md

@@ -25,7 +25,7 @@ This guide shows how to use the Polaris REST catalog to create Iceberg tables in
 
 The following command starts the Polaris catalog container using the `localstack/polaris` Docker image:
 
-```bash
+```bash showLineNumbers
 docker run -d --name polaris-test \
   -p 8181:8181 -p 8182:8182 \
   -e AWS_REGION=us-east-1 \
@@ -48,7 +48,7 @@ curl -X GET http://localhost:8182/health
 
 Set variables and retrieve an access token:
 
-```bash
+```bash showLineNumbers
 REALM="default-realm"
 CLIENT_ID="root"
 CLIENT_SECRET="s3cr3t"
@@ -64,7 +64,7 @@ The `TOKEN` variable will contain the access token.
 
 Create a catalog:
 
-```bash
+```bash showLineNumbers
 curl -s -X POST http://localhost:8181/api/management/v1/catalogs \
   -H "Authorization: Bearer $TOKEN" \
   -H "Content-Type: application/json" \
@@ -89,7 +89,7 @@ curl -s -X POST http://localhost:8181/api/management/v1/catalogs \
 
 Grant necessary permissions to the catalog:
 
-```bash
+```bash showLineNumbers
 curl -s -X PUT http://localhost:8181/api/management/v1/catalogs/polaris/catalog-roles/catalog_admin/grants \
   -H "Authorization: Bearer $TOKEN" \
   -H "Content-Type: application/json" \
@@ -108,7 +108,7 @@ awslocal s3 mb s3://$BUCKET_NAME
 
 In your SQL client, create an external volume using the `CREATE EXTERNAL VOLUME` statement:
 
-```sql
+```sql showLineNumbers
 CREATE EXTERNAL VOLUME polaris_volume
 STORAGE_LOCATIONS = (
   (
@@ -126,7 +126,7 @@ ALLOW_WRITES = TRUE;
 
 Create a catalog integration using the `CREATE CATALOG INTEGRATION` statement:
 
-```sql
+```sql showLineNumbers
 CREATE CATALOG INTEGRATION polaris_catalog
 CATALOG_SOURCE = ICEBERG_REST
 TABLE_FORMAT = ICEBERG
@@ -150,7 +150,7 @@ COMMENT = 'Polaris catalog integration';
 
 Now create the table using the Polaris catalog and volume:
 
-```sql
+```sql showLineNumbers
 CREATE ICEBERG TABLE polaris_iceberg_table (c1 TEXT)
 CATALOG = 'polaris_catalog',
 EXTERNAL_VOLUME = 'polaris_volume',

src/content/docs/snowflake/features/row-access-policies.md

@@ -19,7 +19,7 @@ The following sections demonstrate how to create a row access policy, attach it
 
 Use the `CREATE ROW ACCESS POLICY` statement to define a filter condition. This policy will restrict row visibility based on column values.
 
-```sql
+```sql showLineNumbers
 CREATE OR REPLACE ROW ACCESS POLICY id_filter_policy
 AS (id INT) RETURNS BOOLEAN ->
   id IN (1, 2);
@@ -29,7 +29,7 @@ AS (id INT) RETURNS BOOLEAN ->
 
 Create a table and bind the row access policy to one of its columns using the `WITH ROW ACCESS POLICY` clause.
 
-```sql
+```sql showLineNumbers
 CREATE TABLE accounts (
   id INT
 )

src/content/docs/snowflake/features/snowpipe.md

@@ -27,7 +27,7 @@ awslocal s3 mb s3://test-bucket
 
 You can create a stage using the `CREATE STAGE` command. The stage is used to define the location of the files that Snowpipe will load into the table.
 
-```sql
+```sql showLineNumbers
 CREATE STAGE test_stage
   URL='s3://test-bucket'
   CREDENTIALS = (
@@ -68,15 +68,15 @@ Retrieve the `notification_channel` value from the output of the `DESC PIPE` que
 
 You can use the [`PutBucketNotificationConfiguration`](https://docs.aws.amazon.com/AmazonS3/latest/API/API_PutBucketNotificationConfiguration.html) API to create a bucket notification configuration that sends notifications to Snowflake when new files are uploaded to the S3 bucket.
 
-```bash
+```bash showLineNumbers
 awslocal s3api put-bucket-notification-configuration \
     --bucket test-bucket \
     --notification-configuration file://notification.json
 ```
 
 The `notification.json` file should contain the following configuration:
 
-```json
+```json showLineNumbers
 {
   "QueueConfigurations": [
     {

src/content/docs/snowflake/features/stages.mdx

@@ -30,7 +30,7 @@ CREATE OR REPLACE DATABASE snowflake_tutorials;
 
 Similarly, you can create a table using the `CREATE TABLE` command. In this example, you can create a table called `employees` in `snowflake_tutorials.public`:
 
-```sql
+```sql showLineNumbers
 CREATE OR REPLACE TABLE employees (
    first_name STRING ,
    last_name STRING ,
@@ -96,7 +96,7 @@ awslocal s3 cp employees0*.csv s3://testbucket
 
 In this example, you can create a stage called `my_s3_stage` to load data from an S3 bucket:
 
-```sql
+```sql showLineNumbers
 CREATE STAGE my_s3_stage
 STORAGE_INTEGRATION = s3_int
 URL = 's3://testbucket/'
@@ -105,7 +105,7 @@ FILE_FORMAT = csv;
 
 You can further copy data from the S3 stage to the table using the `COPY INTO` command:
 
-```sql
+```sql showLineNumbers
 COPY INTO mytable
 FROM @my_s3_stage
 PATTERN='.*employees.*.csv';

src/content/docs/snowflake/features/storage-integrations.md

@@ -33,7 +33,7 @@ awslocal s3 cp file.csv s3://testbucket
 
 You can now create a Storage Integration named `s_example` which will connect Snowflake to your S3 bucket using the following statement:
 
-```sql
+```sql showLineNumbers
 CREATE STORAGE INTEGRATION s_example
     TYPE = EXTERNAL_STAGE 
     ENABLED = TRUE 
@@ -82,7 +82,7 @@ The expected output is:
 
 You can now create an external stage using the following statement:
 
-```sql 
+```sql showLineNumbers
 CREATE STAGE stage_example
     STORAGE_INTEGRATION = s_example
     URL = 's3://testbucket'

src/content/docs/snowflake/features/streamlit.md

@@ -74,7 +74,7 @@ To connect to the Snowflake emulator while developing locally, Streamlit provide
 
 To run the sample against Snowflake emulator, your local `~/.streamlit/secrets.toml` should look like this:
 
-```toml
+```toml showLineNumbers
 [snowpark]
 user = "test"
 password = "test"