Blog

<h2>How Column-Level Masking in Snowflake Works&nbsp;</h2><h3><br>What It Is</h3><p>Column-level masking in Snowflake helps us hide sensitive data from users who don’t need to see it. Instead of blocking entire tables, we can apply masking policies to specific columns—like email addresses or salaries—based on roles.</p><h3>Why We Use It</h3><ul><li>Controls access to specific columns, not entire datasets.</li><li>Helps us meet privacy requirements without duplicating tables.</li><li>Keeps sensitive data protected across environments like dev, QA, and prod.</li></ul><h3>How It Works</h3><p>Here’s how Snowflake handles column masking:</p><ul><li>We define a masking policy using SQL.</li><li>This policy acts like a filter—checking the user’s role and deciding what they can see.</li><li>We attach this policy to one or more columns.</li><li>When someone queries the column, Snowflake shows either the real value or a masked version.<br></li></ul><figure id="figure-z0jm7yp6rjm9lq24m8"><img id="z0jm7yp6rjm9lq24m8" src="https://cdn.durable.co/blocks/14VKOA1ciohWGDLnTTLoWJEhNOr4puPDs2SdZUWXVOekUzt3hIeTUaVsIsAthLqF.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/14VKOA1ciohWGDLnTTLoWJEhNOr4puPDs2SdZUWXVOekUzt3hIeTUaVsIsAthLqF.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><h3>Step-by-Step: Creating a Masking Policy</h3><p>Let’s walk through a basic example where we want only HR users to see employee email addresses.</p><p><strong>1. Create the Masking Policy</strong></p><p>We define a policy using SQL. It checks the user’s role. If the role is HR_ROLE, show the real email. Otherwise, show a generic masked value.</p><figure id="figure-2lw2lwmdcvm9lq66j8"><img id="2lw2lwmdcvm9lq66j8" src="https://cdn.durable.co/blocks/7jEMpdYrflOdwvpIPB48ff6Oc5MUgT3LzSEzSGoY8u9cQpCVzWzCNIp96ZpRvwcT.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/7jEMpdYrflOdwvpIPB48ff6Oc5MUgT3LzSEzSGoY8u9cQpCVzWzCNIp96ZpRvwcT.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><p><strong>2. Apply the Policy to a Column</strong></p><p>We attach this policy to the email column in the employees table.</p><figure id="figure-duyejk6kwm9lq727q"><img id="duyejk6kwm9lq727q" src="https://cdn.durable.co/blocks/34sTcgqXK9jupXQTBBgmliMr1T9SODf8SY9nzuokicT4AmMwyXRRNnAccw7Jhv1Z.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/34sTcgqXK9jupXQTBBgmliMr1T9SODf8SY9nzuokicT4AmMwyXRRNnAccw7Jhv1Z.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><p>Now, any time someone queries that column, Snowflake checks their role and applies the policy.</p><figure id="figure-nnpqr7kwgm9lqcpqe"><img id="nnpqr7kwgm9lqcpqe" src="https://cdn.durable.co/blocks/10FYTKdykZT1EpiNmKFRQItxcxIbeI7affLSnaWCJMXSrMnR8HwMfE8E4kcLPlhz.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: 45% 45%;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="45%" data-positiony="45%" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/10FYTKdykZT1EpiNmKFRQItxcxIbeI7affLSnaWCJMXSrMnR8HwMfE8E4kcLPlhz.png" data-mce-style="aspect-ratio: 16/9; object-position: 45% 45%;"></figure><h3>Reusing the Policy Across Tables</h3><p>Snowflake lets us reuse the same policy on similar columns in other tables. For example, we can apply the same email_mask_policy to an email column in a contractors table without writing new logic.</p><p>This helps us maintain consistency and reduce duplication.</p><h3>Masking Numeric Data</h3><p>We can also mask numeric values like salaries or bonuses.</p><p>For example:</p><ul><li>Finance roles see the actual number.</li><li>Other roles see NULL or 0.</li></ul><p>To do this, we follow the same steps:</p><ul><li>Create a policy that checks the user’s role.</li><li>If not authorized, return a placeholder (like NULL).</li><li>Apply the policy to the numeric column.</li></ul><p>This is useful for sharing performance data while keeping compensation private.</p><h3>Tracking Where Masking is Applied</h3><p>To keep track of which columns have masking policies, we can use Snowflake's information_schema.columns view.</p><p>This allows us to:</p><ul><li>Audit which columns are protected.</li><li>Check if policies are applied consistently.</li><li>Identify columns missing masking rules.</li></ul><h3>Best Practices for Column Masking</h3><ul><li><strong>Use clear naming</strong> for policies (<em>email_mask_policy, salary_mask_policy</em>) to make them easier to manage.</li><li><strong>Keep logic simple :</strong> avoid overcomplicating the policy with too many conditions.</li><li><strong>Document the purpose</strong> of each policy in a central table or within your team’s governance process.</li><li><strong>Test across environments </strong>especially in dev or staging—to make sure masking works consistently.</li></ul><h3>Real-Life Example: Customer Support Access</h3><p>Let’s say our support team needs to see basic customer info but not payment details or phone numbers.</p><ul><li>We attach a masking policy to <em>credit_card_number</em> and <em>phone_number</em>.</li><li>The policy allows access only for roles like <em>PAYMENTS_TEAM</em> or <em>SECURITY_TEAM.</em></li><li>All other users just see "<em>masked</em>" or a generic value.</li></ul><figure id="figure-g7cdwmaggm9lqkx9q"><img id="g7cdwmaggm9lqkx9q" src="https://cdn.durable.co/blocks/25UMiRIaNu17pkAyMRCC8pYdlu2aQfga0eZ9N2zHaRyvtofRTT0wneTme8UhO0mw.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: 50% 50%;" data-corners="default" data-aspect="16:9" data-caption="" data-positionX="50%" data-positionY="50%" data-fullWidth="false"/></figure><p>This setup protects sensitive data while still supporting team collaboration.</p><h3>Common Limitations</h3><p>While column masking is powerful, there are a few things to watch for:</p><ul><li><strong>One input column only:</strong> Policies can only use the value of the column they’re attached to.</li><li><strong>Only SELECT queries are affected:</strong> Other operations like INSERT or COPY aren’t masked.</li><li><strong>Not meant for full security:</strong> Masking helps with access control but doesn’t encrypt or fully hide data from backend processes.</li></ul><h3>Summary</h3><p>Column-level masking in Snowflake is a practical way to protect specific fields without blocking access to the entire dataset. It’s flexible, role-based, and easy to maintain at scale.</p><table border="1" data-mce-style="border-collapse: collapse; width: 100%; margin-left: auto; margin-right: auto;" style="border-collapse: collapse; width: 100%; margin-left: auto; margin-right: auto;" data-mce-selected="1"><tbody><tr><td style="width: 50%;" data-mce-style="width: 50%;"><strong>Feature</strong></td><td style="width: 50%;" data-mce-style="width: 50%;"><strong>Benefit&nbsp;</strong></td></tr><tr><td style="width: 50%;" data-mce-style="width: 50%;">Column Level masking</td><td style="width: 50%;" data-mce-style="width: 50%;"><p>Controls access to specific data fields</p></td></tr><tr><td style="width: 50%;" data-mce-style="width: 50%;">Role based policies&nbsp;</td><td style="width: 50%;" data-mce-style="width: 50%;">Show real or masked values depending on who's querying&nbsp;</td></tr><tr><td style="width: 50%;" data-mce-style="width: 50%;">Reusable Logic&nbsp;</td><td style="width: 50%;" data-mce-style="width: 50%;"><p>Apply the same masking rules across multiple tables&nbsp;</p></td></tr><tr><td style="width: 50%;" data-mce-style="width: 50%;">No data duplication</td><td style="width: 50%;" data-mce-style="width: 50%;">Keep one source of truth while customising access&nbsp;</td></tr><tr><td style="width: 50%;" data-mce-style="width: 50%;">Works across environments&nbsp;</td><td style="width: 50%;" data-mce-style="width: 50%;">Consistent protection from development to production</td></tr></tbody></table><p>If we’re sharing data across teams or environments, column-level masking is a helpful tool for minimising risk. It keeps access focused, simple, and transparent—without slowing down collaboration.</p>

