Tips & Troubleshooting — Script Runner
FAQ & tips
- Always Validate on write scripts before Execute — especially with parallel mode.
- GO batches matter: Script Runner splits on GO; keep DDL and dependent DML in sensible order.
- Credentials are stored with Windows DPAPI protection on the local machine — treat exported registration files as sensitive.
- Prefer read-only inventory scripts in parallel; use serial + stop-on-error for schema migrations.
Data Storage & Security
| Item | Details |
|---|---|
| Server groups file | %LOCALAPPDATA%\DBLenseScriptRunner\servergroups.json |
| Templates file | %LOCALAPPDATA%\DBLenseScriptRunner\templates.json |
| Settings file | %LOCALAPPDATA%\DBLenseScriptRunner\settings.json |
| Password encryption | Windows DPAPI (CurrentUser scope) — cannot be shared between users/machines |
| Auto-save | Every group/server change persisted immediately |
| Crash logs | %LOCALAPPDATA%\DBLenseScriptRunner\CrashLogs\ |
| No telemetry | No operational data sent externally. License/update checks use dblense.com. |
System Requirements
| Component | Requirement |
|---|---|
| OS | Windows 10/11 or Windows Server 2016+ |
| Runtime | .NET 8.0 (included in self-contained package) |
| SQL Server | SQL Server 2012+ (any edition including Express) |
| Azure | Azure SQL Database, Azure SQL Managed Instance |
| Installation | None → single portable .exe, no admin rights required |