April 17, 2015 at 8:22 am
My workplace is getting ready to upgrade to SQL 2012. While I wait for the servers to be built, I started playing with 2012 SSMS pointing to our SQL 2008 databases. It seems to me that both Intellisense and the Object Explorer Details window are incredibly slow to load and react to the mouse.
Has anyone else noticed this behavior? I'm on a Windows 7 machine (don't know if that makes a difference).
April 17, 2015 at 8:57 am
I really dislike the native intellisense, so...
I haven't seen major slow downs, but, make sure you have the latest SP and maybe the latest CU installed on top of your SSMS, even if you don't have SQL Server locally. That's what upgrades the GUI.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
April 17, 2015 at 8:59 am
Actually I installed my own copy of Dev edition 2012 on my PC, so I have it all. I'll go out and look for an upgrade.
Thanks, Grant.
April 19, 2015 at 6:44 am
Brandie Tarvin (4/17/2015)
My workplace is getting ready to upgrade to SQL 2012. While I wait for the servers to be built, I started playing with 2012 SSMS pointing to our SQL 2008 databases. It seems to me that both Intellisense and the Object Explorer Details window are incredibly slow to load and react to the mouse.Has anyone else noticed this behavior? I'm on a Windows 7 machine (don't know if that makes a difference).
Get less of this these days with SSMS 2014 but still happens, remedy being forcing the reload (CTRL+SHIFT+R) every time one connects to a database.
😎
April 19, 2015 at 3:37 pm
Brandie Tarvin (4/17/2015)
My workplace is getting ready to upgrade to SQL 2012. While I wait for the servers to be built, I started playing with 2012 SSMS pointing to our SQL 2008 databases. It seems to me that both Intellisense and the Object Explorer Details window are incredibly slow to load and react to the mouse.Has anyone else noticed this behavior? I'm on a Windows 7 machine (don't know if that makes a difference).
Yes. Just one of many problems with 2012 SSMS. I've had it "freeze" for minutes at a time. It's the worst rendition of the product I've seen yet. It also doesn't allow the scroll-wheel on many of the pulldowns and windows, requires that you setup coloring not in one place but two places (Green for Dev, Blue for Staging, Orange for UAT, Red for Prod is what I usually use), doesn't automatically update Intellisense when you add a table (you have to press {Ctrl}{Shift}{R} to do the refresh), usually doesn't register on #TempTables, etc, etc, etc. That's even on SP2 CU5, which came out mid-March.
Rumor has it that all support and changes for 2005 are going out of scope in a year on extended support. That's good. That means that 2005 will actually be a stable product with no chance of a future change mucking up the works. 😛
--Jeff Moden
Change is inevitable... Change for the better is not.
April 20, 2015 at 4:27 am
In other words, applying the post SP1 CU3 pack isn't going to fix the issue.
Happy Happy Joy Joy.
Thanks, all.
April 20, 2015 at 9:37 am
Brandie Tarvin (4/20/2015)
In other words, applying the post SP1 CU3 pack isn't going to fix the issue.Happy Happy Joy Joy.
Thanks, all.
True dat! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
April 20, 2015 at 9:42 am
BAH. I tried applying the CU anyway and got an error response that there were no instances to apply it against.
Sometimes SQL is so damn frustrating.
April 20, 2015 at 9:54 am
I can't say that I think SSMS 2012 is better/worse than 2008/2014. Still a pig and slow, and randomly crashes on me.
At least a few more of the dialogs fit my screens better (and more in 2014), but definitely still issues.
April 20, 2015 at 1:47 pm
We are just beginning to see a few SQL2012s here. I noticed that SSMS for 2012 loads slower than 2005, 2008, 2008R2 as well.
April 20, 2015 at 1:55 pm
We have also been fighting this issue.
We notice it more when clicking from one "folder" to another. Such as procs to tables, databases to management, server to another server.
Some of us have started opening multiple copies of SSMS for each function we are performing.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
April 20, 2015 at 2:00 pm
One thing I forgot to mention is the database restore GUI... you click into it and it freezes and hangs for about 30 seconds about 9 out of 10 times.
April 21, 2015 at 4:35 am
Yeah, just waiting for the connection window to come up when I click Connect in Object Explorer is an exercise in patience.
April 21, 2015 at 8:52 am
I've 2 windows 7 machines - a desktop and a laptop. On the desktop I have SSMS 2012 and the laptop as 2008 R2. I've found that the 2012 version is slower to open (though that may be more the computer than the application) and occasionally it will lose the list of server names that I've connected to. I would love to figure out the trigger for that one because it's annoying as anything.
April 21, 2015 at 9:12 am
LightVader (4/21/2015)
I've 2 windows 7 machines - a desktop and a laptop. On the desktop I have SSMS 2012 and the laptop as 2008 R2. I've found that the 2012 version is slower to open (though that may be more the computer than the application) and occasionally it will lose the list of server names that I've connected to. I would love to figure out the trigger for that one because it's annoying as anything.
SQL 2008 also loses the list of server names and all my non-default options that I set up. I have found that it usually happens after an update to SQL Server or when my machine crashes or when SSMS crashes. Rarely it happens after a specific windows update.
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply