Execution Plan Analyzer is a feature that will cut your query troubleshooting time at least by half or more. With it you can easily see the costliest plan operators based on different properties like IO, CPU, Number of rows, Cardinality, Relatice cost, etc... Can't find a node that is on a particular index? Need that specific nested loops join? Not a problem anymore. With plan searching this now as easy as pie. And just when you think things can't get better they are with Execution Plan Auto Analyzer. It goes through your plan finding most common problems and gives you the usual solution for each one. This feature isn't meant to replace manual analysis but it will find the usual problematic spots that you can fix up fast.

SQL Snippets give you the ability to type shortcuts in editor which after pressing Enter or Tab turn into a predefined code block. You can have as many SQL snippets as you wish. Since version 1.8 snippets can be exported and imported by themselves.
Since version 1.9 snippets can be saved to html or printed out directly.

Window connection coloring lets you immediately know to which server 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. Coloring for each server 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. Any .Net regular expression is valid.

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.

Window Content History saves the whole text in all all opened SQL windows every N minutes. The default being 2 minutes. 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 teh 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.

Uppercase/Lowercase keywords and proper case Database Object Names. Set all keywords to uppercase or lowercase letters. Custom keywords can be added. Format all database objects to their proper case sensitive name.

Simple search for a search term through all non-binary columns in a single table/view or in every table/view in a database. You can search in four ways: Contains, Starts with, Ends with and Equals.

Run selected or full window text on selected databases on the currently connected server. A new window is opened that contains one script for all databases.

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.

Find all occurrences of your search string in the results in datagrid mode.

Insert statements for the whole database are generated by the order of PK-FK relationships. Top tables with no FK's are scripted first. Binary data is by default fully scripted. If you wish you can also set the scripting data limit between 0 and 10 Mb. Larger values than the limit are then scripted as NULL. Insert statements for the data in result grids are scripted into a new temporary table for each grid. For example from 5 result grids insert statements for 5 temporary tables get created.

Regions behave in the same way as in Visual Studio. You can collapse them and expand them. Debug sections 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.

You can specify a custom script text, its name and node on Object Explorer on which you want to run it from. Node name, current database, current connection string and current server can also be specified in the custom script with keywords that are replaced with their respective values at script runtime.

CRUD stored procedure generation for tables based on fully customizable templates that you can change to suit your needs.

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

In General Options you can Import/Export settings, check for new version updates, enable detailed logging and set webservice access if needed.