I am probably speaking out of turn here (it is not Saturday, after all), but I was really annoyed with this SSMS grid problem today, and had to get it off my chest.  I was waiting for a log restore to complete, and periodically running sp_who2 to determine IO completed thus far.  I could have written a query against the DMVs but might have been hit with the same issue.  Essentially, the problem is that the grid alignment in the results pane of SSMS is horrible and often guesses wrong.  What this yields is a lot of data that is obscured by ellipses because SSMS decided that it would make a column 60px wide when 65px would have shown all of the data (and plenty of cases where it makes a column 200px wide when 60px would have been enough).  In this specific case, of course, it was particularly annoying: it consistently obscured only one value in the entire grid: the one I was interested in!

So what did I have to do?  Every time I ran the query to check on the result, I had to drag or double-click on the column header boundary in order to show the whole value.  This is the epitome of annoying.

Now I complained about grid alignment last summer, and due to my frustration today, will likely include a reference to this item in this week's Connect digest.  But in case you want a sneak preview:

#356926 : SSMS : Grid alignment, column width seems arbitrary