« Home « Kết quả tìm kiếm

Microsoft SQL Server 2005 Developer’s Guide- Part 3


Tóm tắt Xem thử

- Overall, the new features in SQL Server 2005 give it a very high return on investment..
- A Brief History of Microsoft SQL Server.
- SQL Server 2005 is the latest version of a database server product that has been evolving since the late 1980s.
- Microsoft SQL Server originated as Sybase SQL Server in 1987.
- Later, Aston-Tate dropped out of the SQL Server development picture, and Microsoft and Sybase signed a co-development agreement to port SQL Server to Windows NT.
- The co-development effort cumulated in the release of SQL Server 4.0 for Windows NT.
- After the 4.0 release, Microsoft and Sybase split on the development of SQL Server.
- SQL Server 6.0 was the first release of SQL Server that was developed entirely by Microsoft.
- In 1996, Microsoft updated SQL Server with the 6.5 release.
- After a two-year development cycle, Microsoft released the vastly updated SQL Server 7.0 release in 1998.
- SQL Server 7.0 embodied many radical changes in the underlying storage and database engine technology used in SQL Server.
- SQL Server 2000, the accumulation of another two-year development effort, was released in September of 2000.
- The move from SQL Server 7.0 to SQL Server 2000 was more of an evolutionary move that didn’t entail the same kinds of massive changes that were made in the move from 6.5 to 7.0.
- Instead, SQL Server 2000 built incrementally on the new code base that was established in the 7.0 release.
- Starting with SQL Server 2000, Microsoft began releasing updates to the basic release of SQL Server in the following year starting with XML for SQL Server Web Release 1, which added several XML features including the ability to receive a result set as an XML document.
- The next year they renamed the web release to the more succinctly titled SQLXML 2.0, which, among other things, added the ability to update the SQL Server database using XML updategrams.
- Two years later, Microsoft SQL Server release history cumulates with the release of SQL Server 2005.
- SQL Server 2005 uses the same basic architecture that was established with SQL Server 7 and it adds to this.
- all the features introduced with SQL Server 2000 and its web releases in conjunction with the integration of the .NET CLR and an array of powerful new BI functions..
- The following timeline summarizes the development history of SQL Server:.
- 䉴 1987 Sybase releases SQL Server for UNIX..
- 䉴 1988 Microsoft, Sybase, and Aston-Tate port SQL Server to OS/2..
- 䉴 1989 Microsoft, Sybase, and Aston-Tate release SQL Server 1.0 for OS/2..
- 䉴 1990 SQL Server 1.1 is released with support for Windows 3.0 clients..
- 䉴 Aston-Tate drops out of SQL Server development..
- 䉴 1992 Microsoft SQL Server 4.2 for 16-bit OS/2 1.3 is released..
- 䉴 1992 Microsoft and Sybase port SQL Server to Windows NT..
- 䉴 1993 Microsoft and Sybase release version 4.2 of SQL Server for Windows NT..
- 䉴 1994 Microsoft and Sybase co-development of SQL Server offi cially ends..
- 䉴 Microsoft continues to develop the Windows version of SQL Server..
- 䉴 Sybase continues to develop the UNIX version of SQL Server..
- 䉴 1995 Microsoft releases version 6.0 of SQL Server..
- 䉴 1996 Microsoft releases version 6.5 of SQL Server..
- 䉴 1998 Microsoft releases version 7.0 of SQL Server..
- 䉴 2000 Microsoft releases SQL Server 2000..
- 䉴 2001 Microsoft releases XML for SQL Server Web Release 1 (download)..
- 䉴 2005 Microsoft releases SQL Server 2005 on November 7 th , 2005..
- SQL Server Management Studio BI Development Studio.
- W hen it comes to server management, a lot has changed for the DBA in SQL Server 2005.
- The administrative tools that were used to manage the previous versions of SQL Server have been replaced, and new management tools have been added to help the DBA interact more efficiently with the database server.
- In this chapter, we’ll first take a look at the new SQL Server Management Studio, which combines, into one integrated environment, the four previous tools: Enterprise Manager, Query Analyzer, Profiler, and Analysis Manager.
- SQL Server Management Studio.
- The SQL Server Enterprise Manager, which was the primary management tool for SQL Server versions 7 and 2000, has been replaced by the new SQL Server Management Studio, which also replaces the Query Analyzer tool, which was the core T-SQL development tool in SQL Server versions 7 and 2000.
- SQL Server 2005 also includes several other administrative tools, such as the new Administration Console, the Database Tuning Adviser, and the Profiler.
- The SQL Server Management Studio is accessed using the Start | Programs | Microsoft SQL Server | SQL Server Management Studio menu option.
- You can see the SQL Server Management Studio in Figure 1-1..
- The SQL Server Management Studio can be used to manage SQL Server 2005 systems as well as SQL Server 2000 and SQL Server 7 systems.
- however, it cannot be used on SQL Server 6.5 or older systems.
- You can use the previous SQL Server 7/2000 Enterprise Manager to manage a new SQL Server 2005 system, but this isn’t supported or recommended because of some architectural changes between the two releases..
- Likewise, the older management tools cannot access any of the new features that have been added to SQL Server 2005.
- The SQL Server Management Studio is the best choice for managing mixed SQL Server 2005 and SQL Server 7/2000 systems..
- The SQL Server Management Studio has been completely rewritten and now uses the latest Microsoft technologies, like Winforms and the .NET Framework..
- instead, SQL Server Management Studio works with T-SQL, MDX, and DTS..
- The SQL Server Management Studio User Interface.
- One of the important improvements the SQL Server Management Studio offers over the SQL Server Enterprise Manager lies in its use of dialog boxes.
- In the older SQL Server Enterprise, if you opened a dialog, you couldn’t do anything else until the dialog was closed..
- The new nonmodal dialogs used by the SQL Server Management Studio solve this Figure 1-1 SQL Server Management Studio.
- Another important enhancement in the SQL Server Management Studio is how it deals with large numbers of database objects.
- In the previous versions of SQL Server, the SQL Server Enterprise Manager always enumerated all of the database objects when it connected to a registered server.
- However, for companies with very large databases, which could contain thousands of database objects, the SQL Server Enterprise Manager could take a very long time listing all of the database objects and their properties.
- This basically left the SQL Server Enterprise Manager unusable until all of the objects were listed.
- With SQL Server 2005, the SQL Server Management Studio loads objects asynchronously, allowing the user to start to expand a database item that has many children, while at the same time performing other activities in the user interface..
- SQL Server Management Studio User Interface Windows.
- This section gives you an overview of the SQL Server Management Studio user interface windows, including:.
- As with the previous SQL Server Enterprise Manager, you must register servers in the SQL Server Management Studio before you can use it to manage them.
- To register new SQL Server systems, you use the SQL Server Management Studio’s Registered Servers window (shown in the upper left-hand corner of Figure 1-1).
- You can connect to and manage any SQL Server component using the SQL Server Management Studio, including instances of the Database Engine, Analysis Services, Reporting Services, Integration Services, and SQL Server Mobile Edition..
- You register a new SQL Server system in the Registered Servers window by right- clicking the window and selecting the New | Server Registration option from the context menu.
- This enables you to quickly populate the Registered Servers windows of other SQL Server Management Studios without having to manually reregister all of the managed servers..
- The Object Explorer window of SQL Server Management Studio allows you to connect to any of the SQL Server components.
- For instance, the SQL Server | Databases folder displays a context menu that allows you to create, attach, back up, restore, copy, and generate scripts for a database;.
- while the SQL Server | Databases | Tables | table context menu allows you to create, modify, open, rename, delete, or generate a script.
- Generating Scripts A very useful enhancement in SQL Server Management Studio is the ability to generate scripts for database objects.
- You can create scripts using Object Explorer or by using the Generate SQL Server Scripts Wizard..
- SQL Server Databases This folder contains the System Databases folder, the Database Snapshots folder, and any User Database folders.
- DTS 2000 Packages Folder for SQL Server 2000 DTS migration packages..
- Management This folder contains the SQL Server Logs, Backup Devices, Server Triggers, and Maintenance Plans folders.
- SQL Server Agent This folder contains the Jobs, Alerts, Operators, Proxies, and SQL Agent Error Logs folders.
- The SQL Server Agent is displayed only to members of the sysadmin role..
- Analysis Server Databases This folder contains the SQL Server 2005 Analysis Services (SSAS) databases.
- Integration Services Running Packages This folder contains the opened and running SQL Server 2005 Integration Services (SSIS) packages..
- SQL Server Mobile This folder contains a limited set of SQL Server nodes that includes: Tables, Views, Programmability, and Replication..
- The first way to open the Generate Scripts Wizard is by right-clicking an instance of a SQL Server Database Engine and selecting the Launch Wizard option.
- You can configure the SQL Server Management Studio to display the Summary Page automatically, or you can disable the display of the Summary Page.
- SQL Server Management Studio opens.
- The Solution Explorer is an important management tool that is provided as a part of the SQL Server Management Studio

Xem thử không khả dụng, vui lòng xem tại trang nguồn
hoặc xem Tóm tắt