October 29, 2009 at 8:32 am
Forgive me if this has been discussed, but I couldn't find anything. When I develop I end up with 6 instance of SSMS open and inside each instance 6 - 10 windows for developing procs\tables etc... Has anyone found a toll out there that does a better job at managing multiple tabs open at once. The tabs give very little indication on what is inside each window. It would be nice if you could have a bunch of windows open and be able to hover over something and see a good portion of the code pop up or something. Or is this just me?
thanks,
October 29, 2009 at 9:49 am
I think it's you.
If SS2K8 SSMS you can color code your connections so you know which query is connected to which server.
I'm not sure any tool handles the multiple tab better.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
October 29, 2009 at 10:06 am
Who said anything about multiple servers? I would then have to open the code on all different servers (even though they all run on a the same one) just to have different colors? Not a viable solution at all. But thanks...
October 30, 2009 at 6:22 am
I hate to say it, but I think it's you. I very seldom have two instances of SSMS open and then it's usually one logged into the production servers and one logged into everything else (we use seperate accounts for production access to help secure the systems and prevent accidents). Even there I only have 5-6 tabs open in each environment at the most, usually less.
You might want to look into TOAD or DBArtisan. They will both manage SQL Server just fine but have completely different GUI's from SSMS. Maybe one of those will better suit your working style.
What are you doing that you need to have 30 seperate queries available all connected to the same server?
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
October 30, 2009 at 7:53 am
I'd agree with Grant. I assumed (badly) that 30 windows would be multiple servers. If it's not, you might need to rethink the way that you develop code.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
October 30, 2009 at 9:38 am
Several things about SSMS bugged me when I finally made the transition from QA. One thing that has saved it from being an unused icon again is that with SSMS 2K8 you can choose what appears on each tab.
Tools > Options > Text Editor > Editor Tab and Status Bar.
There are also a couple of Third party tab extension mods to SSMS and you (from what I've read) have the ability to add your own add-ins or mods to SSMS that can affect tabs.
The coloring per connection is poorly implemented IMO. I'd much rather you be able to color tabs by database name and have the actual *TAB* colored, not the status bar(which requires you to click on a tab first.)
I personally always have 2 copies of SSMS open (on 2 different monitors) and a copy of enterprise manager, which I still find easier to browse around in than the object explorer. I also always have several specific traces running that I monitor. I need more than 2 monitors :crying:.
October 30, 2009 at 9:40 am
Go to 3!
I thought it was great. One died, and I need to replace it, but havnig 3 worked well. It cost me about $300 for another card and monitor. Relatively cheap in terms of productivity.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply