I do alot of development in addition to writting SQL code and have really gotten hooked on intellisence.  I know that in a perfect world, rules would be followed so all the naming conventions were the same.  As it stands we have multiple naming conventions in place, which makes it very difficult to remember exactly what convention was used for a given database or table.  Also in SQL2000 (probubly 2005 as well), when writing SQL code you had to ensure that you were writing case sensitive code if you wanted SQL server to be able to reuse its execution plans correctly.  Having intellisense helps me get things done right.

However, I have worked in SQL for so long without intelisense that I wouldn't be all that handycapped not to have it.

I haven't taken the time to customize my menus yet so I won't comment on that one.  The one annoying bug I have found so far is in SQL2005's management studio.  It occurs when I open a table, select a column name from the criteria pane, and press tab to move off of the selection.  Management studio freezes for several seconds before a I get a .NET runtime error which asks me if I want to terminate the program or continue with it.  So far I have just told it to ignore the error and continue which has worked fine, however I have tried to cut down on my use of the tab key in this area.  I did try going into SQL Prompts options and disabled the tab key.  This fix didn't work at the time, however I have recently rebooted my computer and can't recreate the problem so maybe it is fixed now.