Docs/Installation

Installation

Install the Windows desktop app, complete first-run onboarding, prepare SQL Server permissions, enable Query Store, and configure Database plus AI / LLM settings.

Getting Started

Overview Installation Quickstart Settings

Modules

Dashboard Query Statistics Index Advisor Blocking Analysis Wait Statistics Security Audit Scheduled Jobs Object Explorer

Installation Path

SQL Performance Intelligence installation is complete only when the desktop app launches, the first-run onboarding finishes, the SQL connection succeeds, and the AI / LLM provider is ready for use.

If you want the product overview before setup, read the overview. If installation is already done and you only need the first working usage flow, jump to the quickstart guide.

Install the Windows desktop application.
Accept the license agreement on first launch.
Create the local application access profile with name, company, email, and password.
Start the 30-day full trial automatically.
Add a database connection in Settings > Database.
Add an AI model in Settings > AI / LLM.

# Example silent install
msiexec /i "SQL Performance Intelligence.msi" /quiet /norestart

Use silent installation for managed enterprise rollout. Most users should use the normal interactive Windows installer.

Search Summary

This installation guide covers SQL Performance Intelligence first-run onboarding, SQL Server application login requirements, Query Store enablement, database connection setup, and AI / LLM configuration.

Before You Install

Gather the environment details first. Most failed onboarding attempts come from incomplete connection inputs, not from the installer itself.

A reachable SQL Server host or instance name
The correct SQL port if it is not 1433
A dedicated application SQL login or approved Windows account
A target database name
A DBA contact for permissions or Query Store changes
A decision on local or cloud AI / LLM usage

Step 1

Accept the License Agreement

On the first launch, the application opens the License Agreement. Review the terms, check the acceptance box, and continue. This is the first required step before any local setup or trial activation begins.

The first-run flow begins with the License Agreement.

Step 2

Create the Initial Access Profile

After accepting the license, enter the Full Name, Company Name, Email Address, and the Application Password. This password protects local access to the application on that machine and should be retained by the user or admin who owns the installation.

Initial Access Setup creates the local application user and password.

Step 3

Start the 30-Day Full Trial

Once the identity and password are saved, the application starts the 30-day full trial automatically. No extra activation code, registration form, or online license step is required for the trial. The next guidance directs the user to add a database connection and then an AI model.

The trial starts automatically and points the user to the next setup steps.

Step 4: Add Your First SQL Server Connection

After onboarding, the application routes the user to Settings > Database. Add the first saved SQL Server connection profile there. Use the dedicated application login or approved Windows account prepared by the DBA, not a personal elevated admin account.

Enter the SQL Server host or instance name.
Set the port if your environment does not use the default.
Choose SQL Authentication or Windows Authentication.
Select the target database.
Click Test Connection before Save.
Prefer development, sandbox, or staging before production review.

Step 5: Add Your AI / LLM Provider

Next, open Settings > AI / LLM and add at least one provider. The application supports local and cloud-backed configurations. For a simple first run, add one stable model, test it, and keep it as the default.

Use Ollama for local-only model traffic.
Use OpenAI, Azure OpenAI, Anthropic, or DeepSeek for managed cloud access.
Enter the provider-specific API key, endpoint, or deployment fields exactly.
Run Test before Add.
Save Settings after the provider is added successfully.

Step 6: Validate That Installation Is Complete

The installation is operational when the onboarding flow is finished, the SQL connection works, the AI model test succeeds, and at least one real analysis screen refreshes successfully. After that, continue with the Quickstart guide for the first investigation workflow.

Application launches successfully
License Agreement and Initial Access Setup complete successfully
30-day full trial message appears
At least one saved connection exists
Connection test passes
One AI model test passes
Dashboard refresh works after connection is active

Recommended SQL Server Permissions

Create a dedicated application SQL login or use an approved mapped Windows account with only the visibility required by the product. Exact requirements vary by module, but this read-only baseline gives the best first-run experience without granting data-changing rights.

What The DBA Should Grant

CONNECT
VIEW SERVER STATE
VIEW DATABASE STATE
VIEW DEFINITION
Relevant system DMV and catalog visibility

What Not To Grant

No db_owner
No INSERT, UPDATE, or DELETE
No SQL Agent start or stop rights for onboarding
No broad business-table access unless your policy explicitly requires it

-- Example: create a dedicated application login
CREATE LOGIN [SQLPerformanceApp] WITH PASSWORD = 'ChangeThisStrongPassword!';
GRANT VIEW SERVER STATE TO [SQLPerformanceApp];

USE [YourDatabase];
CREATE USER [SQLPerformanceApp] FOR LOGIN [SQLPerformanceApp];
GRANT CONNECT TO [SQLPerformanceApp];
GRANT VIEW DATABASE STATE TO [SQLPerformanceApp];
GRANT VIEW DEFINITION TO [SQLPerformanceApp];

USE [msdb];
CREATE USER [SQLPerformanceApp] FOR LOGIN [SQLPerformanceApp];
GRANT SELECT ON dbo.sysjobs TO [SQLPerformanceApp];
GRANT SELECT ON dbo.sysjobactivity TO [SQLPerformanceApp];
GRANT SELECT ON dbo.sysjobhistory TO [SQLPerformanceApp];

Query Store Preparation

Query Store is not mandatory for basic use, but it materially improves historical analysis quality for Query Statistics, Index Advisor, and regression-oriented workflows.

Check the target database first and enable Query Store if it is currently off.
Enable it per database, not once for the entire instance.
Use READ_WRITE mode so history continues to accumulate.
Keep QUERY_CAPTURE_MODE = AUTO as the practical default starting point.
Enable wait-stat capture too if your SQL Server version supports it.

ALTER DATABASE [YourDatabase] SET QUERY_STORE = ON;
ALTER DATABASE [YourDatabase] SET QUERY_STORE (
    OPERATION_MODE = READ_WRITE,
    QUERY_CAPTURE_MODE = AUTO,
    CLEANUP_POLICY = (STALE_QUERY_THRESHOLD_DAYS = 30),
    DATA_FLUSH_INTERVAL_SECONDS = 900,
    INTERVAL_LENGTH_MINUTES = 15,
    MAX_STORAGE_SIZE_MB = 2048,
    SIZE_BASED_CLEANUP_MODE = AUTO
);

-- Optional on supported SQL Server versions:
-- ALTER DATABASE [YourDatabase] SET QUERY_STORE (WAIT_STATS_CAPTURE_MODE = ON);

What Happens If Permissions Are Incomplete

The application degrades gracefully where possible, but some modules will return partial visibility when the SQL login cannot see the required metadata.

Query Statistics may fall back from Query Store to DMV-based analysis.
Scheduled Jobs can lose some live running-job visibility if msdb access is limited.
Security Audit can return partial findings when server-level visibility is restricted.
Execution-plan and object-definition workflows can be limited if metadata access is incomplete.

Common Installation Issues

Most installation problems come from environment readiness, connection details, or provider configuration, not from the application binary itself.

SQL Server host or instance is unreachable
Login fails because authentication mode or credentials are incorrect
Target database is not visible or not online
Query Store is disabled for the database you expect to analyze
The dedicated application login is missing required permissions
Cloud provider API key, endpoint, or deployment name is incorrect

Back to Docs Download