IMC1: Memory allocation approval + AD/WSUS clarification
Approved: - Memory caps: SQLEXPRESS 12GB, WID 512MB, AIMSQL 256MB - AIMSQL consolidation (pending backup) - AD is in use, WSUS is not Howard may proceed with implementation. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,66 @@
|
||||
# IMC1 Memory Allocation Approval - 2026-05-07
|
||||
|
||||
## Decision by Mike Swanson
|
||||
|
||||
**Date:** 2026-05-07
|
||||
**Context:** Response to Howard's IMC1 SQL instance correction and memory pressure investigation
|
||||
|
||||
---
|
||||
|
||||
## Approvals
|
||||
|
||||
### 1. Memory Caps - APPROVED
|
||||
Apply the following `max server memory` caps immediately:
|
||||
- **SQLEXPRESS:** 12 GB (production AIM instance)
|
||||
- **WID:** 512 MB (Windows Internal Database)
|
||||
- **AIMSQL:** 256 MB (orphan instance with test DBs)
|
||||
|
||||
**Rationale:** Prevents memory contention that's causing AIM "connection broken" errors.
|
||||
|
||||
### 2. Infrastructure Clarification
|
||||
- **AD (Active Directory):** Installed and IN USE on IMC1
|
||||
- **WSUS:** NOT in use at IMC1
|
||||
|
||||
**Note on WID:** While WSUS is not used, verify if AD RMS (Active Directory Rights Management Services) is active before stopping WID instance. If AD RMS is also unused, WID can be stopped to free ~300 MB.
|
||||
|
||||
### 3. AIMSQL Consolidation - APPROVED (Pending Backup)
|
||||
Howard may proceed with AIMSQL consolidation once:
|
||||
1. 2023-era test DBs (`AIM`, `IMC`, `TestConv61223`) are backed up
|
||||
2. `.mdf` files are located and confirmed safe to retire
|
||||
3. Howard verifies no applications reference this instance
|
||||
|
||||
### 4. Server Migration Timeline
|
||||
Acknowledged priorities:
|
||||
- **Server 2016 EOL:** 2027-01-12 (extended support ends)
|
||||
- **Dedicated DB Host:** Conversation to be scheduled at next ACG strategy call
|
||||
- **Migration Window:** Finite, needs scoping for cost/timeline
|
||||
|
||||
---
|
||||
|
||||
## Next Steps for Howard
|
||||
|
||||
1. Apply memory caps immediately (reversible change)
|
||||
2. Verify AD RMS usage before stopping WID
|
||||
3. Locate AIMSQL `.mdf` files for backup
|
||||
4. Monitor for AIM error recurrence after memory caps applied
|
||||
5. Prepare migration timeline proposal for next strategy call
|
||||
|
||||
---
|
||||
|
||||
## Additional Responses to Howard's Notes
|
||||
|
||||
### Cascades Tucson - Britney Thompson Litigation Hold
|
||||
Will perform 5-minute Graph check to verify litigation hold status before Wave 1 caregiver rollout. This is a compliance priority.
|
||||
|
||||
### Sombra Residential - Syncro Billing
|
||||
Acknowledged: `billable: false` flag is silently ignored. Correct product selection is mandatory. Memory updated.
|
||||
|
||||
### Post-Transwiz Pattern
|
||||
Good catch on ghost account pattern. Will add "post-Transwiz Office identity sweep" to new-PC checklist.
|
||||
|
||||
### Stamback Septic
|
||||
Confirmed invoice status. Prepay block visibility noted.
|
||||
|
||||
---
|
||||
|
||||
**Status:** Decisions documented, ready for Howard's implementation.
|
||||
Reference in New Issue
Block a user