Our primary SQL Server experienced a “non yielding scheduler” and wrote a 234 GB memory dump to disk before restarting. During this time all sites were offline. After the crash dump completed SQL was able to start without issue. We will continue to monitor the server and have plans to switch all of our sites back over to NY this weekend which are running on fully patched SQL 2012 instances. Stay tuned…