How SQL Mocker Uses Your Data
Understand how workspace inputs provide context for schema-aware generation and existing SQL assistance.
Read documentationDocumentation category
Privacy & Security
Understand what context SQL Mocker uses and what remains in your database environment.
What Information Is Sent to AI
Review the prompt and relevant workspace context used for an assistant request.
Read documentationDatabase Credentials
The hosted metadata workflow does not require users to provide database usernames, passwords, connection strings, or server access details to SQL Mocker.
Read documentationDatabase Metadata vs Database Data
Distinguish structural schema information from the production rows stored by the database.
Read documentationRunning Extraction Scripts
Run SQL Mocker metadata scripts yourself and review their output before returning it to the workspace.
Read documentationWorkspace Data
Understand the types of information that can be retained in a current or saved SQL Mocker workspace.
Read documentationRelationship Changes and Your Database
Relationships reviewed, added, edited, or removed in SQL Mocker remain workspace context and do not alter the database.
Read documentation