We are seeing an error on SQL logs on MSSQL8 that looks like a reboot would be best to resolve, we are doing this now.
