Henry Wyckoff

My feedback

  1. 19 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    18 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    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.

    -Matteo

    Henry Wyckoff commented  · 

    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.

    Henry Wyckoff commented  · 
    Henry Wyckoff supported this idea  · 
  2. 162 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  15 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Henry Wyckoff supported this idea  · 
  3. 168 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  8 comments  ·  SQL Server » Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Henry Wyckoff commented  · 

    "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.

    Henry Wyckoff supported this idea  · 
  4. 4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Henry Wyckoff shared this idea  · 

Feedback and Knowledge Base