Column-level masking in Snowflake

<h2>Understanding How Sigma Uses Snowflake’s Compute Layer</h2><p>Sigma Computing connects directly to Snowflake, allowing teams to explore and analyze data at scale without moving it. But to really get value out of this integration, we need to understand how Sigma uses Snowflake’s compute layer.</p><p>This blog explains what’s happening under the hood, how compute usage is triggered, and how we can optimise our workflows for speed and cost.</p><h3>What is Snowflake’s Compute Layer?</h3><ul><li>Snowflake separates storage and compute.</li><li>Compute is handled by virtual warehouses, which run the SQL queries.</li><li>Each virtual warehouse consumes credits when running.</li></ul><p><strong>Example: </strong>When we run a SELECT query from Sigma, it triggers a virtual warehouse in Snowflake to perform the operation. We pay based on:</p><ul><li>Size of the warehouse (e.g., Small, Medium, Large)</li><li>Duration it runs<br>&nbsp;<h3>What Triggers Compute in Sigma?</h3><span style="font-family: inherit; font-size: 18px; font-weight: inherit;" data-mce-style="font-family: inherit; font-size: 18px; font-weight: inherit;">Sigma never stores our data. Instead, it translates actions into SQL queries that Snowflake runs.</span></li></ul><p><strong>Common actions that trigger compute:</strong></p><ul><li>Opening a workbook or dashboard</li><li>Applying filters or parameters</li><li>Creating new calculated columns</li><li>Previewing a dataset</li></ul><p><strong>Example:</strong></p><figure id="figure-j714rgl9dcm98q9gsn"><img id="j714rgl9dcm98q9gsn" src="https://cdn.durable.co/blocks/2altuVtyVvDwtL22PTREI273jISL0Rmc9ZjBkfzzOT1YAmGJgAEWFLXih1RII2ZW.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/2altuVtyVvDwtL22PTREI273jISL0Rmc9ZjBkfzzOT1YAmGJgAEWFLXih1RII2ZW.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><p><em>When a user selects "2024" from a filter, Sigma dynamically builds and sends this SQL to Snowflake.</em></p><h3>Live Queries vs Cached Results</h3><p>Sigma provides live analytics by default, but it also uses caching to reduce unnecessary compute.</p><p><strong>How caching works:</strong></p><ul><li>Sigma caches the result of recent queries.</li><li>If the same query is run within a short period, Sigma returns cached results.</li><li>Changing filters, fields, or datasets invalidates the cache.<br></li></ul><figure id="figure-328iq77g6om98qcq3i"><img id="328iq77g6om98qcq3i" src="https://cdn.durable.co/blocks/fkrXPydg43juLsgARdpmDhYU662aQKXfwEnLiZWK8vzME2toYwLBcV64NqtYrDJ8.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/fkrXPydg43juLsgARdpmDhYU662aQKXfwEnLiZWK8vzME2toYwLBcV64NqtYrDJ8.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><h3>How to Control Snowflake Spend in Sigma</h3><p>Here are some ways we can reduce costs and speed up performance:</p><ol><li><strong>Set Query Timeout and Limits</strong><ul data-mce-style="list-style-type: square;" style="list-style-type: square;"><li>Sigma lets us limit query run time and row count.</li><li>Helps avoid large accidental queries.</li></ul></li><li><strong>Choose Appropriate Warehouse Sizes</strong><ul data-mce-style="list-style-type: square;" style="list-style-type: square;"><li>Use Small or Medium warehouses for most Sigma work.</li><li>Avoid auto-scaling unless needed.</li></ul></li><li><strong>Use Input Controls to Scope Data</strong><ul data-mce-style="list-style-type: square;" style="list-style-type: square;"><li>Drop-down filters or date pickers reduce the size of result sets.</li></ul></li><li><strong>Use Sigma Datasets for Reuse</strong><ul style="list-style-type: square;" data-mce-style="list-style-type: square;"><li>Build reusable datasets that predefine logic.</li><li>Reduces repeated computation.<br></li></ul></li></ol><figure id="figure-uym6e6zu8nm98qpwt0"><img id="uym6e6zu8nm98qpwt0" src="https://cdn.durable.co/blocks/26dlMyNFfv8AwTH9P68oOpXa8XxHNwNi281z3MLuzWhSaEUnwqXd2tMQFj6xVCQM.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/26dlMyNFfv8AwTH9P68oOpXa8XxHNwNi281z3MLuzWhSaEUnwqXd2tMQFj6xVCQM.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><h3>Real-World Example: Monthly Sales Dashboard</h3><p>We built a dashboard that shows monthly sales by region, category, and salesperson.</p><p><strong>What happens behind the scenes:</strong></p><ul><li>Sigma sends a SQL query to Snowflake with filters from the user.</li><li>Snowflake computes the results and returns them to Sigma.</li><li>Sigma displays the results in tables and charts.<br data-mce-bogus="1"></li></ul><figure id="figure-erhujrcfdsm98qss4d"><img id="erhujrcfdsm98qss4d" src="https://cdn.durable.co/blocks/15RRbF1pb8UC1Z7NFJTLDmGVdOGKkQlqS2vQEKDwipWiJBRH6gegl0gIS6XRCGZE.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionX="undefined" data-positionY="undefined" data-fullWidth="false"/></figure><p><strong>Note:</strong> If the same dashboard is opened again within a few minutes without changes, Sigma uses cached results.</p><h3>What Doesn’t Trigger Compute?</h3><p>Sigma actions that don’t hit Snowflake include:</p><ul><li>Changing visualisation types (e.g., bar to line chart)</li><li>Rearranging columns in a table</li><li>Sorting by a field already present in the result set</li></ul><p>This helps us avoid wasting compute on non-SQL changes.</p><h3>Monitoring Usage in Snowflake</h3><p>We can monitor Sigma’s compute usage directly in Snowflake:</p><ul><li>Use the <strong>QUERY_HISTORY</strong> view</li><li>Filter by user, warehouse, time period</li></ul><p><strong>Example:</strong></p><figure id="figure-wvs84kfczcm98qj7or"><img id="wvs84kfczcm98qj7or" src="https://cdn.durable.co/blocks/16Fhx07B1vyuLgxvxb9b3J3i2r3ozGr0AzCjuyrQzhQyfDHPoUZO4WXSubkjs60Y.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/16Fhx07B1vyuLgxvxb9b3J3i2r3ozGr0AzCjuyrQzhQyfDHPoUZO4WXSubkjs60Y.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><p>This helps us identify expensive queries and tune them.</p><h3>Summary:</h3><ul><li>Sigma relies on Snowflake for all compute operations.</li><li>Every action in Sigma can potentially trigger a SQL query.</li><li>Caching helps reduce repeated queries, but live analytics means compute is often active.</li><li>We can control costs by limiting query size, using filters, and monitoring queries in Snowflake.</li></ul><p>By understanding the connection between Sigma and Snowflake’s compute layer, we can build faster dashboards and keep our cloud bill under control.</p><p><br></p><p><br></p>

