SQL Server 2008 management studio. Context menu for views - by nickyG

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 414142 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 2/12/2009 1:57:04 PM
Access Restriction Public


A SQL Server 2005 service pack added an 'Edit' menu option to the view context menu. 

To get a view into a query editor in SQL Server 2008 you must:

Right click the view, script view as, alter to, new query editor window.
Sign in to post a comment.
Posted by Pit G on 3/27/2009 at 10:52 AM
Edit/Modify command is my favorite context menu command for all objects and obviously someone decided to screw things up by removing it from the view objects!!!
It is something that definitely will hold me to stick with the SQL Server Management Studio 2005 where I can.
By the way what is that stupid validation that does not allow connections to SQL Server 2008 with SQL Server Management Studio 2005.

I guess I'll have to wait until the menu customization!!!

I have a suggestion to the next refresh: Adding a pop up dialog that confirms that the user wants to screw up a nicely formatted and more importantly easy to understand code with the one generated by the designer.
Posted by Germo on 3/25/2009 at 8:16 AM
"We have no intention on bringing the command back" => this is very very very bad.
This is one of the most missing features in SQL Server 2008.
The code generated using the wizard is bad (or better: not) formatted. The only way to edit views and have the code well formatted is:
"Right click the view, script view as, alter to, new query editor window."
It works in SQL Server 2005, it can't be so difficult to add this in SQL Server 2008?
Posted by Microsoft on 2/16/2009 at 8:48 AM
Hi n.goodall
    Thank you for your request to add back the edit command. We have no intention on bringing the command back. In the future, we are looking at ways for users to customize the commands, but we aren't there yet.
Thank you,
Bill Ramos