<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aman Gupta on Medium]]></title>
        <description><![CDATA[Stories by Aman Gupta on Medium]]></description>
        <link>https://medium.com/@amangupta_data?source=rss-5ad179c3e241------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*urLwLT4ZjdwWsO1dP9TEbA.jpeg</url>
            <title>Stories by Aman Gupta on Medium</title>
            <link>https://medium.com/@amangupta_data?source=rss-5ad179c3e241------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:55:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amangupta_data/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[End-to-End SQL Server to Snowflake Migration in Single Flow:Powered by SnowConvert AI]]></title>
            <link>https://medium.com/snowflake/end-to-end-sql-server-to-snowflake-migration-in-single-flow-powered-by-snowconvert-ai-c2370e484233?source=rss-5ad179c3e241------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2370e484233</guid>
            <category><![CDATA[snowconvert]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <category><![CDATA[snowflake]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Aman Gupta]]></dc:creator>
            <pubDate>Wed, 17 Dec 2025 23:02:23 GMT</pubDate>
            <atom:updated>2025-12-17T23:02:23.023Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HmkURC3ere-2gxweCB-GKA.png" /></figure><p>Modernizing existing data systems such as Teradata, Oracle, SQL Server, Amazon Redshift, Azure Synapse, Google BigQuery, Netezza, PostgreSQL, Spark SQL, Databricks SQL to Snowflake has traditionally meant stitching together multiple tools for code conversion, data movement, and validation. <strong>SnowConvert AI</strong> changes that for all of these platforms (and many others listed <a href="https://docs.snowflake.com/en/migrations/snowconvert-docs/general/about#snowconvert-ai-capabilities">here</a>), it provides a single, powerful experience to convert code from supported data systems, verify it, and prepare it for deployment to Snowflake (based on capabilities). And for <strong>SQL Server and Amazon Redshift specifically</strong>, SnowConvert AI also adds an integrated, end-to-end flow to deploy the converted schema, migrate data, and validate the results all from one UI, in one go.</p><h4><strong>1. What Is SnowConvert AI?</strong></h4><p><a href="https://docs.snowflake.com/en/migrations/snowconvert-docs/overview"><strong>SnowConvert AI</strong></a> is Snowflake’s free, AI-powered migration solution that understands SQL code from different data systems and converts it into Snowflake-native SQL and JavaScript procedures, while also helping you deploy objects, move data, and validate the results.</p><p>Below is a hands-on walkthrough using a SQL Server → Snowflake migration to show how SnowConvert AI handles code conversion, deployment, data migration, and validation in one flow.</p><p>At a high level, SnowConvert AI does the following:</p><ul><li><strong>Code extraction</strong> — Pulls DDL and procedural code directly from SQL Server, or ingests pre-extracted .sql files from a folder structure.</li><li><strong>Automated code conversion</strong> — Parses T‑SQL (tables, views, procedures, functions, DML) and generates equivalent Snowflake SQL or JavaScript-based stored procedures, with rich warnings and issue codes. Preview capabilities to <strong>convert SSIS packages and Informatica workflows to dbt projects</strong> on Snowflake, and to <strong>repoint Power BI reports from SQL Server/Oracle to Snowflake</strong>, are also available in SnowConvert AI.</li><li><strong>AI-powered verification &amp; repair</strong> — Uses <strong>AI Verification</strong> in Snowflake plus the <strong>SnowConvert AI Migration Assistant</strong> in VS Code to automatically generate tests, run them against Snowflake, and suggest code fixes where needed.</li><li><strong>Deployment</strong> — Connects to your Snowflake account and deploys converted code in dependency-safe order (databases → schemas → tables → views → functions → procedures).</li><li><strong>Data migration</strong> — For SQL Server (and Redshift), runs an integrated data migration flow that pulls rows from the source and loads them into the corresponding tables in Snowflake.</li><li><strong>Data validation</strong> — Compares structure and metrics between source and target (row counts, min/max, averages, distinct counts, etc.) so you can trust that data landed correctly.</li></ul><p>For SQL Server specifically, there is also a dedicated <a href="https://docs.snowflake.com/en/migrations/guides/sqlserver"><strong>SQL Server to Snowflake migration guide</strong></a> and a <strong>SnowConvert AI for SQL Server</strong> documentation set that explains coverage and patterns.</p><h4><strong>2. The End-to-End Flow at a Glance</strong></h4><p>For a SQL Server → Snowflake migration, an <strong>ideal SnowConvert AI flow</strong> looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OHX5avult8euRCBZkmUk9Q.png" /></figure><p>The next sections unpack each step at a practical, “how to actually do this” level.</p><h4><strong>3. Prerequisites and Environment Setup</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wd0sHShk6MteDJmCOCJKQA.png" /><figcaption>Prerequisite</figcaption></figure><h4><strong>4. Installing and Activating SnowConvert AI</strong></h4><p><strong>4.1 Downloading from Snowsight</strong></p><ol><li>Log in to <strong>Snowsight</strong>.</li><li>Open <strong>Ingestion</strong> → <strong>Migrations → SnowConvert AI</strong>.</li><li>Download the installer for your OS, SnowConvert AI is free.</li></ol><p><strong>4.2 Installation and Activation</strong></p><ol><li>Run the installer and complete setup.</li><li>Launch <strong>SnowConvert AI</strong>.</li><li>On first launch you can go to help, Click <strong>Get an Access Code</strong> to request activation code.</li></ol><p>Source code and reports remain <strong>local</strong>. For AI verification/data migration, SnowConvert AI connects to Snowflake but does not upload your source code only operational metadata and test artefacts.</p><h4><strong>5. Creating Your First Migration Project</strong></h4><p><strong>5.1 Project Setup</strong></p><ol><li>Open <strong>SnowConvert AI</strong> → <strong>New Project</strong>.</li><li>Provide:</li></ol><ul><li><strong>Project name</strong> — e.g., SnowConvertAI_SQLServer_Snowflake_Migration</li><li><strong>Source platform</strong> — SQL Server</li><li><strong>Target platform</strong> — Snowflake</li><li><strong>Project directory</strong> — local folder for inputs/outputs/reports</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_XRU7VtJ-hZ-_vLz0tMltA.png" /><figcaption>New Project Page</figcaption></figure><p>3. Choose <strong>method to add code to your project</strong>:</p><ul><li>Direct extraction from SQL Server</li><li>Pre-extracted code from local folders</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cJt_ZCFWtRKxR9fjvx6fEw.png" /><figcaption>Add Code Page</figcaption></figure><h4><strong>6. Extracting SQL Server Code</strong></h4><p><strong>6.1 Direct Extraction from SQL Server</strong></p><p>Use this when the workstation can connect to SQL Server.</p><ol><li>Click extract Code, Enter: Server name or IP, Port (1433 by default), Database name, Credentials, add path where project should be saved.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q7K_AgX68O7tQwurKxhaOg.png" /><figcaption>SQL Server Connection Details</figcaption></figure><p>2. Test connection → Click Save &amp; go to extraction.</p><p>3. <strong>Select objects to extract</strong> object types:</p><ul><li>Tables</li><li>Views</li><li>Stored procedures</li><li>Functions</li></ul><p>4. Click Extract Objects.</p><p>SnowConvert AI writes extracted objects into the project’s input folder, organized by database/schema.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lpew7ma5a_3vA5RstbWVPQ.png" /></figure><p><strong>6.2 Using Pre-Extracted Code</strong></p><p>If you already have .sql scripts extracted (use official extraction method — <a href="https://docs.snowflake.com/en/migrations/snowconvert-docs/general/getting-started/code-extraction/sql-server"><em>code extraction</em></a>) organise them in subfolders of objects and respective SQL files.</p><p>In <strong>Extraction</strong>, choose <strong>already have code </strong>and point to the path, SnowConvert AI infers object types and schemas from the folder structure.</p><p>SnowConvert AI then scaffolds project navigation for <strong>Extraction</strong>, <strong>Conversion</strong>, <strong>AI Verification</strong>, <strong>Deployment</strong>, <strong>Data Migration</strong>, and <strong>Data Validation</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9-f7KgBoK7M8dirH9RTxhg.png" /><figcaption>SnowConvert AI Features</figcaption></figure><h4><strong>7. Automated Code Conversion (T‑SQL → Snowflake)</strong></h4><p><strong>7.1 Running the Conversion</strong></p><ol><li>Open <strong>Conversion</strong>.</li><li>(Optional) Adjust <strong>mapping/naming</strong>: Table renames, Schema renames.</li><li>Click <strong>Start Conversion</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GJrGHIxHxNbJzLJUU473cQ.png" /><figcaption>Conversion Status</figcaption></figure><p>SnowConvert AI:</p><ul><li>Parses SQL Server objects into Snowflake standard DDLs.</li><li>Applies SQL Server → Snowflake rules to generate Snowflake SQL or JavaScript-based stored procedures.</li></ul><p>When done, review:</p><ul><li>Conversion success rates.</li><li><strong>EWIs</strong> (Errors, Warnings, Issues) per object.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hd9MRaMS-NsrmteezJdzcg.png" /><figcaption>Conversion Results Page</figcaption></figure><p><strong>7.2 EWIs and Severity</strong></p><p>EWIs are grouped by severity:</p><ul><li><strong>Critical</strong> — parsing/syntax failures; code not understood.</li><li><strong>High</strong> — serious semantic/functional differences.</li><li><strong>Medium</strong> — lower-impact issues (patterns, edge cases) needing review.</li><li><strong>Low</strong> — informational/performance/style suggestions.</li></ul><p>SnowConvert AI inserts EWI comments (e.g., SSC-EWI-####) into the output. You should resolve and then remove these before production deployment. For more details visit <a href="https://docs.snowflake.com/en/migrations/snowconvert-docs/general/technical-documentation/issues-and-troubleshooting/conversion-issues/README">EWIs</a> Page.</p><h4><strong>8. AI-Assisted Code Verification and Fixes</strong></h4><p>SnowConvert AI layers AI-assisted verification and repair on top of deterministic conversion.</p><p>Two main tools:</p><ol><li><strong>AI Verification</strong> (public preview) inside SnowConvert AI. (covered below)</li><li><strong>SnowConvert AI Migration Assistant</strong> in VS Code. (<a href="https://docs.snowflake.com/en/migrations/snowconvert-docs/migration-assistant/getting-started">Migration Assistant</a>)</li></ol><p><strong>8.1 AI Verification (Public Preview)</strong></p><p>AI Verification (Public Preview) automatically tests converted SQL in a Snowflake test account.</p><p>High-level steps:</p><ol><li>Complete deterministic conversion.</li><li>In SnowConvert AI, click <strong>Go to AI Verification</strong>.</li><li>Connect a <strong>non-production Snowflake account</strong> with:</li></ol><ul><li>CREATE DATABASE and CREATE MIGRATION.</li><li>AI SQL / Cortex functions enabled.</li></ul><p>4. Select objects (dependencies auto-included).</p><p>5. Click <strong>Verify code</strong>.</p><p>Under the hood, AI Verification:</p><ul><li>Builds <strong>synthetic datasets</strong> in Snowflake.</li><li>Generates and runs <strong>unit tests</strong> for your converted code.</li><li>Uses <strong>Cortex AI</strong> to propose fixes where tests fail.</li><li>Marks each object as <em>Verified</em>, <em>Suggested fixes</em>, <em>Could not verify with issues</em>, or <em>could not process</em>.</li></ul><p>You then review diffs (original vs. converted vs. AI-fixed) and accept/reject changes.</p><p><strong>Cost Note:</strong> AI Verification consumes Snowflake credits as under the hood it uses cortex services.</p><p>Combined, deterministic rules + AI Verification + Migration Assistant give you a tight loop: <strong>convert → verify → explain → fix → re-verify</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kaCFYXgI_cybzL4j8DjJSA.png" /><figcaption>SnowConvert AI Verification Screen</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pJjwilYQVmHoh4lnen_hrQ.png" /><figcaption>Verification Completed</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gOin8GvK0e3zhJo1GM71Ag.png" /><figcaption>Object Details which have Issue</figcaption></figure><h4><strong>9. Deploying Converted Objects to Snowflake</strong></h4><p><strong>9.1 Connecting to Snowflake</strong></p><ol><li>Open <strong>Deployment</strong>.</li><li>Add a <strong>Snowflake connection</strong>: Account URL, Username, Auth (Password, PAT)</li><li>Test Connection.</li></ol><p><strong>9.2 Deployment Configuration</strong></p><p>Decide whether to deploy:</p><ul><li><strong>All objects</strong> — DBs, schemas, tables, views, functions, procedures.</li><li><strong>Child objects only</strong> — into existing DBs/schemas.</li></ul><p>Then configure: Which objects/groups to deploy, Overwrite behaviour (CREATE OR REPLACE vs. skip existing).</p><p><strong>9.3 Deployment Order and Results</strong></p><p>SnowConvert AI respects dependencies:</p><p>Databases → Schemas → Tables → Views → Functions → Stored procedures</p><p>After deployment you see:</p><ul><li>Success/failure for each object.</li><li>Error messages for failures (e.g., privileges, missing dependencies).</li><li>Downloadable logs.</li></ul><p>When you change code, you can re-deploy only affected objects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H8G8TkJZPt3U4hlp1SY-Ug.png" /><figcaption>Deployment Status</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4gocfwgOuqdoLxNb6aWvQg.png" /><figcaption>Deployment Results</figcaption></figure><h4><strong>10. Migrating Data from SQL Server to Snowflake (Public Preview)</strong></h4><p>SnowConvert AI’s <strong>Data Migration</strong> flow handles SQL Server and Redshift data loads.</p><p><strong>10.1 Prerequisites</strong></p><p>Confirm:</p><ul><li>Target tables already exist in Snowflake (deployed via SnowConvert AI).</li><li>SQL Server source connection is configured and reachable.</li><li>Snowflake connection has rights to load into those tables.</li></ul><p><strong>10.2 Running Data Migration</strong></p><ol><li>Open <strong>Data Migration</strong> → <strong>Migrate data or click Go to Data Migration </strong>after Deployment.</li><li>Provide Connection Details of Source Legacy Env and Target Snowflake.</li><li>On <strong>Select tables to migrate</strong>: Choose tables, Filter by schema/table if needed.</li><li>Click <strong>Migrate data</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NZk65XmUSW1CUG9WgXQnnQ.png" /><figcaption>Migration Results Page</figcaption></figure><p>SnowConvert AI will:</p><ul><li>Extract data from SQL Server tables.</li><li>Load it into matching Snowflake tables via efficient patterns.</li></ul><p>The <strong>Results</strong> page shows: Tables migrated, Rows loaded, Status and errors, a <strong>Retry data migration</strong> option for failed tables.</p><h4><strong>11. Validating Schema and Data (Public Preview)</strong></h4><p>SnowConvert AI includes <strong>schema</strong> and <strong>data metrics</strong> validation, currently in <strong>public preview</strong>.</p><p><strong>11.1 Schema Validation</strong></p><p>Checks equivalence of:</p><ul><li>Table names</li><li>Column names and order</li><li>Data types</li><li>Character max lengths</li><li>Numeric precision/scale</li><li>Row counts</li></ul><p><strong>11.2 Metrics Validation</strong></p><p>Compares aggregate metrics between source and target:</p><ul><li>Min / Max</li><li>Average</li><li>Null count</li><li>Distinct count</li><li>Standard deviation</li><li>Variance</li></ul><p>This helps confirm that structure and statistical properties are preserved.</p><p><strong>11.3 Running Data Validation</strong></p><ol><li>Open <strong>Validate Data or Click Go to validation </strong>after Migration is done.</li><li>Select tables.</li><li>Start validation.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T9mojxuhy6pGCt09qLmgGQ.png" /><figcaption>Validation Progress</figcaption></figure><p>SnowConvert AI:</p><ul><li>Reads relevant metadata and aggregates from SQL Server and Snowflake.</li><li>Compares them and flags mismatches.</li><li>Presents a per-metric, per-table result summary.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HJQXbgNtD4-B5GjqFk4Z2A.png" /><figcaption>Validation Results Success</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_LR-SRUGZlMDtVjCm3LUug.png" /><figcaption>Validation Results with Status</figcaption></figure><p>Use this to investigate anomalies (e.g., row count differences) and decide whether to re-run migrations or adjust target definitions.</p><h4><strong>12. Best Practices and Catches</strong></h4><p>Patterns that help migrations succeed:</p><ul><li><strong>Use waves, not big bang</strong> — Group objects by subject area and iterate extraction → conversion → deployment → migration → validation.</li><li><strong>Treat AI as a co-pilot</strong> — Let AI Verification/Migration Assistant propose fixes, but review them especially in regulated or high-risk domains.</li><li><strong>Separate DEV/TEST and PROD</strong> — Use dedicated Snowflake roles/accounts for AI Verification and initial migrations; keep production strictly controlled.</li><li><strong>SnowConvert AI Volume handling</strong> — The integrated data migration experience in SnowConvert AI is ideal for pilots, smaller to medium sized environments (Recommended Size under 100 GB for larger Systems you can check <a href="https://docs.snowflake.com/en/user-guide/data-integration/openflow/about">Snowflake Openflow</a>), and many production workloads where simplicity and end-to-end visibility matter as much as raw throughput.</li></ul><h4><strong>13. Conclusion</strong></h4><p>SnowConvert AI is more than a code converter; it’s evolving into a <strong>full migration workbench</strong> for existing systems → Snowflake, combining:</p><ul><li>Deterministic SQL Translation,</li><li>AI-Assisted Verification and Repair,</li><li>Integrated Deployment,</li><li>Data Migration,</li><li>And public-preview Data Validation.</li></ul><p>Used thoughtfully, SnowConvert AI lets you move from an existing data warehouse system to a production-ready Snowflake implementation <strong>faster</strong>, with <strong>fewer moving parts</strong>, and with <strong>much higher confidence</strong> in the outcome.</p><p>Official Documentation:</p><p><a href="https://docs.snowflake.com/en/migrations/snowconvert-docs/overview">SnowConvert AI</a>, <a href="https://docs.snowflake.com/en/migrations/snowconvert-docs/general/frequently-asked-questions-faq">SnowConvert AI FAQs</a>, <a href="https://docs.snowflake.com/en/migrations/snowconvert-docs/migration-assistant/README">Migration Assistant</a>, <a href="https://docs.snowflake.com/en/migrations/snowconvert-docs/snowconvert-ai-verification">AI Verification</a></p><p>Embarking on a Migration journey? Share your experiences or questions in comments, and let’s navigate the path to Snowflake together. Looking for more insights on cloud data platforms, ETL processes and Migrations? Feel free to reach out on LinkedIn <a href="http://www.linkedin.com/in/amangupta-data"><strong><em>Aman Gupta</em></strong></a> or comment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2370e484233" width="1" height="1" alt=""><hr><p><a href="https://medium.com/snowflake/end-to-end-sql-server-to-snowflake-migration-in-single-flow-powered-by-snowconvert-ai-c2370e484233">End-to-End SQL Server to Snowflake Migration in Single Flow:Powered by SnowConvert AI</a> was originally published in <a href="https://medium.com/snowflake">Snowflake Builders Blog: Data Engineers, App Developers, AI, &amp; Data Science</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Converting Oracle DDLs to Snowflake DDLs for Migration]]></title>
            <link>https://medium.com/@amangupta_data/converting-oracle-ddls-to-snowflake-ddls-for-migration-aba4cf352f19?source=rss-5ad179c3e241------2</link>
            <guid isPermaLink="false">https://medium.com/p/aba4cf352f19</guid>
            <category><![CDATA[migration]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[snowflake]]></category>
            <category><![CDATA[data-engineering]]></category>
            <dc:creator><![CDATA[Aman Gupta]]></dc:creator>
            <pubDate>Sun, 10 Nov 2024 14:10:06 GMT</pubDate>
            <atom:updated>2024-11-11T13:26:49.748Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iDSYid-B30QPnWe-YSm_Rg.png" /></figure><h3>Introduction</h3><p>As businesses move towards cloud-based data warehousing solutions, Snowflake has emerged as a leading platform due to its scalability, performance, and ease of use. One of the challenges faced during this transition is converting existing Oracle/SQL Server database schemas (DDLs) to Snowflake-compatible DDLs. In this article, we’ll explore practical ways to convert Oracle DDLs (Similar Methods can we used for SQL Server also) to Snowflake DDLs and provide an example to illustrate the process.</p><h3>Understanding the Differences</h3><p>Before diving into the conversion process, it’s important to understand the key differences between Oracle and Snowflake:</p><p><strong>→ Data Types</strong>: Snowflake’s data types may differ from Oracle’s. For instance, Snowflake uses VARCHAR instead of VARCHAR2, VARIANT or VARCHAR instead of CLOB or BLOB, and NUMBER instead of DECIMAL or INTEGER. <em>One Key Difference is Oracle Stores Date and Date Time both as DATE Datatype whereas Snowflake has two different Data Types DATE for Storing only Date part and TIMESTAMP_LTZ to store Date Time</em>.<br> → <strong>Constraints</strong>: Snowflake does not enforce primary key, unique key, and foreign key constraints. Only NOT NULL is enforced; the rest are supported for migration purposes.<br> → <strong>Storage</strong>: Snowflake provides cloud storage as SaaS thus no Management is need, hence storage-related attributes in Oracle DDLs are not applicable, such as tablespace names, Storage, Logging etc.<br> → <strong>Indexes</strong>: Snowflake does not support indexes, thus Index statements can be excluded from DDLs.<br> → <strong>Partitions</strong>: Snowflake does not support physical table partitioning that is present in traditional databases; hence, these are not needed in DDLs.</p><h3>Conversion Methods</h3><ol><li><strong><em>Manual Conversion<br></em></strong>The most straightforward method is to manually convert each Oracle DDL statement to Snowflake syntax. This approach gives you full control over the conversion but can be time-consuming for large schemas it should only be used for small number of basic tables or for someone if they are trying to do a POC or testing to understand Snowflake.</li></ol><pre>Example:<br>Oracle DDL:<br>CREATE TABLE EMPLOYEES (<br> EMPLOYEE_ID NUMBER<br> ,FIRST_NAME VARCHAR2(100)<br> ,LAST_NAME VARCHAR2(50)<br> ,EMAIL VARCHAR2(100)<br> ,HIRE_DATE DATE <br> ,DOB DATE<br> ,FREE_TEXT CLOB <br> ,SEMISTRUCTURED_TEXT BLOB<br> );<br><br>Snowflake DDL:<br>CREATE TABLE EMPLOYEES (<br> EMPLOYEE_ID NUMBER<br> ,FIRST_NAME VARCHAR(100)<br> ,LAST_NAME VARCHAR(50)<br> ,EMAIL VARCHAR(100)<br> ,HIRE_DATE DATE<br> ,DOB TIMESTAMP_NTZ <br> ,FREE_TEXT VARCHAR <br> ,SEMISTRUCTURED_TEXT VARIANT<br> );<br></pre><p>2. <strong><em>Dynamic Custom Scripting for Bulk Migration<br></em></strong>When faced with the challenge of migrating hundreds or even thousands of tables, the manual method becomes impractical. To efficiently handle large-scale migrations, a dynamic approach is essential for generating Snowflake converted DDLs in bulk and then executing them within Snowflake.</p><p>This method leverages system tables (ALL_TABLES and ALL_TAB_COLUMNS) to retrieve table names and column details from the database. We then dynamically convert data types using case statements, transforming Oracle data types to their Snowflake equivalents. These case statements are driven by specific use cases and can be adapted as needed to fit the requirements of the migration project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F39-Jpq6_r20XTznRrmsAg.png" /><figcaption>SQL Snippet</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CwmTmX1JQx33YbtZu643WA.png" /><figcaption>Create Statement with Converted Data Types</figcaption></figure><p>The SQL statement mentioned above can be executed in bulk for multiple tables. These DDLs can either be executed manually in Snowflake or placed in a DevOps repository for execution. Alternatively, a dynamic procedure can be created in Snowflake to execute these DDLs and capture logs. Additionally, new schema names and other constant prefixes can be incorporated into the SQL as per the requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9poBFn07GB82QSdXkq2iYg.png" /></figure><p>Dynamic Scripting can be used to also Generate Primary Key, Unique Key and Foreign Key Constraints, with ALL_CONSTRAINTS and ALL_CONS_COLUMNS system tables. Reach out if more details are needed on Generating Keys.</p><p><em>Note: This method of Dynamic Custom Scripting can be even used for SQL Server, the logic remains same only Functions and Case Statement Changes as per SQL Server.</em></p><p>3. <strong><em>Automated Tools</em></strong><br>Several automated tools can help with the conversion process but will incur cost and are mostly paid. These tools can parse Oracle DDLs and generate equivalent Snowflake DDLs.</p><p>→Schema Conversion Tools: Tools like AWS Schema Conversion Tool (SCT) can automate the conversion process.<br> →Third-Party Services: Companies specializing in data migration may offer services to convert DDLs. Snowflake provides <a href="https://www.snowflake.com/en/migrate-to-the-cloud/snowconvert/">SnowConvert</a> as accelerator for conversion, if it fits the Requirement and Cost this can be explored.</p><p>One other way not in the above list is using Snowflake inbuilt AI function Cortex Complete, its still dependent on accuracy of the Model for the results but if someone wants to try and automate using AI this feature can be used. Token Limitation and Accuracy can be a Challenge in this Approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*11nwmC-AsBXYofrmYuidzw.png" /></figure><h3>Post-Conversion Considerations</h3><p>After converting the DDLs, you should:<br><em>Review and Test:</em> Ensure that the converted DDLs accurately reflect the original schema and test them thoroughly.<br><em>Optimize:</em> Take advantage of Snowflake’s features, such as clustering keys, to optimize performance.<br><em>Data Migration:</em> Plan the <a href="https://medium.com/@amangupta_data/navigating-the-cloud-migration-from-oracle-exadata-to-snowflake-388be55c96da">data migration</a> process, which may involve exporting data from Oracle and importing it into Snowflake.</p><h3>Conclusion</h3><p>Converting Oracle DDLs to Snowflake DDLs is a critical step in migrating to the Snowflake data platform. Whether you choose manual conversion, automated tools, or custom scripts, it’s essential to understand the differences between the two systems and thoroughly test the converted schemas. With careful planning and execution, you can ensure a smooth transition to Snowflake.</p><p>Embarking on a DDL conversion journey? Share your experiences or questions in comments, and let’s navigate the path to Snowflake together. Looking for more insights on cloud data platforms and ETL processes? Feel free to reach out on LinkedIn <a href="http://www.linkedin.com/in/amangupta-data"><strong><em>Aman Gupta</em></strong></a> or comment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aba4cf352f19" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Choosing the Right ETL Tool for Cloud Migration to Snowflake]]></title>
            <link>https://medium.com/@amangupta_data/choosing-the-right-etl-tool-for-cloud-migration-to-snowflake-d545d76a7148?source=rss-5ad179c3e241------2</link>
            <guid isPermaLink="false">https://medium.com/p/d545d76a7148</guid>
            <category><![CDATA[etl]]></category>
            <category><![CDATA[snowflake]]></category>
            <category><![CDATA[data-engineering]]></category>
            <dc:creator><![CDATA[Aman Gupta]]></dc:creator>
            <pubDate>Thu, 24 Oct 2024 18:31:59 GMT</pubDate>
            <atom:updated>2024-10-24T18:39:13.948Z</atom:updated>
            <content:encoded><![CDATA[<p>After my last post on <a href="https://medium.com/@amangupta_data/navigating-the-cloud-migration-from-oracle-exadata-to-snowflake-388be55c96da">Cloud Migration</a>, few Data Engineers asked me on how to decide which ETL tool to select for the Migration.<br>Below is a Guide on Same based on my Experience and Research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fvcoR3AXmjAo_UIS1lM_Nw.png" /></figure><h3>Introduction</h3><p>Embarking on a cloud migration project from traditional databases to Snowflake is a significant step towards modernizing data infrastructure. A critical component of this migration is the Extract, Transform, Load (ETL) process. Selecting the right ETL tool is paramount to ensure a smooth transition and to leverage the full potential of Snowflake. In this post, we’ll explore the key factors to consider when choosing an ETL tool for cloud migration project.</p><h3>Assessing the Current Environment</h3><p>Before diving into the sea of ETL tools, take a comprehensive look at your current environment. Understand the complexity of existing data, the volume, the sources, and the frequency of updates. This assessment will guide you in finding an ETL tool that can handle your specific requirements.</p><h3>Key Considerations for ETL Tool Selection</h3><p>1.Scalability<br>Snowflake’s architecture allows for seamless scalability. Your ETL tool should be able to scale accordingly, handling increased data loads without performance degradation.</p><p>2.Connectivity<br>Ensure the ETL tool offers robust connectivity options. It should easily connect with your traditional databases and other data sources, as well as with Cloud Databases like Snowflake.</p><p>3.Transformation Capabilities<br>The ability to perform complex transformations is a must. The tool should provide a rich set of features to transform data (Joins, Filters, Router, Aggregations, Lookups) according to your business logic.</p><p>4.Performance<br>Performance is critical. Look for tools that can process large datasets efficiently and leverage Snowflake’s performance features, such as multi-cluster warehousing.</p><p>5.Ease of Use<br>An intuitive user interface and ease of use will reduce the learning curve and facilitate a faster migration process.</p><p>6.Cost<br>Consider the cost of the tool in relation to its features. A cost-effective solution that meets your needs can provide a better return on investment.</p><p>7.Support and Community<br>A strong support system and an active community can be invaluable resources. They can assist with troubleshooting and best practices during and after the migration.</p><h3>Popular ETL Tools for Snowflake Migration</h3><p>Several ETL tools have gained popularity for Snowflake migrations, each with its own strengths:</p><ul><li><strong>Matillion</strong>: Known for its scalability and ease of use, Matillion is designed for cloud database platforms like Snowflake.<br>- <strong>Talend</strong>: Offers a wide range of connectors and robust data transformation capabilities.<br>- <strong>Fivetran</strong>: Focuses on ease of use with a simple setup and maintenance-free operations.<br>- <strong>Informatica</strong>: A well-established player with powerful data integration capabilities and a comprehensive suite of tools.<br>- <strong>Azure Data Factory(ADF)</strong>: ADF is a fully managed, server less data integration solution for ingesting, preparing, and transforming all your data at scale.<br>- <strong>AWS Glue:</strong> AWS Glue is a server less data integration service that makes it easier to discover, prepare, move, and integrate data from multiple sources for analytics, machine learning (ML), and application development.</li></ul><p><a href="https://www.snowflake.com/trending/etl-tools/">https://www.snowflake.com/trending/etl-tools/</a></p><h3>Testing and Evaluation</h3><p>Once you’ve shortlisted potential ETL tools, it’s time to test them. Many vendors offer trial versions that you can use to evaluate how well the tool integrates with your environment and Snowflake. During this phase, pay close attention to the tool’s performance, ease of use, cost and the quality of the support provided.</p><p>Note:- Its not necessarily needed to go for ETL tools always, if you can work around with ELT and use snowflake inbuild feature like Snowpipe &amp; Copy commands with Task, this should give you everything in Snowflake itself. Thus at the end its about what fits your requirement with less cost and more efficiency.</p><h3>Conclusion</h3><p>Selecting the right ETL tool for migrating to Snowflake is a decision that will have a long-term impact on your data operations. By considering the factors outlined above and thoroughly testing your options, you can ensure that you choose a tool that aligns with your business objectives and maximizes the benefits of Snowflake.</p><p>Embarking on a cloud migration journey? Share your experiences or questions in comments, and let’s navigate the path to Snowflake together. Looking for more insights on cloud data platforms and ETL processes? Feel free to reach out on LinkedIn <a href="http://www.linkedin.com/in/amangupta-data"><strong><em>Aman Gupta</em></strong></a> or comment.</p><p>Let’s elevate our data strategies together!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d545d76a7148" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating the Cloud Migration from Oracle Exadata to Snowflake]]></title>
            <link>https://medium.com/@amangupta_data/navigating-the-cloud-migration-from-oracle-exadata-to-snowflake-388be55c96da?source=rss-5ad179c3e241------2</link>
            <guid isPermaLink="false">https://medium.com/p/388be55c96da</guid>
            <category><![CDATA[snowflake]]></category>
            <category><![CDATA[oracle]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-migration]]></category>
            <dc:creator><![CDATA[Aman Gupta]]></dc:creator>
            <pubDate>Thu, 17 Oct 2024 03:32:28 GMT</pubDate>
            <atom:updated>2024-10-17T04:40:39.001Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently I have implemented a Project to <strong><em>Migrate Legacy data from Oracle to Snowflake</em></strong>, writing the Learnings in this Article.</p><p>Note: This is a Generic Article with simple terms which everyone can understand. Also this might come up as an Important Interview Question for Data Engineers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/741/1*v0Kf6pSVoSLHJmgc170AMw.png" /></figure><h3><strong>Introduction</strong></h3><p>In the ever-evolving landscape of data management, cloud migration projects have become a strategic necessity for many organizations. Migrating from an on-premises solution like Oracle to a cloud-native platform like Snowflake can offer unparalleled scalability, flexibility, and cost savings. In this article, I will explain the key considerations and steps involved in a successful cloud data migration project from Oracle to Snowflake.</p><h3><strong>Understanding the Need for Migration</strong></h3><p>Before embarking on a migration journey, it’s essential to understand the ‘why’ behind the move whether its for your own Company or a Client.</p><p>Cloud Architecture (i.e. Snowflake in this case) offers a range of benefits over traditional on-premises databases, including:<br> →<strong><em>Scalability</em></strong>: Automatic scaling to handle varying workloads without the need for manual intervention.<br> →<strong><em>Maintenance</em></strong>: Reduced overhead for maintenance and infrastructure management.<br> →<strong><em>Performance</em></strong>: Enhanced query performance with Snowflake’s unique multi-cluster, shared data architecture.<br> →<strong><em>Cost</em></strong>: Potential cost savings due to Snowflake’s pay-as-you-go pricing model, uncoupled Storage and Compute Cost, Compressed Data Storage.</p><p>Advance Features, more Compatibility of Cloud tools and AI is adding to the fire of Migrations.</p><h3>Planning Your Migration</h3><p>A successful migration requires meticulous planning, Tech stack understanding and Patience. Here are the steps to consider:</p><p>1. Assessment and Inventory<br>Take stock of your current Oracle environment. Understand the current data models &amp; design, Number of Entities, Volume of Data, Code and dependencies (Hidden Entities or Codes are the Pain Points). This assessment will help you map out the migration process and identify potential challenges.</p><p>2. Choosing the Right Tools<br>Select the appropriate tools for data extraction, transformation, and loading (ETL). Snowflake partners with various ETL vendors and cloud providers, and choosing the right one can streamline the migration process.</p><p>3. Establishing Data Model &amp; Schema Conversion<br>Create Data Model &amp; Databases in Snowflake and Convert your Oracle schemas to Snowflake. This process may involve redefining data types and structures to fit Snowflake’s framework (Convert Oracle DDLs and Code i.e. SQLs, Procedures, functions to Snowflake).</p><p>4. Data Migration Strategy<br>Decide on a migration strategy that minimizes downtime and disruption. You may opt for a phased approach, moving data incrementally, or a full-scale migration (Historical Data at one go and then Incremental runs from new source), depending on your organization’s needs. Repointing of Downstream and Reporting to Snowflake should also be accounted for.</p><p>5. Data Quality<br>Before and after migration, cleanse your data to ensure accuracy and consistency. Also there should be checks to compare data between Oracle and Snowflake for counts and data validity. This step is crucial for maintaining data quality during and after the transition.</p><h3>Executing the Migration</h3><p>With a solid plan in place, you’re ready to execute the migration below are the suggested steps:</p><p>1. Data Transfer<br>Transfer your data from Oracle to Snowflake. This process can be done through various methods, including Snowflake’s native tools (Snowpipe, Copy into Command, Kafka Connector) or third-party solutions (Talend, Matillion, IICS).</p><p>2. Validation<br>After the transfer, validate the data to ensure completeness and accuracy. This step is critical to prevent data loss or corruption.</p><p>3. Optimization<br>Optimize your Snowflake environment for performance. This may involve setting up warehouses, clustering data, search optimization and tuning queries. Also keeping a check on costs is Important for any cloud migration. (Cloud comes with its own cost)</p><p>4. Testing<br>Conduct thorough testing to ensure that your applications and processes work as expected in the new environment. Have a validation for PII data add masking or encryption if needed.</p><p>5. Transition<br>Finally, transition your operations to Snowflake. This step may involve training your team, updating documentation, and establishing new workflows.</p><h3>Post-Migration Considerations</h3><p>After the migration, there are several post-migration tasks to address:</p><p>→<strong>Monitoring</strong>: Continuously monitor the Snowflake environment to ensure optimal performance and cost management.<br> →<strong>Security</strong>: Review and implement Snowflake’s security features to protect your data.<br> →<strong>Governance</strong>: Establish data governance policies to maintain data quality and compliance.</p><h3>Conclusion</h3><p>Migrating from Oracle to Snowflake can be a transformative move for organizations looking to leverage the power of the cloud. You can carefully plan and execute your migration project, by this you can unlock new levels of efficiency and innovation. Remember, the journey doesn’t end with the migration; it’s an ongoing process of optimization and adaptation to the dynamic cloud ecosystem.<br>Embark on your cloud migration journey with confidence, and harness the full potential of Snowflake to drive your organization forward.</p><p>If you’re planning a migration or looking for more insights into cloud data platforms, feel free to reach out to me on LinkedIn <a href="http://www.linkedin.com/in/amangupta-data"><strong><em>Aman Gupta</em></strong></a> or comment below. Let’s design our data strategies together!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=388be55c96da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Acing the SnowPro Advanced Architect Examination : A Guide with Preparation Strategy and Sample…]]></title>
            <link>https://medium.com/@amangupta_data/acing-the-snowpro-advanced-architect-examination-a-guide-with-preparation-strategy-and-sample-340b4a8f0791?source=rss-5ad179c3e241------2</link>
            <guid isPermaLink="false">https://medium.com/p/340b4a8f0791</guid>
            <category><![CDATA[snowflake]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[data-engineering]]></category>
            <dc:creator><![CDATA[Aman Gupta]]></dc:creator>
            <pubDate>Sun, 13 Oct 2024 10:30:21 GMT</pubDate>
            <atom:updated>2024-10-13T10:30:21.403Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Acing the SnowPro Advanced Architect Examination : A Guide with Preparation Strategy and Sample Questions</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/703/1*EqSzd9dR1xo5OHlq4NwsmA.png" /><figcaption>Badge</figcaption></figure><p>Recently I have cleared my SnowPro Advance Architect Examination, wanted to share the Journey, Preparation Strategy and Sample Questions with you all.</p><p><strong>About the Exam</strong><br>The SnowPro Advanced Architect certification is a prestigious recognition for professionals who demonstrate advanced knowledge and skills in designing and implementing Snowflake solutions. This certification validates your expertise in Snowflake’s architecture, data modeling, and security features, among other areas. In this article, I will provide you with insights and sample questions to help you prepare for the SnowPro Advanced Architect examination.</p><p><strong>Understanding the Exam Structure</strong><br>Before diving into the study material, it’s crucial to understand the format of the exam. The SnowPro Advanced Architect exam consists of multiple-choice and multiple-response questions it has 65 Question and 115 minute time limit. Minimum 75% is needed pass the exam.</p><p>You’ll be tested on various domains, including:<br>- Advanced Snowflake Architecture<br>- Data Modeling<br>- Data Sharing and Replication<br>- Data Import and Export<br>- Performance Tuning<br>- Security and Access Control<br>- Account and Resource Management</p><p>Weightage Split</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/981/1*rSgLp2OFDEsF_cyln5C5Aw.png" /><figcaption><a href="https://learn.snowflake.com/en/certifications/snowpro-advanced-architect/"><strong>Exam Topic Details</strong></a></figcaption></figure><p><strong>Study Tips</strong><br>1. Review the Snowflake Documentation: Snowflake’s official documentation is an invaluable resource. It provides detailed information on every aspect of the platform.</p><p><a href="https://docs.snowflake.com/">https://docs.snowflake.com/</a></p><p>2. Hands-On Practice: Set up a Snowflake account and practice creating databases, warehouses, and security roles. The more you practice, the more comfortable you’ll become with the platform.</p><p><a href="https://www.snowflake.com/en/resources/learn/snowflake-essentials-training/">https://www.snowflake.com/en/resources/learn/snowflake-essentials-training/</a></p><p>3. Join the Community: Engage with the Snowflake community. Forums and discussion groups can be great places to ask questions and share knowledge. LinkedIn can be used to get Insights from Posts of Snowflake Engineers and Data Super Heroes.</p><p><a href="https://community.snowflake.com/s/login/">https://community.snowflake.com/s/login/</a></p><p>4. Mock Exams: Take practice exams to familiarize yourself with the format and time constraints of the actual test. You can check Udemy Courses, Practice Tests or the exams available online, even snowflake official practice test helps, for which you need to register separately.</p><p><a href="https://learn.snowflake.com/en/certifications/snowpro-practice-exams/">https://learn.snowflake.com/en/certifications/snowpro-practice-exams/</a></p><p><strong>My Experience of the Exam</strong><br>Since I was SnowPro Certified, I was aware of most of the basic concepts. However, in our day-to-day tasks, we do not use all the features, hence a brush-up on the basics is needed. Allocate at least a week or two for the same. After that Refresh advanced topics and prepare for real-time scenario based questions from the projects or case studies.<br>Once you are clear with the basics and some part of advance topics, start taking practice tests or Udemy mocks. <br>The exam is of medium difficulty but is tricky and conceptual. Someone who is new to Snowflake will find it demanding to grasp the questions in one go. During the exam, be careful with time management. Since the questions are lengthy and the options are based on real-time scenarios, time ticks fast, so keep an eye on the clock too. When stuck, try to use the process of elimination, this helped me solve good number of the questions.<br>In multiple-choice questions, it’s given how many options we need to choose, thus further aiding in elimination. Logical thinking based on data warehouse (DWH) concepts also helped.</p><p>I saw few of the <strong><em>Topics</em></strong> which were not very much covered in mocks or Sample Questions, mentioning them below:<br>→<a href="https://docs.snowflake.com/en/user-guide/security-access-control-overview#enforcement-model-with-primary-role-and-secondary-roles">Primary and Secondary Roles</a><br>→<a href="https://docs.snowflake.com/en/user-guide/tables-hybrid">Hybrid Tables</a><br>→Function Alias. (Example: APPROX_TOP_K, MIN_BY, MAX_BY)<br>→<a href="https://docs.snowflake.com/en/developer-guide/sql-api/index">SnowSQL REST API</a><br>→<a href="https://docs.snowflake.com/en/user-guide/network-policies">Network Policies</a></p><p>To give you a taste of what to expect, here are some sample questions that reflect the style and content of the SnowPro Advanced Architect exam:</p><p>1. Advanced Snowflake Architecture:<br>Q: How does Snowflake’s multi-cluster warehouse feature enhance query performance?<br>A) It enables automatic scaling to handle concurrent workloads.<br>B) It allows for data to be replicated across multiple regions.<br>C) It provides dedicated storage for each compute node.<br>D) It encrypts data at rest and in transit.</p><p>2. Data Modeling:<br>Q: When designing a data model for time-series data in Snowflake, which table type is most efficient for handling frequent updates?<br>A) A transient table with clustering keys.<br>B) A standard table with a primary key.<br>C) A temporary table with a secondary index.<br>D) An external table with partitioning.</p><p>3. Data Import and Export:<br>Q: Which Snowflake feature allows for the continuous, automated loading of data from files in a cloud storage service?<br>A) SnowPipe<br>B) Copy into<br>C) Streams and Tasks<br>D) Bulk data loading</p><p>4. Performance Tuning:<br>Q: What is the best practice for optimizing the performance of large joins in Snowflake?<br>A) Use the FLATTEN function to preprocess the data.<br>B) Apply clustering keys to co-locate related data.<br>C) Increase the size of the virtual warehouse.<br>D) Use materialized views to pre-aggregate the data.</p><p>5. Security and Access Control:<br>Q: Which of the following is NOT a valid method for securing data in Snowflake?<br>A) Row access policies<br>B) Network policies<br>C) Data masking policies<br>D) Tagging</p><p>6. Account and Resource Management:<br>Q: What is the primary purpose of the RESOURCE MONITOR in Snowflake?<br>A) To monitor the performance of queries.<br>B) To manage the storage and compute costs.<br>C) To track user login activity.<br>D) To enforce data retention policies.</p><p><strong>Conclusion</strong><br>Preparing for the SnowPro Advanced Architect exam requires a blend of theoretical knowledge and practical experience. By studying the topics outlined above, reading Snowflake Documents &amp; engaging with the Snowflake community, and practicing with sample questions, you’ll be well on your way to achieving this advanced certification. Remember, the key to success is understanding the intricacies of Snowflake’s architecture and features, so make sure to allocate ample time for hands-on practice.</p><p>Good Luck on your journey to becoming a SnowPro Advanced Architect!</p><p>In case of Question Please reach out to me on LinkedIn <a href="http://www.linkedin.com/in/amangupta-data"><strong><em>Aman Gupta</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=340b4a8f0791" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>