Frequently Asked Questions

This page contains some frequently asked questions. You can also check the details response under the subpages.

Q1: How to deal with internal database?

If your database is deployed in an internal network which is not accessible for external connection request, you can:

  1. Use sqlflow-ingester to export the database metadata file.

  2. Use SQLFlow on-premise version.

Check deal with internal database for more details.

Q2: Can I delete my account?

Yes, you can delete your account. Check here for how to do that.

Note: your data will be deleted with your account together

Q3: How to output only the relationships in a table form without temporary intermediates, just column to column relationships between tables?

You can archive this using one of the following two approaches:

  • If you are using SQLFlow UI, change the SQLFlow UI settings and download the data lineage as CSV.

  • You can make REST api request to get the desired CSV data.

Check Table Form Data Without Intermediates to get more details.

Q4: Some schema are missing in the result when using Oracle

Try to check the metadata.json to see whether there's a ORA-01000 error.

ORA-01000: maximum open cursors exceeded tips

Alter the open_cursors value to fix this issue .

Check Not all schema exported from Oracle to get more details.


To facilitate team working with data lineage, one of the premium account privilege is to create shareable link for the data lineage result generated by SQLFlow.

pageBasic Usage

However, in case of the expiration of your premium account, the link used for sharing will expire together with your account even if they were generated before the account's expiration. So please remember to renew in time if these links are still being used.

Q6: Getting "Failed to fetch" when creating a SQLFlow Job

There are various possible reasons to cause this issue:

  • Poor network quality

  • Cross-domain issue between the server and the client

  • Wrong Nginx config

  • Certificate problem for HTTPS

  • Insufficient server disk space

  • ...

Yon can check your browser console to see the error details (F12 for chrome)

Please contact us and send us the error details to support@gudusoft.com. Our support team will help you to solve out this issue.

Q7: Failed to start SQLflow backend for Windows users

Windows users may have following issue when trying to start the sqlflow backend:

This might be due to the lack of memory. SQLFlow needs at least 32G RAM available. Please check if you have enough RAM available.

To assign more memory to SQLFlow, please edit the sqlservice.bat file under sqlflow\backend\bin, add the following line of code after line 16: set heapsize=4G

The more RAM you assign to SQLFlow, the more complex SQL it would be able to deal with and your host server should have enough RAM to assign.

Q8: Get license fail: Could not initialize class com.gudusoft.gspLive.validate.utils.MachineFingerprint

If you have installed SQLFlow On-Premise but when going to your local SQLFlow UI and see this error:

Get license fail: Could not initialize class com.gudusoft.gspLive.validate.utils.MachineFingerprint

It is probably due to the lack of disk space. You can confirm that by checking the log files under


You need to clean your disk and prepare more disk space to launch the SQLFlow backend.

Last updated