Home Dashboard Directory Help
Search

CTRL + L is no longer working for Estimated Execution Plans by ArvindRavish


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 737745
Opened: 4/19/2012 11:08:00 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

CTRL + L keyboard shortcut used to bring up estimated execution plans. But it is now broken in SQL Server 2012. It is not only this, many other keyboard shortcuts no longer function in SSMS 2012.
Details
Sign in to post a comment.
Posted by Brad_Schulz on 9/20/2013 at 1:02 PM
Hah!

Naturally I figured it out how to fix the problem right after I posted it.

I had to go into Tools -> Options -> Environment -> Keyboard and go to Edit.LineCut (not Edit.Cut) and REMOVE the CTRL+L definitions for the DataWarehouse Designer scope and the Text Editor scope.

Sheesh... wouldn't you think that my Global-scope CTRL+L would have overriden those? I guess not.

Anyway, problem solved.
Posted by Brad_Schulz on 9/20/2013 at 12:55 PM
I am having the same problem.

In SQL2012 SSMS (Version 11.0.3128.0) my CTRL+L does NOT show an estimated execution plan. Instead, it's taking on the "usual" Visual Studio behavior of acting like a CTRL+X (i.e. it's cutting whatever is highlighted or cuts the entire line I'm on in the editor if nothing is highlighted).

I've gone to Tools -> Options -> Environment -> Keyboard and I've ensured that only CTRL+X is defined for Edit.Cut and that CTRL+L is defined for Query.DisplayEstimatedExecutionPlan. They are. I've even tried reassigning them as a user preference (with the same definitions), and that still doesn't work.

I've exported the settings and examined the resulting file and I see the correct CTRL+L and CTRL+X settings in there, but SSMS is just ignoring the CTRL+L definition. It continues to cut text in the editor instead of displaying the estimated plan.
Posted by Microsoft on 11/13/2012 at 2:38 PM
Hi there Arvind
Thanks for contacting us. We were not able to reproduce this issue here. There are two things I can think of to try:
1) Reset your settings (From the menu: Tools -> Import and Export Settings…) , then restart SSMS
2) Manually set your settings back to what you want from the menu: tools > Options > Environment > Keyboard

Hope this helps,
-Sam
Posted by Steven Wang - Shangzhou on 4/19/2012 at 2:25 PM
Hi Arvind,

Very insteresting, as it is working perfectly for me.

I'm using the SQL server 2012 RTM version. Enterprise edition.
Sign in to post a workaround.