-
Notifications
You must be signed in to change notification settings - Fork 2
Application Settings
The Settings panel in SQLSkrypter allows you to customize the behavior of the application, improve safety, and optimize workflow.
This chapter describes all major configuration options available in the Main Settings Window.
Toast notifications appear in the bottom‑right corner of the screen and inform you about:
- completed executions
- errors
- warnings
- update availability
- background operations
Recommended: Enabled
They provide quick feedback without interrupting your workflow.
When enabled, SQLSkrypter automatically checks for new versions on startup.
- If an update is available, a notification appears.
- Updates are optional — you choose when to install them.
Recommended: Enabled
Ensures you always have the latest features and security improvements.
Controls whether SQLSkrypter remembers:
- excluded databases
- exclusion rules
- hidden system databases
When enabled, exclusions persist across sessions.
Recommended: Enabled
Prevents clutter and accidental deployments to unwanted databases.
Determines whether SQLSkrypter executes scripts:
- In parallel — faster, ideal for large fleets
- Sequentially — slower, but easier to debug
Parallel execution is safe and significantly improves performance.
Recommended: Enabled
Unless you need strict sequential order for debugging.
Choose which workspace opens by default:
- Script Editor
- Script Files Mode
Useful if you primarily work with update packages or ad‑hoc SQL.
When enabled, SQLSkrypter asks for confirmation before closing the application.
This prevents accidental shutdowns during:
- active deployments
- editing scripts
- preparing update packages
Recommended: Enabled
Allows switching the UI language.
Available languages:
- English
- Polish
Changing the language updates:
- labels
- tooltips
- menus
- dialogs
Defines the maximum allowed execution time for SQL commands (in seconds).
Useful for:
- long‑running maintenance scripts
- heavy reporting queries
- operations on large datasets
Default: 30 seconds
Recommended: Increase to 60–120 seconds for production deployments.
| Setting | Recommended | Reason |
|---|---|---|
| Toast Notifications | ✔ | Quick feedback |
| Auto‑Updates | ✔ | Latest features & fixes |
| Remember Exclusions | ✔ | Cleaner explorer |
| Parallel Execution | ✔ | Faster deployments |
| Confirm on Exit | ✔ | Prevents accidental closure |
| SQL Timeout | 60–120s | More stable deployments |
Next:
➡️ Security and Encryption