Understanding how Sigma uses Snowflake’s compute layer

<h2>Managing Big Data with Sigma: How to Handle Complex Data Sets<br></h2><p>Big data presents both opportunities and challenges. As organizations collect massive amounts of information, they need tools that simplify analysis without requiring deep technical expertise. Sigma Computing provides a way to explore, visualize, and work with complex data sets directly in the cloud—without SQL or coding experience.</p><h3>Why Big Data Feels Overwhelming</h3><p>Organizations today deal with data from multiple sources:</p><ul><li>Customer interactions</li><li>Transaction records</li><li>IoT sensor readings</li><li>Web traffic logs</li><li>Social media insights</li></ul><p>Each data source generates information in different formats, at high volumes, and often with inconsistencies. Managing this complexity requires:</p><ul><li><strong>Fast access</strong> to large data sets</li><li><strong>Real-time collaboration</strong> across teams</li><li><strong>Scalability</strong> to process millions or billions of rows</li><li><strong>Integration</strong> with cloud data warehouses like Snowflake, BigQuery, and Redshift<br></li></ul><figure id="figure-xfzvrjlm9rm8xzq335"><img id="xfzvrjlm9rm8xzq335" src="https://cdn.durable.co/blocks/8bBqWW77l264xU3eA9NuJfOtKs4Faw6W5DU4kBvRhTLaoX2k9Fuv2pdhmHA7Wfm1.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/8bBqWW77l264xU3eA9NuJfOtKs4Faw6W5DU4kBvRhTLaoX2k9Fuv2pdhmHA7Wfm1.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><h3>How Sigma Helps Manage Big Data</h3><p>Sigma is built for cloud data analytics, making it easier to work with large data sets directly from your cloud warehouse and features like <strong>Data Apps</strong>, <strong>AI-powered analytics</strong>, <strong>enhanced data modeling, and expanded connectivity</strong> further improve its capabilities.</p><p><strong>1. Work with Live Data (No Extracts)</strong></p><ul><li>Unlike traditional BI tools that require data extracts, Sigma connects directly to live data. This means:<ul><li>No delays caused by scheduled refreshes</li><li>No outdated reports based on stale data</li><li>Always working with the most current information</li></ul></li><li><strong>Example:</strong> If our business is tracking daily sales, we can build reports that update in real time as new transactions occur.</li></ul><p><strong>2. Explore Billions of Rows Without Writing SQL</strong></p><ul><li>Sigma’s spreadsheet-like interface makes it easy to analyze data without writing SQL queries. Users can:<ul><li>Drag and drop columns</li><li>Apply filters and aggregations</li><li>Build calculations using familiar spreadsheet functions</li></ul></li><li>Use <strong>Formula Assistant</strong>, Sigma’s AI-powered tool, to help create complex calculations efficiently</li><li><strong>Example</strong>: A marketing team can analyze customer behavior by segmenting data without needing help from a data engineer.</li></ul><p><strong>3. Handle Nested and Semi-Structured Data</strong></p><ul><li>Many cloud warehouses store data in semi-structured formats like JSON. Sigma allows users to:<ul><li>Extract JSON fields into separate columns</li><li>Explore nested fields through the user interface</li><li>Join structured and semi-structured data using table relationships</li></ul></li><li>However, JSON data is not automatically flattened; users must manually extract relevant fields when needed.</li></ul><p><strong>4. Optimize Performance by Pushing Queries to the Warehouse</strong></p><ul><li>Analyzing raw big data can be slow. Sigma optimizes performance by:<ul><li>Pushing calculations directly to the cloud data warehouse</li><li>Minimizing data movement by executing queries at the source</li><li>Allowing drill-downs from summaries to details without performance loss</li><li>Using predefined metrics and reusable tables to standardize calculations and improve governance</li></ul></li></ul><p><strong>Note:</strong> Sigma does not automatically create aggregated tables but allows users to manually build summaries for efficient querying.</p><figure id="figure-2zo7secda9m8xzqt4g"><img id="2zo7secda9m8xzqt4g" src="https://cdn.durable.co/blocks/27pOeKdGkJ0AT1a0IsrLwfAknIUBpLgbaWVXj3vPZEKHmyLYmwROEr0NHI6ZsTR5.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/27pOeKdGkJ0AT1a0IsrLwfAknIUBpLgbaWVXj3vPZEKHmyLYmwROEr0NHI6ZsTR5.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><p><strong>5. Build Interactive Data Apps</strong></p><ul><li>Sigma offers Data Apps, which allow users to:<ul><li>Create interactive, no-code analytics applications</li><li>Guide decision-making through customized workflows</li><li>Go beyond static dashboards for a more dynamic experience</li></ul></li><li><strong>Example:</strong> A finance team can build an interactive budgeting tool that updates forecasts based on real-time inputs.</li></ul><p><strong>6. Expanded Connectivity and Embedded Analytics</strong></p><ul><li>Sigma has expanded its integrations, including:<ul><li>OAuth with write access for Snowflake and Databricks</li><li>Azure SQL Database connector for smoother Microsoft integration</li><li>Improved embedded analytics, offering:<ul><li>More customization for reports</li><li>Interactive exploration for embedded users</li><li>A more intuitive user interface</li></ul></li></ul></li></ul><h3>Real-World Use Cases</h3><p><strong>Retail: Inventory and Sales Forecasting</strong></p><ul><li>Retailers must balance stock levels to avoid overstocking or shortages. With Sigma, they can:<ul><li>Analyze historical sales trends</li><li>Predict demand based on seasonality</li><li>Adjust orders dynamically based on real-time inventory</li></ul></li></ul><p><strong>Healthcare: Patient Data Analysis</strong></p><ul><li>Healthcare organizations deal with massive amounts of patient data across different systems. Sigma helps by:<ul><li>Unifying patient records from various sources</li><li>Identifying trends in treatment outcomes</li><li>Ensuring compliance with data security regulations</li></ul></li></ul><p><strong>Financial Services: Fraud Detection</strong></p><ul><li>Banks and fintech companies need to detect fraudulent transactions in real time. Sigma enables them to:<ul><li>Analyze transaction patterns for anomalies</li><li>Cross-check data across multiple sources</li><li>Flag suspicious activity instantly</li></ul></li></ul><h3>Best Practices for Managing Big Data in Sigma</h3><ol><li><strong>Use Filters to Reduce Query Load</strong><ul style="list-style-type: square;" data-mce-style="list-style-type: square;"><li>Limit the data displayed to focus on relevant records</li><li>Use date ranges and category filters to speed up analysis</li></ul></li><li><strong>Build Aggregated Views for High-Level Analysis</strong><ul style="list-style-type: square;" data-mce-style="list-style-type: square;"><li>Summarize data at the appropriate level (e.g., daily, weekly, monthly)</li><li>Drill down only when needed to preserve performance</li></ul></li><li><strong>Use Sigma’s Built-in Spreadsheet Functions</strong><ul data-mce-style="list-style-type: square;" style="list-style-type: square;"><li>Utilize familiar spreadsheet-like calculations for quick analysis</li><li>Apply functions such as moving averages or percentile rankings</li></ul></li><li><strong>Ensure Data Governance and Access Control</strong><ul data-mce-style="list-style-type: square;" style="list-style-type: square;"><li>Use role-based permissions to restrict sensitive data</li><li>Share reports with appropriate stakeholders without exporting raw data</li></ul></li><li><strong>Integrate Sigma with Other Business Tools</strong><ul data-mce-style="list-style-type: square;" style="list-style-type: square;"><li>Connect dashboards with Slack, Google Sheets, or CRM platforms</li><li>Automate workflows using Sigma’s API</li></ul></li></ol><h3>Conclusion</h3><p>Managing big data doesn’t have to be complicated. Sigma provides a cloud-native solution that simplifies exploration, visualization, and collaboration.</p><p>With advancements like Data Apps, AI-powered tools, improved data modeling, and expanded connectivity, Sigma continues to enhance how teams analyze complex data sets. Whether we’re analyzing millions of customer transactions, tracking business performance, or detecting fraud, Sigma makes big data analysis more interactive and accessible.</p><p>If your team is struggling with large-scale data analysis, Sigma might be the missing piece to make insights faster and easier.</p><p><br></p>

