Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Management Studio, why o WHY!

Author  Topic 

sql777
Constraint Violating Yak Guru

314 Posts

Posted - 2007-09-24 : 13:55:07
I like some of the new features in sql2005 management studio, but WHY do you have to right-click -> Modify to view the stored procedure code?

It is SO annoying, previous versions was a simple and quick-double click.

To me this is a major blunder!

Anyone else agree with me?

Zoroaster
Aged Yak Warrior

702 Posts

Posted - 2007-09-24 : 14:02:41
I might agree if I knew what you were talking about! Please clarify with where you are having to right click now that you didn't before?



Future guru in the making.
Go to Top of Page

sql777
Constraint Violating Yak Guru

314 Posts

Posted - 2007-09-24 : 14:40:41
Zoroaster (edited the original post, sorry for not being clear),

If you need to edit a stored procedure, you have to right-click | Modify to view the sql code.

Annoying isn't it?
Go to Top of Page

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-09-24 : 14:43:56
yeah.. i'm stumped too.. no idea what he means.

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp
SSMS Add-in that does a few things: www.ssmstoolspack.com
Go to Top of Page

Zoroaster
Aged Yak Warrior

702 Posts

Posted - 2007-09-24 : 14:44:23
quote:
Originally posted by sql777

Zoroaster (edited the original post, sorry for not being clear),

If you need to edit a stored procedure, you have to right-click | Modify to view the sql code.

Annoying isn't it?



I agree, it should be a configuration option to change that (maybe it is?). For me it's not a big deal but anytime you have to click more to do the same thing it's a step backwards.



Future guru in the making.
Go to Top of Page

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-09-24 : 14:48:04
well acctually it's the same amount of clicks.
now you do right-left and before you did left left.

this is a feature that MS Ergonomics Team (MSET) suggested to aleviate the possible wrist inflamations caused by excesive
double clicking. research has proven that double clicks are most notorious culprits of wrist pain.
because of that the future versions of all MS software will not have double click enabled.
It is expected that the double click will be fully banned from windows message queue altoghether
with the release of Windows in 2011/2012.

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp
SSMS Add-in that does a few things: www.ssmstoolspack.com
Go to Top of Page

Zoroaster
Aged Yak Warrior

702 Posts

Posted - 2007-09-24 : 14:55:59
You are correct, same number of clicks, just more movement. Maybe they should introduce a Wii like interface so you can spin the wand in place of a double-click. It would feel more like SQL Wizardry and prevent clicks completely.



Future guru in the making.
Go to Top of Page

Zoroaster
Aged Yak Warrior

702 Posts

Posted - 2007-09-24 : 15:02:53
Looks like this has been discussed before:

http://www.mydatabasesupport.com/forums/ms-sqlserver/218024-changing-double-click-default-object-explorer.html

There seems to be no way to change the functionality. For me though it is not really an issue as I usually just type sp_helptext <proc name> in the Query window anyway. On the other hand because I used to be very involved in usability testing in my former life I do find it frustrating when changes of this nature are made to a UI without customizable options for those who preferred the "old way".





Future guru in the making.
Go to Top of Page

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-09-24 : 15:20:36
here's some shameless advertising:
with my SSMS add-in you can put any script in the object explorer context menu and run it.
look in my sig.

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp
SSMS Add-in that does a few things: www.ssmstoolspack.com
Go to Top of Page

Zoroaster
Aged Yak Warrior

702 Posts

Posted - 2007-09-24 : 16:04:58
Looks good Spirit, I will have to play with it some.



Future guru in the making.
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2007-09-25 : 02:18:43
"Anyone else agree with me?"

I have a different point of view. Nothing would induce me to make a change to a stored procedure directly within the database anyway. Or even to view it (what good is that? I can't tell whether its version 1 or 2 without comparing it against Version 2 source code, and anyway we have a Logging system that will tell me what version is in a particular database).

All my Sprocs are in my favorite Version Control System and edited with my Favourite SQL Editor tool ...

Kristen
Go to Top of Page

sql777
Constraint Violating Yak Guru

314 Posts

Posted - 2007-09-25 : 13:12:54
Kristen,

So how do you go about making changes? Go to your fav. version control, edit it with your fav. sql editor and THEN copy and paste to the query analyzer???

What is your fav. version control system & sql editor??
Go to Top of Page

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2007-09-25 : 14:07:51
source safe of course. there's no better product on the market

_______________________________________________
Causing trouble since 1980
blog: http://weblogs.sqlteam.com/mladenp
SSMS Add-in that does a few things: www.ssmstoolspack.com
Go to Top of Page

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2007-09-25 : 14:24:06
Oh man...
Now my sarcasm detector broke down



E 12°55'05.25"
N 56°04'39.16"
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2007-09-25 : 14:27:55
quote:
Originally posted by sql777


So how do you go about making changes? Go to your fav. version control, edit it with your fav. sql editor and THEN copy and paste to the query analyzer???



Hopefully your source control would be integrated into SSMS so that you don't need to jump around products to get things checked in and out. If you have a team of database developers, I'd recommend using Visual Studio .NET Team Edition for Database Developers along with Visual Studio .NET Team Foundation server.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/
Go to Top of Page

Kristen
Test

22859 Posts

Posted - 2007-09-26 : 05:27:05
"What is your fav. version control system"

Sub-version / Tortoise. Just change the files in a given* folder, and Sub Version takes care of the rest

* "given" means that SubVersion has already been told that particular folder is under Version Control. You can change the files how you like - copy them to a laptop and then copy the whole lot back again (changed ones and unchanged ones, pre-delete the whole lot and then create new copies, rename the originals and put original-name ones in their place, whatever, it will work out SPECIFICALLY which files have ACTUALLY changed, and only check-in the changed ones - so it works well even when not integrated into the Editor tool

And its free See: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=55210&SearchTerms=Version+Control

" & sql editor??"

Right now its Query Analyser, so I have to admit that the "copy and paste to the query analyzer" step is redundant , and I would have a requirements that "my favourite SQL editor" could actually execute the SQL ...

Kristen
Go to Top of Page

jen
Master Smack Fu Yak Hacker

4110 Posts

Posted - 2007-09-26 : 14:05:08
my fave too... saves a lot of trouble and traces are very very very handy

ANT to deploy to production
Notepad or QA to edit/test

--------------------
keeping it simple...
Go to Top of Page
   

- Advertisement -