A new version of SSMS was released a few days ago. It jumped from 17.9 to 18.0. Nothing too different, but is probably worth upgrading during lunch or something in the next few weeks.
On my VDI, the SSMS installation broken my SQL Server ODBC Driver (version 17). I frogot to copy the error message, but it bubbled up from nanodbc, which is the C++ library underneath the odbc R package. Uninstalling and reinstalling the ODBC driver fixed everything. The DSNs didn't even need to be recreated.
@thomasnwilson @DavidBard @genevamarshall @caston60 @yutiantang @ARPeters @vimleshbavadiya @athumann
A new version of SSMS was released a few days ago. It jumped from 17.9 to 18.0. Nothing too different, but is probably worth upgrading during lunch or something in the next few weeks.
On my VDI, the SSMS installation broken my SQL Server ODBC Driver (version 17). I frogot to copy the error message, but it bubbled up from
nanodbc, which is the C++ library underneath theodbcR package. Uninstalling and reinstalling the ODBC driver fixed everything. The DSNs didn't even need to be recreated.