Frequently asked questions
AI features in DbVisualizer FAQ
DbVisualizer includes some strictly opt-in AI features to help users understand their schemas, generate and optimize SQL and understand errors. We've gathered the most common questions and answers regarding these features below.
The purpose is to help you interact smarter with databases with less work. The scope of the feature is:
- Converting your natural language input to executable SQL statements
- Making changes to or optimising an existing script
- Converting scripts between different SQL dialects
- Explain an error, help with database features
- General advice on databases
DbVisualizer optionally communicates the database context (metadata including table names, column names, and relationships) but does not include row level data.
No, the AI feature in DbVisualizer uses third-party services independent of DbVis Software AB. We pick what we see gives the best performance for our use cases. We test and validate the service, our integration and phrasing to make sure of optimal performance. We also reserve the right to change the service if there is something better in the market.
We are currently using OpenAI (the “AI Provider”) but can potentially add or change to other LLMs. You will be informed at startup of the AI feature which LLM is in use. And in the case of where there are other models to choose from, we will allow the user to configure which model to use.
No, not at the initial release. But it is on our roadmap for future developments. Let us know at support@dbvis.com if you want to cast a vote for prioritizing this feature.
DbVis Software ABs Data Processing Addendum can be found at: https://www.dbvis.com/dpa
DbVis Software AB is a paying API customer of Open AI. The Data Processing Addendum between Open AI and DbVis Software AB is available at: https://openai.com/policies/data-processing-addendum/
Yes, these questions are covered in the Data Processing Addendum of the AI Provider. The applicable DPAs can be found here: https://openai.com/policies/data-processing-addendum/
https://www.dbvis.com/dpa
Use your caution when you decide what to submit to the AI.
No, we will monitor access patterns and meta data for abuse, but do not persist or store your input or results. API/Enterprise data is not used for model training by default (as per provider DPAs) and retention typically applies (~30 days).
No, DbVisualizer will not send any table-data or similar contained in your databases to the AI Providers. However, we will send your prompt and error messages that you wish to fix.
Subject to your opt-in, we will provide the AI with context to deliver better results. This includes, but not limited to, your type of database, driver, structure of your database and your schema. The exact context will be displayed in your AI chat in DbVisualiser which can also be customized according to your preferences.
Compliance is not required since it has been determined that the AI feature in DbVisualizer falls outside of Article 3 in the EU AI Act. In the language of this law, DbVis Software is a distributor of the AI feature, and Open AI is the provider.
No, and there are no current plans for certification, based on the current limited scope of the AI feature in DbVisualizer. But we are monitoring our AI Provider(s) for both ISO certification and EU AI act compliance.
There is an AI balance included per user, set by your license type, at no additional cost.
For an initial limited time only, DbVis will top up your balance free of charge, We do however reserve the right to deny additional balance if we deem usage abusive.
When your AI balance runs out, the AI feature will stop processing prompts. Users will be able to top-up their balance to reactivate the AI feature in the DbVisualizer User Portal (launching in 2026). Full pricing available after the User Portal is launched.
Please note that you need an internet connection to run the AI feature.
An active subscription of the Pro version or an Eval license is required to use the AI feature.
We are responsible for embedding and transferring your prompts safely to the AI, but not for how the AI handles your data, nor can we be held liable for the quality of the results or any consequential damages. The same caution should be applied when using the AI feature in DbVisualizer as when using a commercially available AI service directly, including the prompts you write, the data you submit, and how you scrutinize the results.
Yes, the AI feature in DbVisualizer is Opt-In and disabled by default. It can also be disabled via central configuration.
No, the AI feature is strictly user initiated.
- The user logs in using the DbVisualizer Authorization Server, creating an account on their first login.
- The authorization server issues a short-lived access token.
- The DbVisualizer client packages your prompt, conversation history, and optional context (type of db, driver, structure, schema). DbVisualizer connects to our AI backend via encrypted https streaming request, using the access token as authorization.
- The DbVisualizer AI Backend processes the request:
a. Enrichment of the message - add additional context sources for LLM understanding + restructures the message for optimal LLM processing
b. Minification (optimize for token usage)There is no data persisted in the DbVisualizer AI backend regarding the contents of the prompt. Only metadata such as which model, token usage, timestamp etc are persisted.
There is no data persisted in the DbVisualizer AI backend regarding the contents of the prompt. Only metadata such as which model, token usage, timestamp etc are persisted.
- The request is sent to the selected AI provider and model for processing.
- The response is relayed to the DbVisualizer client.
Potentially yes. Use caution when you decide what to include in your prompts.
See data processing agreement regarding organizational and technical measures: https://www.dbvis.com/dpa
AI usage is auditable with respect to users, request timestamps and token consumption. Not the content of prompt or response as that is not persisted.
Please see our DPA here: https://www.dbvis.com/dpa
At this time, AI can be disabled at the client level, not per connection.