- Download SQLTriage from GitHub Releases
- Run the installer or extract the ZIP
- Launch SQLTriage
- Complete the onboarding wizard
- Go to Servers page
- Click Add Server
- Enter your SQL Server instance name (e.g.,
SERVERNAMEorSERVERNAME\INSTANCENAME) - Enter credentials if not using Windows Authentication
- Click Test Connection
- Click Save
- Live Monitor (
Ctrl+2): Real-time sessions, wait stats, blocking chains - Quick Check (
Ctrl+Q): 30-second health snapshot - Full Audit: Comprehensive diagnostic scripts
Q: Why is my alert firing constantly?
A: Alerts use IQR (Interquartile Range) baselines that learn your server's normal behavior over time. If you're seeing constant alerts:
- Check the Alerting → Alert History page to see what's triggering
- Adjust the alert threshold in Settings → Alerting
- Use the "dry-run mode" in alert configuration to test without notifications
- The baseline adapts automatically, but you can reset it in Alerting → Baselines
Q: How do I adjust the alert delay?
A: In Settings → Alerting, set NextAlertDelayMinutes to prevent alert spam. This creates a cooldown period after each alert fires.
Q: Is SQLWATCH required?
A: No, SQLWATCH is optional. Most features work without it:
- Live Monitor: Works without SQLWATCH
- Quick Check: Works without SQLWATCH
- Full Audit: Works without SQLWATCH
- Historical dashboards: Requires SQLWATCH for trend data
To enable historical data, deploy SQLWATCH via the Database Deploy page.
Q: How do I run SQLTriage as a Windows Service?
A: During installation, check "Install Windows Service". Or manually:
- Open command prompt as Administrator
- Navigate to SQLTriage installation folder
- Run:
SQLTriage.exe --install-service - Start the service:
net start SQLTriage - Access via browser at
http://localhost:5000(default port)
The service runs headless with web access for remote monitoring.
Q: How do I migrate credentials between machines?
A: Use the credential export/import feature:
- Go to Settings → Server Credentials
- Click Export Credentials
- Save the
.lmcredsfile (PBKDF2 encrypted) - On the new machine, click Import Credentials
- Enter the passphrase to decrypt
This securely transfers all server connections.
Q: Where are the log files located?
A: Logs are in logs/app-YYYYMMDD.log next to the SQLTriage.exe file.
For debugging:
- Enable debug logging in Settings → General
- Check the log file for detailed error information
- Include relevant log entries when reporting issues
- Documentation: Full docs
- Issues: Report bugs
- Discussions: Community help
- Report a Bug: Bug report template
- Explore the Environment View for topology visualization
- Set up Alerting for automated notifications
- Run Vulnerability Assessment for security checks
- Configure Dashboard Editor for custom layouts QUICKSTART.md