During scheduled database maintenance, a lock-intensive database change encountered normal production traffic and created a large queue of waiting requests. This caused database connections and resource usage to rise rapidly, resulting in intermittent application unavailability and disconnections for some connected clients. The initial database change was reverted, which produced partial recovery, but the service later became unstable again as queued and reconnecting workload returned. A database restart provided the clean recovery point that restored stable service.