在SSMS Microsoft SQL Server Management Studio中显示已损坏的重复滚动条

时间:2021-01-16 10:36:59

Microsoft SQL Server Management Studio (SSMS) corrupts the display results and query window in both versions 2005 and 2008 as shown in the screenshot. It seems like the window drawing / re-drawing display system repeats the scroll bars and does not draw / re-draw the content areas. This occurs on Windows 7 x64 on both a 2-monitor setup on a workstation and on a laptop.

Microsoft SQL Server Management Studio(SSMS)会破坏2005和2008版本中的显示结果和查询窗口,如屏幕截图所示。看起来窗口绘制/重绘图显示系统重复滚动条并且不绘制/重新绘制内容区域。这在Windows 7 x64上发生在工作站和笔记本电脑上的双显示器设置上。

UPDATE Q1 2011: MS has tagged this with "Active" on its issue tracker at MS Connect.

更新2011年第一季度:MS已在MS Connect的问题跟踪器上标记为“Active”。

UPDATE Q2 2011: Bug reproduced on NVidia (2) and Radeon hardware

更新2011年第二季度:在NVidia(2)和Radeon硬件上再现了Bug

A few add-ons such as Tabs Studio and a few screen capture utilities are in use, but the behavior persists even if these are disabled and/or unloaded and on reboot.

一些附加组件(如Tabs Studio和一些屏幕捕获实用程序)正在使用中,但即使在禁用和/或卸载以及重新启动时,行为仍然存在。

My question is if this is caused by something that is within my control and how the behavior may be fixed. In the meantime I am using Linqpad (wonderful) but we still need to use SSMS for a number of reasons and this is driving us nuts.

我的问题是,这是否是由我控制范围内的事情以及如何修复行为引起的。与此同时,我正在使用Linqpad(很棒)但我们仍然需要使用SSMS有很多原因,这让我们感到疯狂。

At least one other person has had this happen and has posted on MS's connect site, but it has not be resolved or address by MS as far as I can tell.

至少有一个人已经发生这种情况,并已发布在MS的连接网站上,但据我所知,它尚未被MS解决或解决。

在SSMS Microsoft SQL Server Management Studio中显示已损坏的重复滚动条

3 个解决方案

#1


2  

It's an identified bug in SSMS per http://connect.microsoft.com/SQLServer/feedback/details/533311/display-corruption-on-ssms-at-large-resolutions-on-second-screen

根据http://connect.microsoft.com/SQLServer/feedback/details/533311/display-corruption-on-ssms-at-large-resolutions-on-second-screen,这是SSMS中发现的错误

No workarounds have been identified.

没有找到解决方法。

#2


2  

I had this issue as well (SSMS 2008 R2, Win 7 64 bit, 3 screens, NVIDIA Quadro NVS 420).

我也有这个问题(SSMS 2008 R2,Win 7 64位,3屏,NVIDIA Quadro NVS 420)。

The workaround that fixed the problem for me was was to change the 'Compatibility Settings' for Ssms.exe. Check the Setting: 'Disable display scaling on high DPI settings'.

为我解决问题的解决方法是更改​​Ssms.exe的“兼容性设置”。检查设置:'在高DPI设置下禁用显示缩放'。

Screenshot here: http://imgur.com/uONK7

屏幕截图:http://imgur.com/uONK7

Next time SSMS opened, no more annoying scrolling bugs.

下次SSMS打开时,没有更烦人的滚动错误。

#3


0  

I also had the same problem in SSMS2008R2. A quick fix is to drag a Splitter between ObjectExplorer and SQLEditor. SSMS re-paints itself then and display is at least correct. Works with about 75% probability. :)

我在SSMS2008R2中也遇到了同样的问题。快速解决方法是在ObjectExplorer和SQLEditor之间拖动Splitter。然后SSMS重新涂漆,显示至少是正确的。工作概率约为75%。 :)

#1


2  

It's an identified bug in SSMS per http://connect.microsoft.com/SQLServer/feedback/details/533311/display-corruption-on-ssms-at-large-resolutions-on-second-screen

根据http://connect.microsoft.com/SQLServer/feedback/details/533311/display-corruption-on-ssms-at-large-resolutions-on-second-screen,这是SSMS中发现的错误

No workarounds have been identified.

没有找到解决方法。

#2


2  

I had this issue as well (SSMS 2008 R2, Win 7 64 bit, 3 screens, NVIDIA Quadro NVS 420).

我也有这个问题(SSMS 2008 R2,Win 7 64位,3屏,NVIDIA Quadro NVS 420)。

The workaround that fixed the problem for me was was to change the 'Compatibility Settings' for Ssms.exe. Check the Setting: 'Disable display scaling on high DPI settings'.

为我解决问题的解决方法是更改​​Ssms.exe的“兼容性设置”。检查设置:'在高DPI设置下禁用显示缩放'。

Screenshot here: http://imgur.com/uONK7

屏幕截图:http://imgur.com/uONK7

Next time SSMS opened, no more annoying scrolling bugs.

下次SSMS打开时,没有更烦人的滚动错误。

#3


0  

I also had the same problem in SSMS2008R2. A quick fix is to drag a Splitter between ObjectExplorer and SQLEditor. SSMS re-paints itself then and display is at least correct. Works with about 75% probability. :)

我在SSMS2008R2中也遇到了同样的问题。快速解决方法是在ObjectExplorer和SQLEditor之间拖动Splitter。然后SSMS重新涂漆,显示至少是正确的。工作概率约为75%。 :)