How to use Google Sheets with SQL: multi-column guide

If you’re a founder, marketer, or agency owner, “select multiple columns in SQL” sounds technical—but in practice it’s just choosing which truths about your business you want to see. The trick is doing it reliably, at scale, and getting it into Google Sheets where your team actually works. Let’s walk through practical ways to do this, from manual SQL to fully automated AI-agent workflows.### 1. Traditional/manual ways to select multiple columns in SQLThese approaches assume you or your team run queries directly on a database (PostgreSQL, MySQL, etc.) using a console or GUI tool.1) Basic multi-column SELECT- Goal: Pull specific fields from a single table.- Syntax: SELECT column1, column2, column3 FROM table_name;- Example: SELECT id, email, created_at FROM customers;- Steps: 1. Open your SQL tool (e.g., psql, MySQL Workbench, or a cloud console). 2. Identify the exact column names (often via DESCRIBE table_name or GUI schema browser). 3. Type SELECT id, email, created_at FROM customers; and run. 4. Export results as CSV and import into Google Sheets if needed.- Reference: PostgreSQL SELECT docs: https://www.postgresql.org/docs/current/sql-select.html2) Selecting all columns, then narrowing- Sometimes you don’t yet know which columns you need.- Syntax: SELECT * FROM table_name;- Steps: 1. Run SELECT * FROM leads; to explore. 2. Note down the column names you actually care about (e.g., name, email, utm_source, created_at). 3. Refine to SELECT name, email, utm_source, created_at FROM leads; for ongoing use.- Reference: General SELECT overview: https://dev.mysql.com/doc/refman/8.0/en/selecting-rows.html3) Selecting multiple columns with conditions (WHERE)- Goal: Limit rows to what’s relevant (e.g., active campaigns only).- Syntax: SELECT col1, col2 FROM table WHERE condition;- Example: SELECT campaign_name, channel, spend FROM marketing_spend WHERE date BETWEEN '2025-01-01' AND '2025-01-31';- Steps: 1. Decide which columns you need for your report. 2. Add a WHERE clause with date or status filters. 3. Test on a small date range first, then widen.4) Using column aliases for clarity- Goal: Make your exports easier to read in Google Sheets.- Syntax: SELECT column_name AS friendly_name FROM table;- Example: SELECT email AS customer_email, created_at AS signup_date FROM customers;- This makes your Sheet headers useful without manual renaming.- Reference on aliases: https://www.w3schools.com/sql/sql_alias.asp5) Joining tables and selecting multiple columns across them- Real business data usually lives in multiple tables.- Example: SELECT c.id, c.email, s.plan_name, s.mrr FROM customers c JOIN subscriptions s ON c.id = s.customer_id;- Steps: 1. Identify the join key (like customer_id). 2. Decide which columns from each table you need. 3. Use table aliases (c, s) to keep the query readable.6) Limiting results for testing- Don’t crash your DB while experimenting.- Syntax: SELECT col1, col2 FROM table LIMIT 50;- Use LIMIT to validate column choices before running full-scale.**Pros of manual methods:** Complete control, full SQL power, works in any database.**Cons:** Human time cost, error-prone, tedious exports into Google Sheets, hard to standardize across a growing team.### 2. No-code methods with Google Sheets and automation toolsIf you’d rather stay in Google Sheets and still get SQL-style column selection, these options help.1) Google Sheets QUERY function- Sheets has a built-in SQL-like language via QUERY.- Syntax: =QUERY(A1:F1000, "select A, C, F where F > 100", 1)- Steps: 1. Place your raw data in a Sheet (imported CSV, connected data, or pasted export). 2. In a new tab, use QUERY to select only the columns you need. 3. Use letters instead of column names (A, B, C) but treat them like SELECT statements.- Official docs: https://support.google.com/docs/answer/30933432) Connected Sheets / Data connectors to SQL-like sources- If you use BigQuery or similar, Google Sheets can query it directly.- Steps (BigQuery example): 1. In Google Sheets, go to Data > Data connectors > Connect to BigQuery. 2. Choose your project and dataset. 3. Use the connector UI or SQL editor to specify columns, such as: SELECT id, email, country FROM analytics.users; 4. Load results into a Sheet and schedule refresh.- Docs: https://support.google.com/docs/answer/75728953) Zapier/Make/Integromat flows from SQL to Google Sheets- Tools like Zapier or Make let you visually pick which columns to pull.- Typical Zapier flow: 1. Trigger: “Schedule – every hour/day.” 2. Action: “MySQL – Find Rows” or “Run SQL” (you write the SELECT with chosen columns). 3. Action: “Google Sheets – Create Spreadsheet Row(s)” and map each SQL column to a Sheet column.- No-code, but you still design the SELECT and mapping once.**Pros of no-code methods:** Friendly UI, closer to where business teams live, can be scheduled, less engineering needed.**Cons:** Still requires someone to understand which columns to pick, brittle when schemas change, complex to manage at scale across many reports or clients.### 3. Scaling with AI agents (Simular) for Sheets + SQLHere’s where things become interesting for busy agencies and teams: you can delegate the entire “select multiple columns in SQL and push to Google Sheets” loop to an AI computer agent.Simular’s agents operate your desktop, browser, and cloud tools like a power user: opening your SQL client, writing queries, exporting results, and updating Sheets—thousands of steps, reliably.1) Agent as your SQL & Sheets operator- Workflow idea: 1. You describe the task: “Every morning, query our PostgreSQL database for id, email, plan, mrr from subscriptions where status = 'active', then update the ‘MRR Overview’ Google Sheet.” 2. The Simular agent opens your DB tool, writes a precise SELECT id, email, plan, mrr FROM subscriptions WHERE status = 'active'; 3. It exports results, opens Google Sheets in the browser, pastes or imports data into the right tab, and cleans headers. 4. You plug this into your pipeline via webhook so it runs on schedule.- Pros: No repetitive clicking, consistent column selection, easy to change the spec by natural language.- Cons: Requires initial setup and security controls; best for recurring workflows.2) Agent maintaining many reports and clients- If you’re an agency with multiple client databases: 1. Train the Simular agent on your standard reporting templates (which columns, which filters, which Sheets tabs). 2. For each client, the agent logs into the correct DB, runs the appropriate SELECTs, and updates client-specific Sheets. 3. When schemas change (columns renamed, added), you update instructions once; the agent adapts across all accounts.- Pros: Massive leverage for agencies and RevOps teams; you scale reporting without scaling headcount.- Cons: Needs good documentation of edge cases; you’ll want a human to review the first few runs.3) Agent-driven quality control on SQL selections- The agent can also validate your existing queries: 1. It reads your saved SQL scripts. 2. It compares the selected columns to what downstream Google Sheets or dashboards expect. 3. It flags overuse of SELECT * and suggests explicit column lists.- Pros: More reliable analytics, fewer broken dashboards.- Cons: Slight upfront time to plug in your SQL scripts and Sheets references.Because Simular Pro is designed for production-grade reliability, transparent execution, and long workflows, it’s well-suited to this seemingly small but constant task: selecting the right SQL columns and keeping Sheets perfectly in sync.