Backward Compatibility with SQL Server 2000 Tools
SQL Server 2005 introduces new tools for managing SQL Server. SQL Server Management Studio replaces SQL Server Enterprise Manager, SQL Query Analyzer, the MDX sample application, and some features of the Analysis Manager. SQL Server Enterprise Manager and SQL Query Analyzer cannot be used to manage SQL Server 2005.
sqlcmd is the SQL Server 2005 command prompt tool for executing script files. Connecting to SQL Server 2005 with osql is still fully supported. You must use the version of osql shipped with SQL Server 2005 to perform all SQL Server 2005 functions, however. The version of osql that shipped with SQL Server 2000 will perform those SQL Server 2005 functions that are compatible with SQL Server 2000, but some new features may not be available.
Connecting to SQL Server 2005 with isql is only supported for features common to SQL Server 7.0.
Connecting to SQL Server 2005 with Enterprise Manager is not supported. Connecting to SQL Server 2005 with the SQL Server 2000, service pack 4 version of Query Analyzer is supported.
Use SQL Server Management Objects (SMO) to develop applications that connect to SQL Server 2005. SMO replaces SQL Distributed Management Objects (SQL-DMO) as the preferred application programming interface (API) for developing applications that connect to SQL Server. SQL Server 2005 continues to support applications written in SQL-DMO.
SQL Server Configuration Manager is a Microsoft Management Console (MMC) snap-in that is available from the Start menu, or can be added to any other MMC display. You can start, stop, pause, and resume services with SQL Server Configuration Manager but you cannot manage SQL Server objects such as tables using SQL Server Configuration Manager. SQL Server Management Studio does not use MMC and cannot be added to other MMC tools.
SQL Server Configuration Manager replaces Server Network Utility and Client Network Utility for configuring network protocols.