The following sections list the minimum hardware and software requirements for running Microsoft SQL Server 2005. Deleting legacy maintenance plans - 2005. SQL Server > SQL Server Tools. SQL Server Tools http:// Question 6 5/16/2006 9:26:38 PM 12/12/2008 5:37:41 AM Any questions and discussions related specifically to SQL Server tools, including SQL Server Data Tools. Maintain DTS packages in SQL Server 2005. by Joseph Toscano, Contributor. If you choose this upgrade path, your databases are replaced with their 2005 equivalents and your development tools are replaced with 2005's new tools. You will be able to find these 2000 packages in SQL Server 2005 Management Studio under Management > Legacy > Data Transformation Services.
SQL Server 2. 00. Management Tools SQL Server 2.
- This article explores several workarounds that facilitate modifying and managing legacy DTS packages until you are ready to migrate them into SQL Server Integration Services format.
- Using SQL Management Studio from SQL Server 2005 to work on a SQL 2000 instance. So, we still use DTS packages for now. On one of my workstations, when opening a DTS package under 'Management > Legacy > Data Transformation Services' I see a chronological sort order for versions of that package, with the newest version at the top.
DBAs and developers. With the addition of some new services in SQL Server 2. DBA concern. The new SQL Server Management Studio replaces both the SQL Server 2. Enterprise Manager and the Query Analyzer.
You need to be aware of two supporting tools: the SQL Server Configuration Manager and the Surface Area Configuration tool. Related: Tool Used with SQL Server 2. Express and SQL Server 2. Feature Pack Let's look at each in turn before turning to the SQL Server Management Studio.
Note that SQL Server 2. Community Technology Previews, which are interim beta- level, pre- release builds.
Sql 2005 Legacy Tools Word
Some minor changes in these management tools may occur before release. The information in this article is based on the feature- complete April Community Technology Preview (CTP). Configuration Management Tools You'll need to use three new small tools whenever you install SQL Server 2. For increased security, SQL Server 2.
With the first tool, you can manage SQL Server services; the other two tools form a set that you can use to manage the interfaces through which unintended or malicious access to SQL Server can occur. We call this set of interfaces SQL Server's attack surface area. SQL Server Configuration Manager.
The SQL Server Configuration Manager is a helper tool that you'll need to manage the Windows login accounts for the various SQL Server 2. You can't start or stop SQL Server 2. SQL Server Management Studio as you can with the Enterprise Manager, so you'll need to learn the SQL Server Configuration Manager right away. You can invoke it from the Windows Start Menu or from the Computer Management applet in the Windows Administrative Tools dialog. If you're running SQL Server Management Studio, which you'll learn about in the next section, you can launch it from the Management Studio Registered Servers dialog. You use the SQL Server Configuration Manager to manage SQL Server services, network libraries, and the SQL Native Client, as Figure 1 illustrates.
Here, you can set and change service accounts and enable and disable services. This tool has some overlap with the next two surface- area configuration tools, which manage these services and other features from a security- threat management standpoint. Surface- area configuration tools. Many new services are available in SQL Server 2. In addition to the standard SQL Server, SQL Agent, and Analysis Server services, you can now configure services for Integration Services (formerly Data Transformation Services—DTS), Reporting Server, Full- Text Search, and SQL Browser. These services are part of the potential attack surface of a SQL Server 2.
To minimize the potential attack surface, Microsoft has provided two new surface- area configuration tools, one for managing services, and another for connectivity features. You'll notice links for these tools at the end of a SQL Server 2. Windows Start Menu. Both of these tools help join the disparate services and features that expose a SQL Server to potential attack, and you can enable and disable those services directly through these tools. The Surface Area Configuration for Services and Connections tool allows you to enable or disable the various services, as shown in Figure 2. You can also disable and enable the SQL Browser service, which listens on UPD port 1.
In the Surface Area Configuration for Features tool, which Figure 3 shows, you can enable connectivity features, including ad- hoc remote queries, CLR integration, Database Mail (SMTP) stored procedures, remote Dedicated Administrator Connections, native Web services (SOAP) endpoints, the OLE automation extended stored procedures, Service Broker endpoints, SQL Mail (MAPI) stored procedures, xp_cmdshell, and the Web Assistant. By default, all these features are disabled and must be explicitly enabled. You can also use the sp_configure system stored procedure to enable many of the features and the relevant T- SQL commands to enable the endpoints. Management Studio SQL Server 2.
SQL Server Management Studio, a comprehensive tool that combines features relevant to both DBAs and developers. Management Studio is a complex tool and contains too many features to cover in detail in this article. The major new changes can be organized along three lines: server management, query editing, and performance analysis. Management Studio is the great "tool consolidator": Microsoft deliberately combined the best administrative features of Enterprise Manager and the best query- editing and analysis features of Query Analyzer into an entirely new tool.
At the same time, Management Studio adds many new features not available in either tool. We'll take a closer look at the new features later in the article. When you first launch Management Studio, you'll notice a Visual Studio look and feel. But even though Management Studio is based on the Visual Studio shell and has some of the same layout, don't let looks fool you: Management Studio is a completely new tool written in managed code. What you'll notice immediately are two basic types of dialogs: the central, non- movable area of the Management Studio Window is the document window area, and the peripheral areas are called components. By default, the document window initially displays the Summary page, which contains several reporting functions about registered SQL Servers.
When you first start up Management Studio, you'll see the Registered Servers and Object Explorer component dialogs on the left side of the window and the Summary page in the document window on the right, as Figure 4 shows. Note that this is the default set of initial components displayed, but you can change them to your own preferred components in the locations you choose. The Summary page lists the contents of an Object Explorer node or produces a report on the selected node. As you work more with the components, you'll invoke a third type of dialog, the non- modal dialog windows that are independent of Management Studio's main window. Each of the component dialogs is dockable and hideable, just as in Visual Studio.
A pushpin icon in the top button bar of each window provides an auto- hide option, which you can also reach by right- clicking at the top of the window. Automatically hiding windows can be useful when you need extra screen space for expanding the Object Browser, authoring queries, and so on. You can change the behavior of these dialogs by clicking the Window Position option, a small, triangular down arrow at the top right of each component dialog.
You can activate many other component dialogs from the View menu. The default Registered Servers and Object Explorer component dialogs are most useful for administration. Other component dialogs such as the Solution Explorer, Template Explorer, and Properties dialogs are more useful for query editing and analysis. Management Studio remembers your most recent windows settings and uses your last configuration when you restart the tool. If you want to reset your windows to the default setting, choose Reset Window layout from the Window menu. Management Studio supports administration and script editing for multiple products: instances of the SQL Server database engine, along with instances of the Analysis Services server, Report Server, Integration Services, and SQL Server Mobile. You can register all these types of services in Management Studio's Register Servers component and manage them using Object Explorer.
You can also edit T- SQL scripts, Analysis Services scripts, and SQL Server Mobile scripts and organize them in projects using the Solution Explorer component, as we show in the Query Editing section. Administration To fully appreciate the new features that Management Studio brings to DBAs, let's begin with a comparison of Management Studio with Enterprise Manager, the standard SQL Server 2. Enterprise Manager is the essential SQL Server 2.
For example, it manages only the SQL Server relational engine and the SQL Agent service, but not Analysis Services. Further, Enterprise Manager can't display large numbers of servers, databases, or database objects efficiently. Another problem is that it often uses modal dialogs, so after starting some action such as a backup, you often have to bring up a second instance of Enterprise Manager to continue monitoring a server. Finally, Enterprise Manager is a Microsoft Management Console (MMC) application and isn't particularly stable, occasionally causing frustrating errors and unresponsive behavior.
Management Studio overcomes all these limitations. You can now manage Analysis Services instances in addition to the relational- engine instances.
Management Studio uses the new SQL Management Objects (SMO) API for efficient management of large numbers of database objects. Finally, it uses non- modal dialogs whenever possible and is written in stable managed code. Registered servers. Unlike with Enterprise Manager, the Management Studio component for registering servers and organizing those servers is separate from the component for exploring server objects.
You can export a registered server or server group's registration information to an XML configuration file, and then later import it into the same or another server, by just right- clicking over the registered server or server group and choosing Export. SQL Server 2. 00.
SQL Server services management from server management. For example, you can't start or stop services from the Registered Servers component; to manage the services, you need to run the SQL Server Configuration Manager. Management Studio separates registering a server from connecting to a server and exploring the server's objects. Registering a server in the Registered Servers window makes a momentary connection for validation but doesn't keep you connected to the server.