Settings
Configure SQL connections, AI providers, licensing, local app lock, cache behavior, thresholds, and visual preferences from one control surface.
Getting Started
Settings is the product-wide control surface for SQL connections, AI providers, generation behavior, prompt rules, tuning feedback memory, licensing, local application access protection, cache behavior, query-analysis thresholds, and visual preferences. Most users visit this page during first-run setup and then return only when infrastructure, credentials, or workflow policies change.
- Add or update a SQL Server connection
- Set up, test, and select a default AI provider
- Tune generation temperatures and prompt rules
- Review tuning feedback memory from earlier AI-assisted actions
- Review trial or licensed state and configure local app lock
- Adjust UI font size and navigation visibility
- General
- AI / LLM
- Database
- Tuning Memory
- Access Licensing
- Appearance
General Settings and Module Visibility
The General tab controls startup behavior, menu visibility, and Query Analysis bottleneck thresholds. This is the right place for UI simplification and interpretation tuning, not for SQL connectivity or AI credentials.
- General
- AI / LLM
- Database
- Tuning Memory
- Access Licensing
- Appearance
- Reset to Defaults restores main application settings.
- Save Settings persists the current configuration state.
- Some tab-level actions are immediate, such as testing a connection or validating a license.
The most common onboarding sequence after installation is to configure Database first, then add one provider in AI / LLM, and only after that revisit advanced thresholds or prompt rules.
- Language
- Startup
- Navigation Menu
- Query Analysis bottleneck thresholds
- Interface language is currently fixed to English.
- Navigation visibility simplifies the UI but does not uninstall modules.
- Query Analysis thresholds affect interpretation inside Query Statistics, not SQL Server itself.
- Use threshold changes sparingly and validate on known workloads.
AI Provider Management
The Providers tab is where you add, test, edit, and choose the default AI model backend. This is the normal starting point for Ollama, OpenAI, Azure OpenAI, Anthropic, or DeepSeek configuration.
Generation Temperature Controls
The Generation tab tunes output determinism for core and advanced workflows. Lower values produce more deterministic responses; these values should be changed carefully and validated on the exact workflow they affect.
AI Prompt Rules
AI Prompt Rules expose the internal system and user prompt templates behind different workflows. This is an advanced area and should only be changed when a repeated quality problem justifies prompt-level intervention.
- Providers
- Generation
- AI Prompt Rules
- Add AI Model
- Test the provider
- Set Default
- Save Settings
Database Connections and Query Settings
The Database tab manages saved connection profiles, timeout policy, and caching behavior. This is the most important Settings tab during onboarding because every analysis module depends on one or more working saved SQL Server profiles.
- Database Connections
- General Query Settings
- Cache Settings
- Test Connection validates the current profile before saving.
- Encrypt Connection should usually remain enabled.
- Trust Server Certificate should be used only when the environment requires it.
- Clear Cache is for freshness troubleshooting, not routine cleanup.
Tuning Feedback Memory
Tuning Memory stores the review history of AI-generated object and tuning actions. It helps the operator mark suggestions as hard-blocked, improved, or reset, so prior decision context stays visible over time.
- Search and review prior AI-generated actions
- Track outcome, block state, confidence, and fingerprints
- Mark Hard Block, Mark Improved, or Reset to Suggested
- This tab is a review and feedback surface, not an automatic execution engine.
- Outcome, block state, and confidence should be treated as operator guidance, not as hard truth.
- Use it to retain human judgement across repeated AI-assisted analysis sessions.
Access Licensing and Local App Lock
Access Licensing combines visible license state, identity fields, local app lock, and guided activation entry points. This is where you review trial or licensed state and decide whether the machine needs password-protected local access.
- License Status
- Identity
- Local App Lock
- Guided Activation
- Generate Device ID only when needed; the saved device ID is typically preserved.
- Use Start Trial or the activation wizard based on your entitlement path.
- Clear License removes local state but does not necessarily revoke server-side entitlement.
- Local App Lock should be treated as real machine-level access control.
Appearance Preferences
Appearance stores visual preferences such as theme and font sizes. These are usability settings rather than performance or connectivity settings, and they are mainly used to improve readability on dense displays.
- Theme
- Fonts
- Theme is currently Light-only.
- UI Font Size has the clearest product-wide effect.
- Code Font Size and line-number preferences are stored but not dynamically consumed by every surface.
- Use Settings > Database to add a connection, test it, and save it before opening deeper modules.
- Use Settings > AI / LLM > Providers to add one stable default provider before changing prompt rules or advanced temperatures.
- Use Settings > Access Licensing to confirm trial or licensed state and configure local app lock when the machine needs local access protection.
- Use Settings > General only after first successful use if you need module visibility changes or Query Statistics threshold tuning.
- Keep one stable default AI provider instead of rotating defaults frequently.
- Use descriptive names for connection profiles and provider definitions.
- Change Query Analysis thresholds gradually and validate the result in Query Statistics.
- Use Tuning Memory as an operator review log, not as an automatic truth source.
- Keep encryption enabled for SQL connections unless your environment requires an exception.
- Treat local app-lock credentials as real machine-level access controls.
Use Installation for first-run onboarding and SQL prerequisites, Quickstart for the shortest path to a working setup, and Overview for product positioning before making environment-specific configuration choices.