14

I couldn't see the results in grid pane, so I did the following:

Tools > Options > Query Results > Results to Grid 
      > uncheck the "Discard results after execution" check box

But still I couldn't see the results in grid. I even hit the "Reset to Default" button in same window yet no luck

Please shed some light on this.

marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459
Mar1009
  • 721
  • 1
  • 11
  • 27

3 Answers3

40

Location of UI Button on Sql Server Management Studio Toolbar to change the default query output

Check your default "Results To" selected UI element. Make sure it is selected as "Results To Grid".

I ran into this issue and when I looked at the setting under 'Query Result' > 'SQL server' > it was already set as "Results To Grid"

I believe it was when I was trying hot-keys and fat-fingered CTRL+T which changes the results window to "Results To Text"

JukeSpeets
  • 561
  • 5
  • 7
8

Check 'General' tab under 'Query Result' > 'SQL server' to see if the 'Default destination for result' is set to 'Result to Grid'enter image description here

Afshin Amiri
  • 3,438
  • 1
  • 20
  • 21
  • 1
    Tried that too and even restarted SSMS but still not working. – Mar1009 Aug 11 '18 at 15:00
  • 1
    Anyway, that can be checked more easily with the menu: Query / Results To. If this was the case, I think Mar1009 would have at least said that the results were being shown as text or that he was asked to save a file. – Andrew Aug 11 '18 at 15:05
  • I Reset this :options > Keyboard > Reset and restarted it. now worked – Mar1009 Aug 11 '18 at 15:25
  • After making the update open a new query window, then the updates are working – Jay Jul 01 '22 at 07:34
0

After dealing with this issue today in SSMS 2017, and nothing seemed to fix it. I looked at all of the setting listed here and even reset the keyboard as mentioned by Mar1009. I would still only see the records affected. I closed SSMS, and re-opened it and it now works fine. so one of the tips above did help, not sure which one it was, but I'd just like to add that it required me shutting SSMS down and reopening it to see the fix.

Dharman
  • 30,962
  • 25
  • 85
  • 135
DavyMac
  • 49
  • 5