{"id":2626,"date":"2020-12-19T20:04:36","date_gmt":"2020-12-19T12:04:36","guid":{"rendered":"https:\/\/www.gudusoft.com\/?page_id=2626"},"modified":"2026-07-13T22:08:44","modified_gmt":"2026-07-14T06:08:44","slug":"sqlflow-faq","status":"publish","type":"page","link":"https:\/\/www.gudusoft.com\/jp\/sqlflow-%e3%82%88%e3%81%8f%e3%81%82%e3%82%8b%e8%b3%aa%e5%95%8f\/","title":{"rendered":"sqlflow FAQ"},"content":{"rendered":"

Answers to the questions we hear most about Gudu SQLFlow<\/strong> \u2014 what it does, how it treats your data, the editions and pricing, how to get SQL in and lineage out, and how to manage your account.<\/p>\n\n\n\n

\n
39<\/b>SQL\u65b9\u8a00\u306b\u306f\u305d\u308c\u305e\u308c\u5c02\u7528\u306e\u30d1\u30fc\u30b5\u30fc\u304c\u3042\u308b\u3002<\/span><\/div>\n
\u5217\u30ec\u30d9\u30eb<\/b>\u8840\u7d71\u3001\u76f4\u63a5\u304a\u3088\u3073\u9593\u63a5<\/span><\/div>\n
\u7121\u6599<\/b>tier \u2014 no card required<\/span><\/div>\n
\u9759\u7684<\/b>analysis \u2014 never reads your table data<\/span><\/div>\n<\/div>\n\n\n\n
\n\n

New to SQLFlow?<\/strong> \u30af\u30a8\u30ea\u3092\u8cbc\u308a\u4ed8\u3051\u3066 free online visualizer<\/a> and watch its column-level lineage appear \u2014 no signup needed for public examples.<\/p>\n\n<\/div><\/div>\n\n\n\n

About SQLFlow<\/h2>\n\n\n\n

What is Gudu SQLFlow?<\/h3>\n\n\n

Gudu SQLFlow \u306f\u81ea\u52d5\u5316\u3055\u308c\u305f SQL\u30c7\u30fc\u30bf\u30ea\u30cd\u30fc\u30b8\u30c4\u30fc\u30eb<\/a>. You give it SQL \u2014 queries, stored procedures, dbt projects, or a whole database \u2014 and it produces an interactive, column-level data lineage diagram that shows exactly where every piece of data comes from and where it goes. It works by static analysis of your SQL code, so it never needs access to your data.<\/p>\n\n\n\n

What is column-level data lineage?<\/h3>\n\n\n

Table-level lineage tells you that one table is built from another. \u5217\u30ec\u30d9\u30eb\u306e\u7cfb\u7d71<\/a> tells you, for every output column, the exact source columns that feed it and the functions, joins, and set operations along the way. That granularity is what makes impact analysis and audit answers precise instead of approximate.<\/p>\n\n\n\n

\u9593\u63a5\u7684\uff08\u5f71\u97ff\uff09\u7cfb\u8b5c\u3068\u306f\u4f55\u3067\u3059\u304b\uff1f<\/h3>\n\n\n

A column used in a \u3069\u3053<\/code> clause, a \u53c2\u52a0\u3059\u308b<\/code> condition, or a \u30b0\u30eb\u30fc\u30d7\u5206\u3051<\/code> never lands in the output, but it absolutely shapes the result. SQLFlow models this influence as a distinct, toggleable relationship type \u2014 indirect lineage \u2014 so you can see pure data flow or the full impact surface. Most lineage tools do not make this distinction, and it is exactly what impact analysis needs.<\/p>\n\n\n\n

Which SQL dialects does SQLFlow support?<\/h3>\n\n\n

39 dialects, each with its own dedicated parser rather than a generic ANSI approximation: Snowflake, BigQuery, Redshift, Databricks, Azure SQL, Athena, Oracle, SQL Server, PostgreSQL, MySQL, IBM Db2, Teradata, Netezza, Greenplum, Vertica, SAP HANA, Hive, Impala, Spark SQL, Presto, Trino, ClickHouse, DuckDB, and more. You choose the dialect for each analysis.<\/p>\n\n\n\n

Can SQLFlow analyze stored procedures and dynamic SQL?<\/h3>\n\n\n

Yes \u2014 this is one of its strongest capabilities. Oracle PL\/SQL and SQL Server T-SQL have dedicated procedural parsers. SQLFlow traces lineage through procedure parameters and temp tables, resolves dynamic SQL assembled inside procedures, and draws an interactive call graph of which procedures invoke which.<\/p>\n\n\n\n

SQLFlow\u306fdbt\u3092\u30b5\u30dd\u30fc\u30c8\u3057\u3066\u3044\u307e\u3059\u304b\uff1f<\/h3>\n\n\n

\u306f\u3044\u3002dbt\u30de\u30cb\u30d5\u30a7\u30b9\u30c8\u3092\u30a4\u30f3\u30dd\u30fc\u30c8\u3059\u308b\u3068\u3001SQLFlow\u304cdbt\u30e2\u30c7\u30eb\u5168\u4f53\u306b\u308f\u305f\u308b\u5217\u30ec\u30d9\u30eb\u306e\u30c7\u30fc\u30bf\u30ea\u30cd\u30fc\u30b8\u3092\u751f\u6210\u3057\u3001\u30e2\u30c7\u30eb\u3068\u305d\u308c\u3089\u304c\u69cb\u7bc9\u3059\u308b\u30a6\u30a7\u30a2\u30cf\u30a6\u30b9\u30aa\u30d6\u30b8\u30a7\u30af\u30c8\u3068\u306e\u6574\u5408\u6027\u3092\u53d6\u308b\u3053\u3068\u304c\u3067\u304d\u307e\u3059\u3002<\/p>\n\n\n\n

\n\n

How is SQLFlow different from open-source parsers like sqlglot or sqllineage?<\/h3>\n\n\n

\u30aa\u30fc\u30d7\u30f3\u30bd\u30fc\u30b9\u30d7\u30ed\u30b8\u30a7\u30af\u30c8 sqlglot<\/code> \u3068 SQL Lineage<\/code> are good tools for parsing individual queries, and for simple SELECT\/INSERT statements they may be all you need. The gap appears on real production code: stored procedures and dynamic SQL, dialect-specific syntax across dozens of engines, star-expansion and view resolution that need schema context, indirect lineage through filter and join conditions, and visualizing lineage at the scale of thousands of scripts.<\/p>\n\n\n

SQLFlow\u306f\u3001 \u6c4e\u7528SQL\u30d1\u30fc\u30b5\u30fc<\/a>, a commercial SQL compiler front-end developed since the mid-2000s and validated against roughly 13,000 per-dialect test fixtures. That depth on hard SQL is the difference. If you are evaluating, run your gnarliest stored procedure through both and compare.<\/p>\n\n<\/div><\/div>\n\n\n\n

Data, security & deployment<\/h2>\n\n\n\n

SQLFlow\u306f\u79c1\u306e\u30c7\u30fc\u30bf\u3092\u8aad\u307f\u53d6\u308a\u307e\u3059\u304b\uff1f<\/h3>\n\n\n

No. SQLFlow performs static analysis of SQL code and optionally reads schema metadata \u2014 table and column definitions. It never reads the rows in your tables. There is no code path that reads business data.<\/p>\n\n\n\n

Can I run SQLFlow inside my own network or air-gapped?<\/h3>\n\n\n

\u306f\u3044\u3002 SQLFlow \u30aa\u30f3\u30d7\u30ec\u30df\u30b9<\/a> deploys via Docker or Kubernetes inside your network and runs fully air-gapped, with no cloud dependency and no outbound connection. With the on-premise edition your SQL text never leaves your infrastructure \u2014 which is why banks, healthcare providers, and government teams use it.<\/p>\n\n\n\n

Where does my SQL go with SQLFlow Cloud?<\/h3>\n\n\n

With SQLFlow \u30af\u30e9\u30a6\u30c9<\/a>, the SQL you submit is analyzed on Gudu-hosted servers and is never used to read your data. If your policy forbids SQL text leaving your network, use SQLFlow On-Premise, which runs the identical engine inside your own infrastructure.<\/p>\n\n\n\n

Editions, pricing & access<\/h2>\n\n\n\n

\u7121\u6599\u7248\u306f\u3042\u308a\u307e\u3059\u304b\uff1f<\/h3>\n\n\n

Yes. SQLFlow Cloud has a free tier \u2014 paste SQL and get column-level lineage diagrams in your browser, including indirect lineage, ER diagrams, call graphs, and the AI lineage query. Premium adds larger inputs, REST API access, and team features.<\/p>\n\n\n\n

SQLFlow\u306e\u6599\u91d1\u306f\u3044\u304f\u3089\u3067\u3059\u304b\uff1f<\/h3>\n\n\n

SQLFlow Cloud starts free; premium accounts are $49.99\/month. SQLFlow On-Premise is $500\/month or $4,800 one-time per selected database type, installable on two servers. Full details are on the \u4fa1\u683c\u30da\u30fc\u30b8<\/a>.<\/p>\n\n\n\n

Does SQLFlow have a REST API?<\/h3>\n\n\n

Yes. The SQLFlow REST API<\/a> exposes the full analysis surface as JSON over HTTP \u2014 submit SQL and receive the column-level lineage graph \u2014 so you can automate lineage in CI pipelines, catalogs, and internal tools. API access is included with premium and on-premise plans.<\/p>\n\n\n\n

Can I embed SQLFlow in my own application?<\/h3>\n\n\n

Yes. An embeddable JavaScript widget with a 30+ method API drops the interactive lineage diagram into any web app, and a Java library exposes the same engine for backend JVM integration. The API, widget, and library all return consistent results because they share one parser.<\/p>\n\n\n\n

Getting data in and out<\/h2>\n\n\n\n

How do I get my SQL into SQLFlow?<\/h3>\n\n\n

Three ways: paste SQL directly, upload SQL files or a dbt manifest, or connect a source \u2014 pull metadata from a live database over JDBC, or feed in Snowflake query history or Redshift query logs. In every case SQLFlow analyzes SQL code and schema metadata only.<\/p>\n\n\n\n

What is SQLFlow Ingester (Grabit)?<\/h3>\n\n\n

SQLFlow Ingester<\/a> (formerly Grabit) is a command-line tool that collects SQL \u2014 the DDL of tables, views, procedures, functions, and triggers \u2014 from databases over JDBC, from GitHub or Bitbucket, or from the file system, and feeds it to SQLFlow. It extracts metadata only and schedules cleanly as a cron job for automated, repeatable extraction.<\/p>\n\n\n\n

\u5229\u7528\u53ef\u80fd\u306a\u30a8\u30af\u30b9\u30dd\u30fc\u30c8\u5f62\u5f0f\u306f\u4f55\u3067\u3059\u304b\uff1f<\/h3>\n\n\n

Lineage exports as JSON (structured, machine-readable), CSV (for spreadsheets and catalogs), and PNG (for documents and reviews). Enterprise deployments add export adapters for DataHub, Microsoft Purview, and OpenMetadata.<\/p>\n\n\n\n

Can SQLFlow feed my data catalog?<\/h3>\n\n\n

Yes. SQLFlow slots in as the lineage engine behind a catalog you already run: analyze your SQL estate, then push the results into DataHub, Microsoft Purview, or OpenMetadata through the included export adapters, or into anything custom via JSON\/CSV and the REST API.<\/p>\n\n\n\n

Can I ask questions about the lineage in plain English?<\/h3>\n\n\n

Yes. Since version 8.2.3, SQLFlow includes an AI lineage query: ask questions like \u300c\u3069\u306e\u30ec\u30dd\u30fc\u30c8\u304c\u9867\u5ba2\u306e\u30e1\u30fc\u30eb\u306b\u4f9d\u5b58\u3057\u3066\u3044\u308b\u306e\u3067\u3059\u304b\uff1f\u300d<\/em> against the analyzed graph. Answers are grounded \u2014 every table and column the AI references is validated against the lineage graph before it reaches you.<\/p>\n\n\n\n

\n\n

SQL\u306e\u7cfb\u7d71\u56f3\u3092\u4eca\u3059\u3050\u78ba\u8a8d\u3057\u307e\u3057\u3087\u3046<\/h2>\n\n\n

\u7121\u6599\u306e\u30d3\u30b8\u30e5\u30a2\u30e9\u30a4\u30b6\u30fc\u306b\u30af\u30a8\u30ea\u3092\u8cbc\u308a\u4ed8\u3051\u308b\u304b\u3001\u6240\u6709\u5730\u5168\u4f53\u306e\u30b9\u30ad\u30e3\u30f3\u306b\u3064\u3044\u3066\u3054\u76f8\u8ac7\u304f\u3060\u3055\u3044\u3002<\/p>\n\n\n

\n
SQLFlow\u3092\u7121\u6599\u3067\u304a\u8a66\u3057\u304f\u3060\u3055\u3044<\/a><\/div>\n\n\n\n
\u4fa1\u683c\u3092\u898b\u308b<\/a><\/div>\n<\/div>\n\n<\/div><\/div>\n\n\n\n

Account & sign-in<\/h2>\n\n\n\n

Where do I find my UserId and secret key?<\/h3>\n\n\n\n

Open https:\/\/sqlflow.gudusoft.com<\/a> and click the avatar icon at the top-right corner of the page. You will see this:<\/p>\n

\"SQLFlow\u30a2\u30ab\u30a6\u30f3\u30c8\u30e1\u30cb\u30e5\u30fc<\/p>\n

Click the Account<\/strong> menu item, then use the \u751f\u6210<\/strong> button to create a new secret key.<\/p>\n

\"SQLFlow<\/p>\n

With your UserId and secret key, follow the REST API instructions at github.com\/sqlparser\/sqlflow_public\/tree\/master\/api<\/a>.<\/p>\n\n\n\n

Why am I unable to log in?<\/h3>\n\n\n\n

Two things commonly block sign-in:<\/p>\n

1. Your account is not activated.<\/strong> When you sign up, you receive an email asking you to activate your account. If you try to log in before clicking that link, the login form shows:<\/p>\n

code:unauthorized, description:\u30ed\u30b0\u30a4\u30f3\u524d\u306b\u30e1\u30fc\u30eb\u30a2\u30c9\u30ec\u30b9\u3092\u78ba\u8a8d\u3057\u3066\u304f\u3060\u3055\u3044\u3002<\/strong><\/em><\/p>\n

Click the link in your activation email, then return to https:\/\/sqlflow.gudusoft.com<\/a> \u518d\u5ea6\u30ed\u30b0\u30a4\u30f3\u3057\u307e\u3059\u3002<\/p>\n

2. Your browser is blocking third-party cookies.<\/strong> If so, you will see one of these errors:<\/p>\n

\u4e0d\u660e\u307e\u305f\u306f\u7121\u52b9\u306a\u30ed\u30b0\u30a4\u30f3 \u30c1\u30b1\u30c3\u30c8<\/strong><\/em><\/p>\n

\"Error:<\/p>\n

\u78ba\u8a8d\u30da\u30fc\u30b8\u3092\u69cb\u6210\u3067\u304d\u307e\u305b\u3093<\/strong><\/em><\/p>\n

\"Error:<\/p>\n

Disable “Block third-party cookies” in your browser to fix it:<\/p>\n

Chrome<\/strong><\/p>\n

\"Chrome:<\/p>\n

Firefox<\/strong><\/p>\n

\"Firefox:<\/p>\n

Microsoft Edge<\/strong><\/p>\n

\"Microsoft<\/p>\n\n\n\n

\n\n

Still have a question?<\/h2>\n\n\n

Try SQLFlow free on your own SQL, or reach out and we’ll help you scope it.<\/p>\n\n\n

\n
SQLFlow\u3092\u7121\u6599\u3067\u304a\u8a66\u3057\u304f\u3060\u3055\u3044<\/a><\/div>\n\n\n\n
\u304a\u554f\u3044\u5408\u308f\u305b<\/a><\/div>\n<\/div>\n\n<\/div><\/div>\n\n\n\n