Managing Big Data with Sigma Comutng

<h2>What Are Data Apps in Sigma Computing?</h2><p>Sigma Computing enables teams to create interactive, no-code data applications (data apps) directly within the platform. These apps allow business users to explore, filter, and interact with data without requiring SQL expertise.</p><h3>Key Features:</h3><ul><li><strong>No-Code Interface:</strong> Build apps with drag-and-drop elements.</li><li><strong>Live Data Interaction:</strong> Query data in real-time without exporting.</li><li><strong>Custom UI Components:</strong> Use buttons, dropdowns, and filters for better experience.</li><li><strong>Security &amp; Access Control:</strong> Share insights securely with role-based permissions</li></ul><figure id="figure-npwui14jspm8nehfuz"><img id="npwui14jspm8nehfuz" src="https://cdn.durable.co/blocks/339852awCdJCddZW5gyMEZiwx8u23t0SLiJE1Y8aTu7fsJQhQEDgbnXDMpf3qrsW.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: undefined undefined;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/339852awCdJCddZW5gyMEZiwx8u23t0SLiJE1Y8aTu7fsJQhQEDgbnXDMpf3qrsW.png" data-mce-style="aspect-ratio: 16/9; object-position: undefined undefined;"></figure><h3>How to Build a Data App&nbsp;</h3><p>Creating a data app involves structuring data, defining user interactions, and enabling real-time updates. Here’s a step-by-step guide:</p><ul><li><strong>Step 1: Define the Purpose</strong><ul><li>Identify the business problem the app will solve.</li><li>Determine key metrics and data sources.</li></ul></li><li><strong>Step 2: Prepare Your Data</strong><ul><li>Connect to data sources (Snowflake, Google BigQuery, etc.).</li><li>Clean and structure data for easy access.</li></ul></li><li><strong>Step 3: Design the User Interface</strong><ul><li>Use Input Tables for user-driven data filtering.</li><li>Add Dropdowns and Buttons for interactivity.</li><li>Configure Conditional Formatting for highlighting insights.</li></ul></li><li><strong>Step 4: Add Real-Time Interactivity</strong><ul><li>Use Sigma’s parameter feature to dynamically update charts and tables.</li><li>Set up Drilldowns to allow users to explore granular details.</li></ul></li><li><strong>Step 5: Publish and Share</strong><ul><li>Set permissions for different user roles.</li><li>Embed the app within dashboards or external platforms.</li></ul></li></ul><figure id="figure-i0eh2urq7om8nfni5d"><img id="i0eh2urq7om8nfni5d" src="https://cdn.durable.co/blocks/21yMMIDmeaR77GxYIl7LyqMkucd8B4dvAeareWdXAtw2fR8K2QVB8SJ4nE0WS4Uh.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl selected" style="aspect-ratio: 16/9; object-position: undefined undefined;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/21yMMIDmeaR77GxYIl7LyqMkucd8B4dvAeareWdXAtw2fR8K2QVB8SJ4nE0WS4Uh.png" data-mce-style="aspect-ratio: 16/9; object-position: undefined undefined;" data-mce-selected="1"></figure><h3>Interactive Features That Make Data Apps Powerful</h3><ul><li><strong>Parameterized Filters</strong><ul><li>Let users adjust filters dynamically without modifying queries.</li><li><strong>Example:</strong> A dropdown to select different product categories and update sales reports instantly.</li></ul></li><li><strong>Dynamic Calculations</strong><ul><li>Users can modify input values, triggering real-time calculations.</li><li><strong>Example:</strong> A sales projection tool where users enter expected growth rates to update charts.</li></ul></li><li><strong>Drill-Through Capabilities</strong><ul><li>Click on data points to explore detailed records.</li><li><strong>Example:</strong> Clicking on a country in a global sales map to view regional breakdowns.</li></ul></li><li><strong>Embedded Workflows</strong><ul><li>Integrate apps into other platforms like Slack or web portals.</li><li><strong>Example:</strong> A finance app that pulls live revenue data into executive dashboards</li></ul></li></ul><h3>Real-World Use Cases&nbsp;</h3><ol><li><strong>Sales Performance Dashboard</strong><ul><li>Track regional and product-wise sales with interactive selectors.</li><li>Users filter by timeframe, product category, and sales team.</li></ul></li><li><strong>Financial Forecasting Tool</strong><ul><li>Allows finance teams to simulate revenue scenarios.</li><li>Users input expected costs and revenue trends to update forecasts.</li></ul></li><li><strong>Customer Support Insights</strong><ul><li>Displays real-time customer feedback and support ticket trends.</li><li>Users filter by sentiment, agent, and response time.</li></ul></li><li><strong>Inventory Management System</strong><ul><li>Helps supply chain teams track stock levels and predict shortages.</li><li>Users select warehouse locations to view inventory data.</li></ul></li></ol><h3>Importance</h3><p>Data apps bridge the gap between data teams and business users. They make insights actionable without requiring advanced analytics skills. By using interactive components, organizations can ensure that data is not just stored but actively used for better decision-making.</p><figure id="figure-fvowhow6esm8nfomaj"><img id="fvowhow6esm8nfomaj" src="https://cdn.durable.co/blocks/18nvEB8S2CI3z2ixgwSy74UVnDpQiW3heg7cvA9WVou6xp2LMgYznShEbTRa25dx.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/18nvEB8S2CI3z2ixgwSy74UVnDpQiW3heg7cvA9WVou6xp2LMgYznShEbTRa25dx.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><h3>Conclusion</h3><p>Building data apps in Sigma Computing transforms raw data into interactive experiences. With minimal effort, teams can create powerful applications that drive meaningful insights.</p><p>Want to see Sigma data apps in action? Start experimenting today with interactive dashboards that fit your business needs!</p><p><br></p><p><br><br><br></p>

