Could you check if “C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\1033\Microsoft.DataWarehouse.VsIntegration.rll” is missing from your machine?
If it is, you may try two things (either one) to alleviate the pain:
1) Locate ssms.pkgundef (typically at “C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\ssms.pkgundef”)
Edit it and add a line line this at the bottom:
[$RootKey$\FontAndColors\Data Warehouse Designer]
2) Grab the missing file from a machine running the same version of SSMS (it could be a temporary VM with just that binary)
It would be helpful if somebody could share (OneDrive or equivalent) the content of the TEMP\SSMSSetup folder (that’s the history of the SSMS setup): it may reveal useful info for us.
Note: there may be sensitive information in those log files (machine names, path names, etc…), so use your best judgement.
Option 1 worked for me. I used Notepad++ in admin mode to add the one line. Closed SSMS and reopened. Now I can see the full list of font options.
Same problem here. I tried the steps shown here (https://docs.microsoft.com/en-us/sql/ssms/sql-server-management-studio-changelog-ssms?view=sql-server-2017#uninstall-and-reinstall-ssms-17x) and the symptom did not go away.
"The SSDT team doesn't respond quickly enough" -- I'd argue that the SSDT team doesn't respond at all. Their official blog hasn't been touched since April 2017 and they have been completely radio-silent for over a year.
4 votesHenry Wyckoff shared this idea ·