December 3, 2009 at 8:37 pm
Comments posted to this topic are about the item All-in-one
December 4, 2009 at 4:51 am
I'm with you on the Notepad/Word thing!
As for SSMS, I have two instances of that open at once. One is setup for browsing around databases, jobs, SSIS packages etc, and the other is setup as basically a glorified Query Analyser. The QA version sits on my left-hand side monitor, while the other one is on my right-hand side monitor. This mimics how I used to work with Enterprise Mangler and Query Analyser back before we upgraded to 2008.
Not sure that really answers your question though.
December 4, 2009 at 5:04 am
I think I prefer to have more smaller tools. The article made me ask myself why I still use SQL Server 2000 QA for most of my work. I think that when I can't identify what toolbar buttons do without hovering over them, I'm probably less productive.
December 4, 2009 at 5:09 am
As with most things in my life, I prefer a simpler tool that does ONE thing, but does it very well. I'm not looking for the 67 tools in some magical Swiss Army knife. In fact the pocket knife I carry around has but a single solitary blade. Buck Knives, made BEFORE they started shipping their manufacturing to China.
I don't want a combination snowblower, weed-whacker, lawnmower, and juicer.. a tool that does several jobs only marginally will only irritate me.
Same thing for computer programs. I'd love for Word to have the option of disabling parts of it. These monstrous sized programs are designed to eliminate the need for other programs, but they don't do any one particular thing VERY well.
Same concept behind my heavy duty diesel truck, my comfy sedan, my wife's road rocket, and my motorcycle... The proper tool...
Honor Super Omnia-
Jason Miller
December 4, 2009 at 5:37 am
I'm with you on the frustration from "sometimes it works this way, sometimes it works that way" resulting from merged applications. Worse, the application "remembers" what you used last and presumes that to be how you wish to work again. So for beginners like me, it is a constant search for methods in a thick forest of options.
December 4, 2009 at 5:39 am
I generally prefer several smaller tools that do jobs really well. Take for example type ahead. It's built into SSMS, but it stinks. Get a copy of Red Gate SQL Prompt and live in heaven. Other examples that come to mind, we have SCOM monitoring our servers, but getting it to do some of the detailed drill down on SQL Server is a pain in the buttocks, enter Idera's Diagnostic Manager. It doesn't do all the stuff SCOM does, but it does a few things very well. I could keep going, but I think the point is made. After all, you're probably reading this with a web browser. Why? You can open web pages inside Visual Studio, one less app on the old desktop. No? Too big? Too slow to open you say? Question answered.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 4, 2009 at 5:54 am
For my personal use, I don't have a problem with everything combined. However, I have corporate responsibility for creating installation packages for application users needing the management tools and developers needing BIDS. In the past, I could extract the client installation portion from the installation DVD and only supply that to whomever needed it. With SQL Server 2008, I need to supply the entire installation DVD to anyone needing only BIDS or SSMS. Since we us MVLS software with embedded keys, I have to surround the supplied installation software with a package that does not allow the installer access to more than they need because of licensing concerns. It can be done but is a real hassle and we still need to move huge amounts of unneeded software around to various locations.
I would very much like to see the various tools in separate install packages.
December 4, 2009 at 5:58 am
This makes me think of Anton Chigurh's quote from No Country for Old Men "That's foolish. You pick the one right tool."
December 4, 2009 at 6:15 am
No Country for Old Men "That's foolish. You pick the one right tool."
First, I resemble that remark! I've recently done a five year stint as a requirements analyst. It's all about communication. The first decision as an analyst is "choose the tool to capture this requirement." Text, database entry, spreadsheet, document, discussion, laundry list . . . The tool constricts subsequent options, but also focuses the analysis.
Perhaps this applies here also - efficiency says you remove screws with a screwdriver, nails with a nail puller, either with a shotgun.
December 4, 2009 at 6:25 am
2New2Guru (12/4/2009)
efficiency says you remove screws with a screwdriver, nails with a nail puller, either with a shotgun.
I'd prefer to use a Dillon Aero...
Honor Super Omnia-
Jason Miller
December 4, 2009 at 6:43 am
My choice is having several tools that does their job pretty well.
I thought this many times about the SSMS, especially when the Activity Monitor opens one window for each server. I wanted it like Profiler, to have multiple servers being monitored from one window.
Also, when SSMS is closed (or SSMS shutdowns erroneously), all my activity monitors, Job Activity Monitors and Log Viewers are closed. It would be great if they are independent from SSMS.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
December 4, 2009 at 6:44 am
I like the idea of several smaller tools for those that use them extensively. As a developer who fell into the dba role, I'm quite happy having two tools to go to for most of my SQL work. From SQL 2000, I remember hunting for what tool to use to do a job. With 2008, I know where to find things. I'm content with a Swiss Army Knife.
That said, I see great value in specialized tools for those that can use them. I use a programmers' editor as opposed to the VS2008 IDE for straight code writing. Even the time it takes to switch between the tools is worth the hassle. The best tool to use is the one that works well for the user.
So yes, I would like to see a program group (Specialized tools) along with the (generic tools) available now.
December 4, 2009 at 7:01 am
This is an especially interesting question because since we have discovered SQL Server Central there can be no doubt that we have run into some great tools written by members of the site - but then the discussion always seems to turn to "Why the heck doesn't Microsoft build [this] in???"
A great example - CRUD procs. We picked up a great independently written stored procedure that saves a lot of time writing those darn create, replace, update and delete procs. We use that a great deal and yet wonder why Microsoft has not written something into SSMS that allows this to be automated. This is just one example, but there are tons of them.
Another example? SQL Prompt. One of my guys uses this handy tool from Redgate and every time I see it I find myself scratching my head as to why Microsoft would not just add something like this to SQL Server.
The answer we hear is that if Microsoft wrote SQL Server with everything in it that should be in it, there would be no future revenue stream from on-going "upgrades" and new versions.
Presuming there is truth in that - I don't think there is a choice. So I guess its many smaller tools, and thanking God now and then that there are some really creative coders out there who post stuff on sites like SSC to help us (and so many others) round out SQL Server from what it is, to what it should be.
December 4, 2009 at 7:07 am
I have to say I like one tool providing many services, I have the tool running all day. I do also run a separate monitoring tool. But I like having one place to look at for all my Database tools. Maybe because I work at a small company and I perform many functions including DBA and DBD and IT support and the list goes on. It is just simpler, to go to one tool.
December 4, 2009 at 7:09 am
I personally like SSMS. Fits my needs nicely.
Since I almost always have it running, I don't use either Notepad or Word, I just fire up a connection window, type what I need, then save as .txt. So I'm taking it beyond what it's even meant for.
In many cases, I prefer specialized tools. I carry a knife with one locking blade, and nothing else. No screwdriver, no bottle opener, no corkscrew, etc., just a small blade.
But in the case of SSMS, I like that everything I need is in one place. Can't really say why, it just works well for me. Better than Management Studio and Query Analyzer did.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 15 posts - 1 through 15 (of 43 total)
You must be logged in to reply to this topic. Login to reply