绝对值得一试!
下载地址:
http://www.ssmstoolspack.com/Download.aspx
Search Results in Grid Mode and Execution Plans
Find all occurrences of your search string in the execution plans or in the results in datagrid mode.
Generate Insert statements for a single table, the whole database or current resultsets in grids
Insert statements for the whole database are generated by the order of PK-FK relationships. The insert statements for the top tables with no FK's are scripted first
Binary data larger than 5 Mb isn't included in the Insert statements. If you have an image column with 3 Mb of data this will be scripted to an insert statement.
Insert statements for the data in result grids are scripted into a new temporary table for each grid. so if you have 5 result grids you get insert statements for 5 temporary tables.
Query Execution History (Soft Source Control)
Every 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 between check-out and check-in of your file.
Actions are saved in a list that is written to a file and/or a database on a timer which you can set to a desired interval.
Text document Regions and Debug sections
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.
New query template
When opening a new query window you can specify a template that will be displayed.
CRUD (Create, Read, Update, Delete) stored procedure generation
CRUD stored procedure generation for tables based on fully customizable templates that you can change to suit your needs.
Running custom scripts from Object explorer's Context menu
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 will be changed at script runtime.
Search Results in Grid Mode and Execution Plans
Find all occurrences of your search string in the execution plans or in the results in datagrid mode.
Generate Insert statements for a single table, the whole database or current resultsets in grids
Insert statements for the whole database are generated by the order of PK-FK relationships. The insert statements for the top tables with no FK's are scripted first
Binary data larger than 5 Mb isn't included in the Insert statements. If you have an image column with 3 Mb of data this will be scripted to an insert statement.
Insert statements for the data in result grids are scripted into a new temporary table for each grid. so if you have 5 result grids you get insert statements for 5 temporary tables.
Query Execution History (Soft Source Control)
Every 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 between check-out and check-in of your file.
Actions are saved in a list that is written to a file and/or a database on a timer which you can set to a desired interval.
Text document Regions and Debug sections
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.
New query template
When opening a new query window you can specify a template that will be displayed.
CRUD (Create, Read, Update, Delete) stored procedure generation
CRUD stored procedure generation for tables based on fully customizable templates that you can change to suit your needs.
Running custom scripts from Object explorer's Context menu
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 will be changed at script runtime.