SecurityInsight settings · Settings > Sign-in & Azure resources
Pro database size
| Key | SI_Bootstrap_SqlServiceObjective |
|---|---|
| Where | Settings > Sign-in & Azure resources |
| Type | Text |
| Default | Empty: the product's rule -- Standard S3 for every install, raised to it when smaller, never lowered. |
| Edition | pro |
What it does
The size (Azure SQL service objective) of the Pro database. Allowed values: S1, S2, S3, S4, S6, S7, S9, S12. Empty = the product's rule.
When set
Every update sets the Pro database to this size, raising or LOWERING it, by one online change (no data loss; open connections reconnect once). Never below S1. A database on Premium, vCore or in an elastic pool is left as it is. The identity database is not affected: it stays S1. A smaller size costs less but makes pages and the nightly writes slower.
When blank or default
Left blank, the default applies: Empty: the product's rule -- Standard S3 for every install, raised to it when smaller, never lowered.
Risk and how to reverse it
Affects how the jobs sign in or which Azure resources they use. A wrong value stops the affected jobs at their next run (nothing is changed or deleted); a broader identity or right gives the jobs more access than they need. Reversible: correct it and run again.
Requires
A SecurityInsight Pro licence.
Recommended
Keep the default. Change it when: Only when support advises it -- for example S2 for a small install whose database is mostly idle.
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack