As already noted, SQL Server 2005 has improved some of the old tools and introduced a number of new tools. However, for those of you who have worked with the earlier versions of SQL Server, you may see that some of the tools no longer exist. Of course, this does not mean that the tasks and scenarios that the old tool supported have been removed from the product. To the contrary, improvements have been made to the tool or it has been integrated with another tool to increase productivity. The goal in SQL Server 2005 has been to increase productivity. One of the points of improvements has been to integrate the same experience across all SQL Server products to provide ultimate productivity. For example, Query Analyzer in SQL Server 2000 provided a good authoring experience for SQL Server 2000 Engine. However, the tool for execution of MDX queries against Analysis Services 2000 was a tool named MDX Sample Application. In SQL Server 2005, both these tools have been integrated into SQL Server Management Studio.
For those of you who were familiar with the old tool set and would like to be able to find your way through the new tool set, see Table 1.1.
Analysis Manager, MDX Sample Application, Enterprise Manager, and Query Analyzer are consolidated into SQL Server Management Studio. In fact, Management Studio is an integrated and comprehensive environment for management, administration, authoring, monitoring, and development for all SQL Server 2005 products (see Figure 1-2).
Figure 1-2. Integration of legacy tools in SQL Server Management Studio.
SQL Profiler has had a small name change: In SQL Server 2005 it is called SQL Server Profiler.
The Index Tuning Wizard launch point was only from Enterprise Manager in SQL Server 2000. In SQL Server 2005, it has a number of impressive features that make it a first-class tool. The new name is Database Engine Tuning Advisor, and it can be launched from the Windows Start menu.
ISQL is not included in the SQL Server 2005 tool set. Microsoft officially deprecated ISQL in SQL Server 2000 and it is not shipped in SQL Server 2005. As its replacement, you should consider using SQLCMD.
Table 1-1 describes the relationship between functionality of SQL Server 2000 and SQL Server 2005 Tools.