No, the server itself is unusable; something happened and we are no longer able to even remote-desktop to it.
It needs to be rebuilt and the SQL re-installed. Problem is this was initially the "active" node in the cluster configuration.
The SQL instance now resides in the "passive" node, B, but we have no HA for it; if something happens to server B, we have no failover option at the moment.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]