SSMS Tools Pack is a Microsoft SQL Server Management Studio (SSMS) add-in. It can be used with SSMS versions 2008, 2008 R2, 2012 and 2014. Tab Sessions make your work with tabs even easier. Each tab is saved periodically as defined by the interval for Window Content History. The two features are connected. You can also Restore Last Session by pressing the button on toolbar. This openes the last saved tabs already connected to the server they were connected too before. Simple, easy and fast.

SQL Editor Plus
SQL Editor Plus (available only in SSMS 2012 and up) gives you two helpful options for now. The first one is running a statement at your cursor position by pressing SHIFT+F5.

The second one can be a real life saver.
It's called the Accidental Data Destruction Protector.
It pops an "Are you sure?" window if it detects you've executed a DELETE or UPDATE statements without a WHERE clause or a TRUNCATE statement. If you're sure you want to proceed just press Enter, F5 or Ctrl+E to continue execution. By default it checks for all three destructive statements only if you're executing a selected text. All of this can be set in Options.

New query template
When opening a new query window you can specify a template that will be displayed.



Window Content History saves the whole text in all opened SQL windows every N minutes. The default being 1 minute. This feature fixes the shorcoming of the Query Execution History which is saved only when the query is run. If you're working on a large script and never execute it the existing Query Execution History wouldn't save it. By contrast the Window Content History saves everything in a .sql file so you can even open it in your SSMS. The Query Execution History and Window Content History files are correlated by the same directory and file name so when you search through the Query Execution History you get to see the whole saved Window Content History for that query. It is turned ON by default.

Query Execution History logs every SQL statement that you run in a file on your disk or in a table in a database you specify with a connection string. This way, if you're working on some script you can get the full history of every change you've made. SQL Statements are saved in a list that is written to a file and/or a database with a timer which you can set to a desired interval. Older query history logs can be auto deleted. Time after which the logs are deleted is user settable. The size of the code to be saved can also be set up to the maximum of 5 MB of code.

Current window history is a dockable window that shows queries executed in a currently active window. It alse has a search box at the top that filters results as you type. Each entry also shows the color of the server/database it was run on. This is very helpful if you change your connection in the same query window.



Copy execution plan to clipboard/file
Copy selected or all execution plans to a bitmap that is saved either the clipboard or to a file. Large execution plans that don't fit in the window are also copied in full. Width of a picture containing all execution plans is equal to the width of the widest execution plan.

Window Connection Coloring
Window Connection Coloring lets you immediately know to which server and database you're connected to. The color strip can be docked to any side of the window and its color can be easily changed from either its context menu or from Window connection coloring options.
In SSMS 2012 and higher the actual query window tab is also colored at the top border with the same color as the already existing strip making it much easier to visually see to which server your query window is connected to even when a window is not focused.

Coloring for each server or database can be added, removed or just disabled. In version 1.9 the server name as a regular expression has been added.
This makes managing a lot of servers easier. For example if you have 100 servers named like PROD_***, DEV_***, TEST_*** you can now write a regular expression that replaces 100 lines in the server grid with just 3 lines. Any .Net regular expression is valid.
To add a new server or database name, just add a row to the server names grid.

Regions and Debug sections
Regions behave in the same way as in Visual Studio. You can collapse them and expand them. Debug sections (SSMS 2005 and SSMS 2008 (R2) only) are sections that get commented when you change your script to Release configuration. A debug section is also a collapsable region. If you deploy a script in debug mode with added debug sections it will fail when run from SSMS without SSMS Tools Pack installed. You can of course comment those sections yourself by simply searching for start and end text of the debug sections.

Home:

http://www.ssmstoolspack.com

[/b]

[b] Only for V.I.P

Warning! You are not allowed to view this text.