I want some Moore

Blog about stuff and things and stuff. Mostly about SQL server and .Net
posts - 218, comments - 2281, trackbacks - 33

My Links

Advertisement

News

Hi! My name is 
Mladen Prajdić  I'm from Slovenia and I'm currently working as a .Net (C#) and SQL Server developer.

I also speak at local user group meetings and conferences like SQLBits and NT Conference
Welcome to my blog.
SQL Server MVP

My Books

SQL Server MVP Deep Dives 2
The Red Gate Guide to SQL Server Team based Development Free e-book

My Blog Feed via Email
Follow MladenPrajdic on Twitter


Users Online: who's online

Article Categories

Archives

Post Categories

Cool software

Other Blogs

Other stuff

SQL stuff

SSMS Tools Pack 2.0 is out! With huge productivity booster features that will blow your mind and ease your job even more.

What better way to end the summer and start those productive autumn days ahead than with a fresh new version of the SSMS Tools Pack.

This is a big release with two new features that are huge productivity boosters.

First new feature are Tab Sessions. Every SQL tab you open is saved every N (default 2) minutes and is stored in a session. This works similar to internet browser sessions. Once you reopen SSMS you can restores your last session with a click of a button. You even get every window connected to the server it was previously connected to. The Tab History Window looks like this:

TSH

 

The second feature is Execution Plan Analyzer. It is designed to quickly help you find costliest operators by a number of properties. If that's not enough you can easily search through the whole execution plan for whatever you like.
And to top it off you can auto analyze the execution plan. The analysis reports various problems the execution plan has and suggests a most common solution. The ultimate purpose of the Execution Plan Analyzer is to make your troubleshooting quicker and easier. It uses a simple user interface that is easy to navigate and is built directly into the execution plan itself. The execution plan analyzer looks like this:

SQLEPA

 

Smaller fixes include a completely redesigned SQL History Search window and various other bug fixes.

You can download the new version 2.0 at the Download page.

For more detailed feature descriptions go to the main Features Page.

Enjoy it!

Print | posted on Wednesday, September 21, 2011 6:24 PM | Filed Under [ .Net SQL Server SSMS Tools Pack ]

Feedback

Gravatar

# re: SSMS Tools Pack 2.0 is out! With huge productivity booster features that will blow your mind and ease your job even more.

Hi Mladen,

Great update. I do have a feature request regarding the autosave functionality. Could you create an option that would have the autosave feature save over the same file each time? Right now a new randomly created file is created for each autosave - even if it has been previously autosaved.

Thanks again for the great SSMS additions.


9/23/2011 1:18 AM | 7gartner
Gravatar

# re: SSMS Tools Pack 2.0 is out! With huge productivity booster features that will blow your mind and ease your job even more.

It already works that way.
If the tab window text hasn't been changed between the two savings if doesn't create a new file.
if it has been changed then it creates a new version with the same hash+time of saving in the file name.

If you're referring to the tab session saving, it creates a session XML file per the SSMS run. So if you start your SSMS 3 times a day, 3 session files will be created.
9/23/2011 11:24 AM | mladenp
Gravatar

# re: SSMS Tools Pack 2.0 is out! With huge productivity booster features that will blow your mind and ease your job even more.

Fantastic to see this updated!

I like the new Tab Session History stuff, and have some feature suggests/tweaks...Sesion Tab History seems to compliment Theo Spears/Redgate's recent SQL Tab Magic nicely. Borrowing some inspiration from there...

Another window, like Tab Session History, but meant for switching between open tabs would be cool (If/when STM becomes available only by paying for SQL Prompt, I'm screwed... can't afford that right now).

In that window, and in the Tab Session History window, can you list some header info including the server & db connected, date & time of last execution from that window, and maybe even show or highlight the specific sql last executed, if it's not the whole tab contents?

The date & time info would a useful way to select/switch tabs, if there was a way to order tabs by that - see them in a list for choosing, etc. Another useful way to order tabs when listed is by connected server/db.

Would be nice if there were a toolbar that listed each server & db connected with a click to select & create a new query window to that one (sort of like Ctrl-N when you're already in a window connected to the server/db and you just want a new window), vs the built-in New Query Window button + connection dialog + switch db process.

Thanks
9/23/2011 4:07 PM | JB
Gravatar

# re: SSMS Tools Pack 2.0 is out! With huge productivity booster features that will blow your mind and ease your job even more.

Mladen,

What I mean is could there be a configuration option where a new file is not created each time autosave detects a change? The first time autosave runs it would create the file hash+time for each open tab. The next time it ran (and detected a change in content in a tab) it would re-use the original filename and overwrite the file with the new contents of each changed tab.

Hopefully this makes sense. The reason I am asking for this is that I have an automated job that sweeps changes to SVN for me every few minutes. If I don't use the same filename then there is no revision history for a document in SVN (and no ability to easily perform diffs, etc.).

thanks again for the great add-in.



9/23/2011 9:45 PM | 7gartner
Gravatar

# re: SSMS Tools Pack 2.0 is out! With huge productivity booster features that will blow your mind and ease your job even more.

First, I want to say THANK YOU for the add-in. The outlining alone is a life saver!!! Not to mention all the other features.

I just downloaded it last week and love it. I do have 1 question/feature request. I really like the debug region and use it a ton. I work a lot with stored procedures and often have to debug them. Instead of opening the proc and copy and pasting the guts from out of the BEGIN and END tags I usually comment out everything but the guts and now (thanks to you) I add a debug region to declare and set the parameters (see below.)

I was wondering if there was currently a way or would it be hard to add a "release" region feature, that does just the opposite of the debug region? Meaning it would comment out the stuff you ONLY need for release LIKE the ALTER PROC line for example.

/*
ALTER PROC [dbo].[asd]
(
@Var1 DATETIME = NULL,
@Var2 NVARCHAR(10) = NULL,
.......
)
AS
BEGIN
*/

#-BeginDebug DEBUG Variables
DECLARE @Var2 NVARCHAR(10),
@Var1 DATETIME

SET @Var2 = '1.7'
--SET @Var1 = '10/7/2011'

#-EndDebug

proc guts......

--END
10/15/2011 2:35 AM | Jon Alvarez
Comments have been closed on this topic.

Powered by:
Powered By Subtext Powered By ASP.NET