SQLBrander.com B.V.

How to fix scaling issues in SQL Server Management Studio on 4k or other high density displays.

Many thanks to SpaghettiDBA (Gianluca Sartori). He wrote about this on SQLServerCentral.com: http://www.sqlservercentral.com/blogs/spaghettidba/2015/10/14/ssms-in-high-dpi-displays-how-to-stop-the-madness/

Sadly enough Microsoft sees this as a non issue for us and won’t fix this issue. (https://connect.microsoft.com/SQLServer/feedback/details/764009/ssms-does-not-display-properly-in-high-dpi). Many more High DPI displays will occur in the future.

In short how to fix this in four easy steps:

1) Create [SSMSDPISCALING.reg] file as per example below
2) Create [Ssms.exe.manifest] file as per example below
3) Double-click on [SSMSDPISCALING.reg] to enter a key into the registry
4) Copy [Ssms.exe.manifest] file to “C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio” folder
    (Replace 120 by 130, 110, 105 or 100 if using another version of SSMS than SQL 2014)

I have tested this work around with SQL Server 2014 and SQL Server 2016 Management Studio Versions on Windows 10

Reg file [SSMSDPISCALING.reg] contains:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide]
“PreferExternalManifest”=dword:00000001

Manifest file [Ssms.exe.manifest] contains:
<?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes”?>

<assembly xmlns=”urn:schemas-microsoft-com:asm.v1″ manifestVersion=”1.0″ xmlns:asmv3=”urn:schemas-microsoft-com:asm.v3″>

<dependency>
  <dependentAssembly>
    <assemblyIdentity type=”win32″ name=”Microsoft.Windows.Common-Controls” version=”6.0.0.0″ processorArchitecture=”*” publicKeyToken=”6595b64144ccf1df” language=”*”>
    </assemblyIdentity>
  </dependentAssembly>
</dependency>

<dependency>
  <dependentAssembly>
    <assemblyIdentity type=”win32″ name=”Microsoft.VC90.CRT” version=”9.0.21022.8″ processorArchitecture=”amd64″ publicKeyToken=”1fc8b3b9a1e18e3b”>
    </assemblyIdentity>
  </dependentAssembly>
</dependency>

<trustInfo xmlns=”urn:schemas-microsoft-com:asm.v3″>
  <security>
    <requestedPrivileges>
      <requestedExecutionLevel level=”asInvoker” uiAccess=”false”/>
    </requestedPrivileges>
  </security>
</trustInfo>

<asmv3:application>
  <asmv3:windowsSettings xmlns=”
http://schemas.microsoft.com/SMI/2005/WindowsSettings”>
    <ms_windowsSettings:dpiAware xmlns:ms_windowsSettings=”
http://schemas.microsoft.com/SMI/2005/WindowsSettings”>false</ms_windowsSettings:dpiAware>
  </asmv3:windowsSettings>
</asmv3:application>

</assembly>

On the first of April the Release Candidate 2 was released of Microsofts database product SQL Server 2016. More information on the blog:

The Release Candidates are following up much faster which seems to me an indication that the RTM release won’t be far away (no guarantees of course).

Important improvements:

  • R Services setup – the setup process for R Services is much more integrated into SQL Server setup. There is no longer a need to manually download and install Microsoft R open and R Server if the SQL Server is connected to the Internet; it becomes part of the SQL Server install sequence.
  • SQL Server Management Studio (SSMS) – This release of SSMS features an update to the Visual Studio 2015 shell bringing enhancements such as the quick launch toolbar and improved theming support.
  • Mobile reports – Brand Packages will now be downloaded to the mobile report publisher from a server running RC2 and available for use in report creation.  Basic mobile report content migration between servers is now supported.

For additional information about RC 2, see SQL Server 2016 Release Notes, What’s New for SQL Server R Services and the SSMS RC 2 blog post.

Download available from MSDN (subscription needed) or Evaluation Center download (registration needed).