← 输入框|sqlnb.com|刷新
Sidequery

SQL Notebook Support

Help for SQL Notebook on iPhone and iPad.

Contact support

For questions, bug reports, or feature requests, email [email protected].

Include your app version, iOS or iPadOS version, device model, the steps you took, and the error message. A small example or screenshot can help. Remove passwords, access tokens, personal records, and confidential database contents first.

Start with the welcome notebook

  1. Open SQL Notebook and the welcome notebook.
  2. Change the multiplier in the sample, then tap Run All.
  3. Swipe from the left edge to open your data and notebooks.

The default connection runs SQLite locally using temporary storage. You do not need an account or an external database to try the sample. SQL Notebook is free to use.

Connect to your data

The iOS app supports SQLite, DuckDB, DuckDB Quack, PostgreSQL, and Flight SQL. Open Connections, choose Add Connection, and select your database type. Enter the details required by your database provider and save the connection with Done.

Local SQLite and DuckDB connections do not require a remote account. Remote connections require a reachable server and the credentials your provider gives you. Flight SQL supports OAuth client credentials when configured with a secure endpoint.

If a query or connection fails

  • Run the welcome sample on the default connection to check that local queries work.
  • Confirm the selected connection and the SQL syntax for that database.
  • For remote databases, check the host, port, credentials, TLS settings, and any required VPN or network access.
  • If you use temporary SQLite storage, do not rely on it to retain database tables between sessions. Keep your notebook and use a saved database file when you need persistent data.

If the issue continues, email the error and a minimal example that does not contain private data.

Privacy

No Sidequery account is needed. Notebooks are stored locally, and saved connection credentials use the device’s Keychain. Remote queries go directly to the database or authentication provider you choose. Read the SQL Notebook Privacy Policy for details.