I whined about this recently on Facebook. After that, I did something practical: I searched for a solution.
I found a workaround at Connect:
Open SSMS
Select "Tools", "Customize…"
– Click "Keyboard…"
– In the list window, scroll down and select "Window.ShowResultsPane"
– Under "Use new shortcut in:", select "SQL Query Editor"
– Place your cursor in the "Press shortcut keys:" input area and press Ctrl+R
– Click "Assign", then "OK".
Tested and approved.
:{>
Hey, I blogged about this. 🙂
http://sqlblog.com/blogs/aaron_bertrand/archive/2011/07/14/sql-server-v-next-denali-getting-ctrl-r-to-work-again.aspx
Thanks for the great help, I was facing this issue from long time.
There is no problem when I open SSMS, but when I used to open SSMS as a different user the Ctrl+R combination didn’t used to work.
Now after going by the steps you provided it is working perfectly.
Thanks!
SQLwithManoj.wordpress.com
I noticed this on a co-worker’s machine yesterday. Drove me nuts. A lot of his key bindings are weird (and wrong… for me at least).
The main difference is that I do a fresh install of Windows every 18-24 months. I start at SQL 2005 and work upwards to SQL vCurrent. My current laptop was set up before SQL 2012 was out. So I had 2008 R2 keybindings in 2008 R2’s SSMS.
They came through to 2012’s SSMS when it first ran. This obviously doesn’t happen if there’s no version prior to 2012 already installed.
Thanks for the tip – if it was my workstation I’d be straight into mucking with the keybindings!
What’s more annoying in later versions of BIDS is that things like tab stops, etc in the reporting services expression editor window are mucked up. I can’t drive all of it with just the keyboard anymore and need to mouse+keyboard on most dialogs…. Frustrating! So I stick with BIDS 2008 R2 🙂