I just got a new computer at work. Switched from window 10 home to pro, and when I installed SSMS on the new PC the view dependencies windows is not displaying at correct size. The 'Object Dependencies' Window is not listed in the adjustable Fonts and Colors settings. Is there any way to fix this?
Found the issue here
Just override the DPI Scaling in App properties to fix.
Related
I've created a package in VS 2015 which works. However, when I try to deploy it to my 2014 SQL Server the C# Scripts are causing a problem (they are C# 2015).
I've looked all over to try and find how to change the target version, and everywhere says to click on the projects properties, go to to the Configuration Properties tab and change the target under general setting.
Unfortunately I don't have a general settings under the Configuration Properties Tab.
Can anybody tell me what I am missing?
Don't know how you got to the screen in your picture, but you need to do it this way:
Make sure you have an SSIS Package from the Project you want to deploy open in an active window.
In the menu bar: Project > {Your Project Name} Properties...
Should open a dialog like this:
I just installed Microsoft SQL Server Management 2012 and everything works fine
except I get a very strange font and backcolor issue which I have no idea why it's happening.
I have not modified any of the colors so I am very bewildered by it.
Any one have any idea what is causing this:
Check your background setting in Tools --> Options
Sorry for a noob question, but this is driving me nuts!
Some windows are of a disproportionate size in SQL SSMS and I need to reset them. I recently replaced my old development laptop with a new one and I did a fresh install of Windows 10, Visual Studio 2015 Enterprise, and SQL Server 2014 Enterprise. When I initially installed management studio, my laptop's screen resolution was set at 2880x1620 with "Change the size of text, apps, and other items" set to 200%. I've now docked my laptop and adjusted the built-in display to 1920x1080 and 100% and when I start management studio the dialog windows are huge! They're so big in fact that many of the text boxes overlap each other.
Is there any way to reset SMS to factory defaults?
The login window:
The new db window:
The problem you're running into occurs because SSMS has not been optimized for High-DPI displays. You can try the recently released SSMS November preview release that has initial support for High-DPI displays.
I've a problem with SQL Server 2012. I'm running SQL server studio management 2012 and then, after connection to local database I'm trying to add a new query. After click button new query I'm getting wrong window. It's window without upper control panel. What's more main window it's not refreshing. I dunno why. It's refreshing after maximizng window, but not dynamically. I have no idea what's wrong. I've windows 7 64 bit and my version of SQL Studio management is:
Microsoft SQL Server Management Studio 11.0.3128.0
Microsoft Internet Explorer 9.10.9200.16521
Microsoft .NET Framework 4.0.30319.296
Operating System 6.1.7601
I've noticed LOTS of graphical / UI bugs with the 2012 SSMS. Same version (11.0.3128.0).
Guessing you got this resolved by now, but perhaps you just dragged the query window out of the main SSMS window? I never really use this ability since it treats the "popup" windows as modal and always-on-top, which is annoying.
Frequently, when I resize windows, I get vertical black bars. When I stretch the window, it normally clears it up, but sometimes I have to min/maximize it to get it back to normal. Probably a different bug, but Here's a screenshot
I just got a new PC with Windows 7. While editing a WPF window, when I right-click on a control and select Properties, I get the familiar property window docked in the lower-right coner. For some reason, I do not see the lightning bolt button to toggle over to the events. Also, when I double-click on a control, nothing happens.
Has anyone seen this? What can I do?
You need to install VS 2008 SP1 for that feature (and a lot more!).
I manually uninstalled VS 2008 (by uninstalling each component one-by-one as specified in the readme file), then reinstalled it along with SP1, and it's fixed now.