SQL Studio Workflow
Use this page as the map for SQL Studio in Mission Control. It tells you which screen to open for each job, in what order, and which detailed guide to follow next.
Audience: Data analysts, controllers, ERP leads, report writers, and other tech-savvy users who write or inspect Vista SQL in Mission Control.
Where: Mission Control → SQL Studio
Prerequisites (outside this pack)
SQL Studio runs against your team's Vista SQL connection. Before you rely on Run SQL:
- Complete day-zero SQL access setup — see Vista SQL Access Overview, and Cloud SQL Connectivity or ODBC Driver for SQL Server as needed.
- Confirm the team's Azure Bridge / connector is online — see Azure Bridge FAQ (and the customer FAQ if you are troubleshooting with end users).
This guide set assumes Bridge is already working. It does not re-document connector install or purchase flows.
What each area owns
SQL Studio is two pages. Use the visualizer to understand tables and copy boilerplate; use the editor to run queries, review grids, and keep reusable statements.
| Domain | What you do | Where |
|---|---|---|
| Schema exploration | Browse Vista tables, place them on a canvas, inspect columns/joins, copy generated SQL | Schema Visualizer |
| Query execution | Write or paste SQL, run SELECT/WITH, review and export results | SQL Editor |
| Reusable SQL | Save, open, favorite, rename, duplicate, and delete statements | SQL Editor → SQL Statements sidebar |
Recommended order
- Confirm Bridge — if Run SQL fails with connection/permission errors, fix connectors first (links above), not the query.
- Explore schema (optional) — in Schema Visualizer, add tables from Tables, follow joins, then copy from Canvas SQL or the table SQL panel.
- Paste and run — open SQL Editor, paste or write a
SELECT/WITHstatement, click Run SQL (or Run Selected when text is highlighted). - Review / export — use the results grid; export with CSV or EXCEL when you need a file.
- Save for reuse — click Save so the statement appears under SQL Statements for later opens.
You can skip the visualizer if you already know the tables and SQL. You should not skip Bridge readiness if execution fails before you get a grid.
Mission Control page map
| Nav item | Route | Use it to… |
|---|---|---|
| SQL Editor | /missioncontrol/sql/sql-editor | Manage tabs and SQL Statements; Run SQL / Run Selected; Save, Format, Suggestions; export results. |
| Schema Visualizer | /missioncontrol/sql/schema-visualizer | Search Tables, build a canvas, inspect properties, copy generated SELECT / INSERT / UPDATE / DELETE SQL. Does not execute SQL. |
Editor vs Visualizer
| SQL Editor | Schema Visualizer | |
|---|---|---|
| Primary job | Run queries and keep saved statements | Explore schema and generate copyable SQL |
| Executes against Vista? | Yes — Run SQL / Run Selected | No — copy only |
| Allowed to run | Statements that start with SELECT or WITH | N/A (no run) |
| Generated DML (INSERT / UPDATE / DELETE) | Not executed here | Available as copy text for external use |
| Persist model | Saved statements on the server; open tabs/drafts in the browser | Canvas layout in the browser (localStorage); no server-saved diagrams |
Design or discover joins in the visualizer. Execute and save in the editor. Do not expect INSERT / UPDATE / DELETE copied from the visualizer to run inside SQL Studio.
SELECT-only execution
Run SQL and Run Selected only send statements that begin with SELECT or WITH (after trim). Other statement types do not run from the editor toolbar.
If you need DML for Vista outside TUDS, generate it in Schema Visualizer and copy it out — SQL Studio will not execute it for you.
Guides in this set
| Guide | Status |
|---|---|
| Write, run, and save SQL queries | Drafted |
| Explore Vista schema and generate SQL | Drafted |
Start with Schema Visualizer if you need table/join context first. Start with the SQL Editor guide if you already have a query to run or save.