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.

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 it's color can be easily changed from either it's context menu or from Window connection coloring options. Coloring for each server can be added, removed or just disabled.

Every SQL statement that you run is logged 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.

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 then 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 or deleted 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.