sync: auto-sync from HOWARD-HOME at 2026-05-06 13:50:24

Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-05-06 13:50:24
This commit is contained in:
2026-05-06 13:50:25 -07:00
parent 17f0d0becb
commit d5bf06ab9a
3 changed files with 3 additions and 3 deletions

View File

@@ -123,7 +123,7 @@ GuruRMM command_id for audit: `1889a150-b775-4fb2-9f4b-cd794d4e7d9f`, exit 0.
- WID: 512 MB
- AIMSQL: 256 MB (or just leave it; we want it stopped eventually anyway)
The cap stops the trim cycle even when global pressure rises, because SQL voluntarily stays under the ceiling instead of getting forcibly trimmed.
2. **Confirm Station 1's hostname / IP** with Leslie. None of the active SQLEXPRESS sessions matched `IMC-STATION1` exactly. Likely either `DESKTOP-44L80C0` / `DESKTOP-MR3ALTK` (un-renamed boxes) or a station that was disconnected at check time.
2. ~~**Confirm Station 1's hostname / IP** with Leslie. None of the active SQLEXPRESS sessions matched `IMC-STATION1` exactly. Likely either `DESKTOP-44L80C0` / `DESKTOP-MR3ALTK` (un-renamed boxes) or a station that was disconnected at check time.~~ **Resolved 2026-05-06 by Howard:** Station 1 = `IMC-STATION1`, IP **192.168.0.50**. It wasn't in the active connection list at enumeration time — consistent with it being disconnected after the user-facing error and not yet reconnected at our snapshot. For next recurrence, target diagnostics by `client_net_address = '192.168.0.50'` in `sys.dm_exec_sessions` and by remote IP in SQLEXPRESS connection events.
3. **Locate AIMSQL `.mdf` files** before any consolidation talk. They weren't where I expected. Worth a 5-minute filesystem search.
4. **Schedule SQLEXPRESS-targeted restart cadence** only if the memory cap doesn't hold — but it's after-hours-only because every register would briefly disconnect.