Data Apps in Sigma Computing

<h2>Mastering Input Tables in Sigma Computing</h2><p>Data analysis often requires flexibility—whether it’s adding assumptions for forecasting, adjusting data for scenario modeling, or simply incorporating new information manually. Sigma Computing’s Input Tables provides an intuitive way to input and modify data directly in a cloud-based environment, making data analysis more interactive and dynamic.</p><h3>What Are Input Tables?</h3><p>Input Tables in Sigma allow users to manually enter data directly into their workbooks. Unlike standard tables that only display pre-existing data, Input Tables let users modify and enhance their datasets dynamically.</p><p><strong>They are particularly useful for:</strong></p><ul><li><strong>Scenario Modeling:</strong> Enter different variables and analyze outcomes.</li><li><strong>Manual Adjustments:</strong> Fix data inconsistencies without modifying source data.</li><li><strong>Collaborative Planning:</strong> Teams can input estimates, assumptions, or project plans.</li></ul><p>This feature enables the integration of new data points and the augmentation of existing datasets from sources like Snowflake or Databricks, facilitating rapid prototyping, advanced modeling, forecasting, and what-if analyses—all without altering the original source data.</p><h3>Types of Input Tables</h3><p>Sigma offers two primary types of Input Tables:</p><ul><li><strong>Empty Input Tables:</strong> These are blank tables where users can manually add data. They are ideal for scenarios where you need to input data that doesn't already exist in your data warehouse.</li><li><strong>Linked Input Tables:</strong> These tables are derived from existing data elements within your workbook. They allow you to link new data entries to existing datasets, facilitating more complex analyses and data relationships.</li></ul><figure id="figure-y182mjofzm8e4iw86"><img id="y182mjofzm8e4iw86" src="https://cdn.durable.co/blocks/bBBiXdmUJVBxwI3ECHgGR10f25Q7YTAkqnYZrEZnimYhcG4I3iBHIKnGVwRpigZr.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/bBBiXdmUJVBxwI3ECHgGR10f25Q7YTAkqnYZrEZnimYhcG4I3iBHIKnGVwRpigZr.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><h3>Creating an Input Table</h3><p>To create an Input Table in Sigma, follow these steps:</p><ul><li><strong>Enter Edit Mode:</strong> Open your workbook and switch to edit mode.</li><li><strong>Access the Add New Panel:</strong> Navigate to the 'Add New' panel within the workbook.</li><li><strong>Select Input Table Type:</strong>For an empty table, choose 'Empty' under the Input Tables section.</li></ul><p>For a linked table, select 'Linked' and choose the source element you wish to link to.</p><ul><li><strong>Define Table Structure:</strong> Add columns and specify data types as needed.</li><li><strong>Input Data:</strong> Manually enter your data into the table cells.<br></li></ul><figure id="figure-allssw1qpam8e4qxfc"><img id="allssw1qpam8e4qxfc" src="https://cdn.durable.co/blocks/14wI310BuiUQ4hyIosdvthpbEfpPRJVBzTuuvhQOS7Fk25dlCn5wcgGd4hfKF0O4.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionX="undefined" data-positionY="undefined" data-fullWidth="false"/></figure><h3>Benefits of Using Input Tables</h3><ul><li><strong>Dynamic &amp; Interactive</strong><ul><li>Unlike traditional static reports, Input Tables allow real-time modifications without altering the underlying data source.</li></ul></li><li><strong>Enhanced Collaboration</strong><ul><li>Multiple users can simultaneously enter, adjust, and analyze data without spreadsheet chaos.</li></ul></li><li><strong>Scenario Modeling</strong><ul><li>Quickly adjust variables and assumptions to see their impact on calculations.</li></ul></li></ul><h3>Use Cases for Input Tables:</h3><ul><li><strong>Data Entry:</strong> Input Tables enable users to manually input data that may not be available in existing datasets, allowing for the incorporation of external information into analyses.</li><li><strong>Data Augmentation:</strong> Users can add supplementary data to existing datasets, enriching analyses with additional context or variables.</li><li><strong>Scenario Modeling and What-If Analysis:</strong> Input Tables facilitate the creation of hypothetical scenarios by allowing users to adjust variables and observe potential outcomes without modifying the original data.<br></li></ul><table style="border-collapse: collapse; width: 100%;" border="1" data-mce-style="border-collapse: collapse; width: 100%;"><tbody><tr><td style="width: 38.3333%;" data-mce-style="width: 38.3333%;"><strong>USE CASE</strong></td><td style="width: 61.6667%;" data-mce-style="width: 61.6667%;"><strong>HOW INPUT TABLES HELP</strong></td></tr><tr><td style="width: 38.3333%;" data-mce-style="width: 38.3333%;"><strong>Budget Planning&nbsp;</strong></td><td style="width: 61.6667%;" data-mce-style="width: 61.6667%;">Enter budget estimates and compare them with actuals</td></tr><tr><td style="width: 38.3333%;" data-mce-style="width: 38.3333%;"><strong>Risk Assessment</strong></td><td style="width: 61.6667%;" data-mce-style="width: 61.6667%;">Manually input risk factors and model their impact</td></tr><tr><td style="width: 38.3333%;" data-mce-style="width: 38.3333%;"><strong>HR &amp; Payroll</strong></td><td style="width: 61.6667%;" data-mce-style="width: 61.6667%;">Add employee salary adjustments for financial forecasting&nbsp;</td></tr><tr><td style="width: 38.3333%;" data-mce-style="width: 38.3333%;"><strong>Operational Planning&nbsp;</strong></td><td style="width: 61.6667%;" data-mce-style="width: 61.6667%;">Track equipment maintenance costs and schedules</td></tr></tbody></table><h3>Best Practices for Using Input Tables</h3><ul><li><strong>Use Linked Input Tables Wisely:</strong> When modifying existing datasets, always ensure data integrity.</li><li><strong>Keep Input Table Data Clean:</strong> Avoid unnecessary data entry to prevent clutter.</li><li><strong>Utilize Sigma’s Functions:</strong> Combine Input Tables with Sigma's built-in calculations and aggregations for more robust analysis.</li></ul><h3>Practical Example: Sales Forecasting</h3><p>Imagine you're a sales manager aiming to project future sales based on various scenarios. Here's how you can utilize an Input Table for this purpose:</p><ul><li><strong>Create an Empty Input Table:</strong> Set up a table with columns for 'Month', 'Projected Sales', and 'Marketing Spend'.</li><li><strong>Input Data:</strong> Enter data for each month, including projected sales figures and planned marketing expenditures.</li><li><strong>Perform Analysis:</strong> Use Sigma's analytical tools to correlate marketing spend with projected sales, helping you identify optimal investment strategies.</li></ul><h3>Conclusion:</h3><p>Input Tables in Sigma Computing provide a versatile and user-friendly means to enhance data analyses. By allowing manual data entry and integration with existing datasets, they support a wide range of applications, from basic data augmentation to complex scenario modeling. This functionality empowers users to conduct more comprehensive and flexible analyses, leading to more informed business decisions. Input Tables empower teams to work smarter with data.</p><p><br></p>

Input tables in Sigma Computing

<h2>Geospatial Analysis in Sigma Computing – Working with location-based data.</h2><p>Geospatial data is everywhere—from mapping a delivery route to tracking weather patterns. With Sigma Computing, we can take advantage of geospatial data to uncover location-based insights quickly and easily.</p><h3>What Is Geospatial Data?</h3><p>Sigma Computing supports a special data type known as geography. This data type is designed to store structured spatial data that represents geographic locations or features. Here’s what we need to know:</p><ul><li><strong>Structured Spatial Data:</strong><ul><li>Contains information like points, lines, and areas that represent real-world locations.</li><li>Can be used to map customer locations, distribution centers, or even regions of influence.</li></ul></li><li><strong>Primary Uses:</strong><ul><li>Creating maps for visualization.</li><li>Performing spatial joins to compare and contrast different geographic features.</li></ul></li><li><strong>Supported Data Sources:</strong><ul><li>Sigma directly supports the geography data type when connected to Snowflake and BigQuery.</li><li>When using other connections (like different cloud data warehouses or DBMS), Sigma retrieves data in standard geospatial formats such as Well-Known Text (WKT), though it presents them as plain text.</li></ul></li></ul><h3>Understanding Geography Data Formats</h3><p>Geography data can be represented in multiple formats, each of which visually or textually describes different kinds of geographic features. Here are the key formats and what they represent:</p><ul><li>Well-Known Text (WKT): A textual markup language for representing vector geometry objects.</li></ul><p><strong>Examples:</strong></p><ul><li style="list-style-type: none;" data-mce-style="list-style-type: none;"><ul><li><strong>POINT: </strong>POINT (10 20)</li></ul></li></ul><p>Represents a single location defined by X (longitude) and Y (latitude) coordinates.</p><ul><li style="list-style-type: none;" data-mce-style="list-style-type: none;"><ul><li><strong>LINESTRING:</strong> LINESTRING (30 40, 50 60, 70 80)</li></ul></li></ul><p>Describes a sequence of points connected by straight lines, useful for mapping roads or paths.</p><ul><li style="list-style-type: none;" data-mce-style="list-style-type: none;"><ul><li><strong>POLYGON:</strong> POLYGON ((0 0, 10 0, 10 10, 0 10, 0 0))</li></ul></li></ul><p>Defines an area with a boundary, such as a city or a country.</p><ul><li style="list-style-type: none;" data-mce-style="list-style-type: none;"><ul><li><strong>MULTIPOINT, MULTILINESTRING, and MULTIPOLYGON:</strong></li></ul></li></ul><p>These formats combine multiple points, lines, or polygons into a single entity. They’re useful when we need to represent several related features together.</p><ul><li><strong>Why Use These Formats?</strong><ul><li>They standardize how geographic information is stored and shared.</li><li>They allow for a wide range of spatial operations (like distance calculations, overlaps, or containment tests).</li></ul></li></ul><h3>Building Geography Map Charts in Sigma</h3><p>Creating a visual map that shows our geospatial data can add significant value to our analysis. Let’s walk through how we can build a geography map in Sigma.</p><p>SIgma Computing offers 3 types of Map charts-</p><ul><li><strong>Map - Points</strong><ul><li>Point maps require a numerical column on both the map's LATITUDE and LONGITUDE fields.<br></li></ul></li></ul><figure id="figure-xi5ub14s7m820qdq9"><img id="xi5ub14s7m820qdq9" src="https://cdn.durable.co/blocks/2eQHjyOR9xhjb38GgpY20Hn7so8uuKPPeBJgUSX9cqyifVXrREUTPX294CuESeeL.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/2eQHjyOR9xhjb38GgpY20Hn7so8uuKPPeBJgUSX9cqyifVXrREUTPX294CuESeeL.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><ul><li><strong>Map - Region</strong><ul><li>Region maps require a single text Columns in the Region property. Column values must match one of the following region types and be consistent within the column.</li></ul></li></ul><figure id="figure-id7oxgobbsm821p7dd"><img id="id7oxgobbsm821p7dd" src="https://cdn.durable.co/blocks/2eJasGD10CiAtsriyZGViDVj9HfFin509wD6DgMkonWFzijTAT4ely5z4aZXLvhL.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/2eJasGD10CiAtsriyZGViDVj9HfFin509wD6DgMkonWFzijTAT4ely5z4aZXLvhL.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><figure id="figure-6kufmk9hgm821qsyt"><img id="6kufmk9hgm821qsyt" src="https://cdn.durable.co/blocks/3ye5uEOYK2L4NXsC9euc7UD0u52d47sRHI0LIDJR5KaU1eqVlcXISP2zedu7xjpl.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/3ye5uEOYK2L4NXsC9euc7UD0u52d47sRHI0LIDJR5KaU1eqVlcXISP2zedu7xjpl.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><ul><li><strong>Map - Geography</strong><ul><li>WKT and JSON formats allow the storage of more complex geographical data than simple numeric lat/long columns.</li><li>Sigma's Map - Geography chart requires a <strong>geography or variant data</strong> <strong>column</strong> on the map's <strong>Geography</strong> field. If our WKT or GeoJSON data is stored as a text column (abc), we can convert it using the <strong>Geography</strong> or <strong>Variant</strong> function.</li><li>GeoJSON data must also have "coordinates" nested within a "geometry" key in order to be plotted. In GeoJSON and our geography type, the coordinate order is always longitude, latitude.</li></ul></li></ul><p><strong>Examples</strong></p><p>For example, given the following GeoJSON data:</p><figure id="figure-c47ke9si7fm8223mxi"><img id="c47ke9si7fm8223mxi" src="https://cdn.durable.co/blocks/4WcJdO2n9WWdMJS78vkSuEvyzTHeCprF88Kzi1kM1dtZMcXJrbW5J4Y6hIOx3bb7.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/4WcJdO2n9WWdMJS78vkSuEvyzTHeCprF88Kzi1kM1dtZMcXJrbW5J4Y6hIOx3bb7.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><p>Below is a non-working example, even though it is valid GeoJSON, as it lacks the "geometry" key:</p><figure id="figure-twpcyi8kgsm82266q6"><img id="twpcyi8kgsm82266q6" src="https://cdn.durable.co/blocks/3aWBqr2f84Mw0X08TFN8yIt8IazOJiVA3FWXFbAyPoJvUgWNgRyZZs6RkZ2tRqpV.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: center center;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined" data-positiony="undefined" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/3aWBqr2f84Mw0X08TFN8yIt8IazOJiVA3FWXFbAyPoJvUgWNgRyZZs6RkZ2tRqpV.png" data-mce-style="aspect-ratio: 16/9; object-position: center center;"></figure><h3>Steps to Build Your Map</h3><ul><li><strong>Step 1: Connect to Your Data Source</strong><ul><li>Confirm the data source (e.g., Snowflake or BigQuery) supports the geography data type.</li><li>For other connections, geospatial data might appear as text—use Sigma’s Geography or Variant functions to convert it.</li></ul></li><li><strong>Step 2: Prepare Your Data</strong><ul><li>Clean the data and ensure that geography columns are in the proper format (WKT or correctly structured GeoJSON).</li><li>Validate and convert text-based geospatial data using Sigma’s built-in functions if needed.</li></ul></li><li><strong>Step 3: Create a New Worksheet in Sigma</strong><ul><li>Open a new worksheet dedicated to your map.</li><li>Drag and drop the converted geography field into the visualization area.</li></ul></li><li><strong>Step 4: Configure the Map Visualization</strong><ul><li>Choose the map type that suits your data:<ul><li><strong>Region Map:</strong> For text-based identifiers like state or country names.</li><li><strong>Point Map:</strong> For numeric latitude and longitude columns.</li><li><strong>Geography Map:</strong> For complex WKT or GeoJSON data.</li></ul></li></ul></li><li>Adjust layers, colors, and labels to enhance clarity.</li></ul><h3>Geospatial Joins in Sigma: Intersect and Within</h3><p>One of the standout features in Sigma Computing is the ability to perform geospatial joins. Geospatial joins helps us answer questions like “Which customer locations lie within a sales region?” or “Which roads cross a specific area?” Sigma offers two main operators for these tasks:</p><ul><li><strong>Intersect Operator:</strong><ul><li><strong>What It Does:</strong><ul><li>Returns rows from both datasets when their geospatial objects overlap or intersect.</li></ul></li><li><strong>How to Think About It: </strong><ul><li>Imagine two circles on a map. If they overlap, the intersect operator finds those overlapping areas.</li></ul></li><li><strong>When to Use It:</strong><ul><li>Finding common areas between two spatial datasets.</li><li>Mapping where two different features (like service zones and delivery areas) touch.</li></ul></li></ul></li><li><strong>Within Operator:</strong><ul><li><strong>What It Does: </strong><ul><li>Returns rows where geospatial objects from one dataset are entirely contained within those of another.</li></ul></li><li><strong>How to Think About It:</strong><ul><li>Picture a small park inside a larger city boundary. The “within” operator would show that the park is entirely within the city.</li></ul></li><li><strong>When to Use It:</strong><ul><li>Identifying if a point (like a store location) falls completely inside a predefined boundary (such as a service area).</li></ul></li></ul></li></ul><p><strong>Practical Example:</strong></p><p>Imagining we have two datasets:</p><ul><li><strong>Dataset A:</strong> Contains customer addresses as points.</li><li><strong>Dataset B:</strong> Contains sales territories as polygons.</li></ul><p>Using the <strong>within</strong> operator, we can easily find which customers are served by which sales territory. Alternatively , if we want to see areas where customer clusters and sales territories overlap, the <strong>intersect</strong> operator comes into play.</p><figure id="figure-5dchc7w7ym822a2av"><img id="5dchc7w7ym822a2av" src="https://cdn.durable.co/blocks/3nhVBDw5SsbRhFQpQDazNLFMKiQPx9yJFEpHXQglnO8XMEKC0SZOLme6jOMozTOA.png" alt="" title="" class="object-cover bg-gray-100 rounded-lg md:rounded-xl lg:rounded-2xl" style="aspect-ratio: 16/9; object-position: undefined% 50%;" data-corners="default" data-aspect="16:9" data-caption="" data-positionx="undefined%" data-positiony="50%" data-fullwidth="false" data-mce-src="https://cdn.durable.co/blocks/3nhVBDw5SsbRhFQpQDazNLFMKiQPx9yJFEpHXQglnO8XMEKC0SZOLme6jOMozTOA.png" data-mce-style="aspect-ratio: 16/9; object-position: undefined% 50%;"></figure><p><strong>Explanation:</strong></p><ul><li><strong>Customer Data &amp; Sales Territory Data :</strong> Represent the two datasets.</li><li><strong>ST_WITHIN (or) INTERSECT:</strong> The join operation where the spatial function (either ST_WITHIN or INTERSECT) is applied.</li><li><strong>Output:</strong> The final output, which lists customers along with their corresponding sales territory.</li></ul><h3>Conclusion</h3><p>Working with geospatial data in Sigma Computing opens up a new dimension of analysis by allowing us to incorporate real-world location data into our decision-making process.</p><p>Whether we’re mapping retail locations, planning distribution routes, or analyzing regional trends, Sigma’s geospatial capabilities make the process efficient and accessible—even for users with limited technical expertise.<br></p>

Blog

Column-level masking in Snowflake

Understanding how Sigma uses Snowflake’s compute layer

Managing Big Data with Sigma Comutng

Data Apps in Sigma Computing

Input tables in Sigma Computing

Working with Geospatial Data in Sigma Computing