Catálogo de publicaciones - libros

Installing SQL Server is no longer an awkward chore that requires several passes through the process to complete. The SQL Server 2005 installation process now follows the Microsoft standard installation format. With all the components available to install in one pass, there should be less confusion about the process and fewer installation problems. SQL Server 2005 presents only a few new considerations to take into account during installation, with these mainly relating to Reporting Services and the installation tree. Updating the installed instance with new functionality, or even removing installed components, is much easier to decipher than in previous versions, so you can be confident you’ll get it right the first time.

In this chapter, we’ve taken a whirlwind tour of the new management technologies in SQL Server 2005. You’ve seen how SQL Server 2005 takes SQL Server management to the next level with new management tools, new APIs, and even new command-line tools. It’s important that you get familiar with all of these technologies, since you will be using one or more of them to manage and monitor your servers.

SQL Server 2005 introduces a large number of new features for DBAs to add to their arsenals: catalog views, performance enhancements, and better data-integrity tools than previous versions of SQL Server. Although the learning curve can be steep with some of these new tools, in the long run use of them will lead to higher-quality, better-performing systems—and more time for DBAs to kick back and take a much-needed break!

CLR integration allows developers to extend the functionality of SQL Server 2005 using safe, wellperforming methods. Coding CLR stored procedures is an easy way to improve upon some of the things that T-SQL doesn’t do especially well. In the next chapter, we’ll cover the other types of CLR objects available to developers: functions, aggregates, user-defined types, and triggers. We’ll also present a more in-depth look into managing routines from a DBA’s perspective.

When used prudently, CLR routines make powerful additions to SQL Server’s toolset. Functions, aggregates, triggers, and types can each be used in a variety of ways to expand SQL Server and make it a better environment for application development. It’s important to remember that some caveats exist and that careful testing is required. That said, SQL Server 2005’s CLR integration should prove incredibly useful for most software shops.

As you’ve seen in this chapter, we’ve established your understanding of XML technologies that work against both SQL Server 2000 and 2005. This includes the OPENXML and FOR XML query extensions, XML BulkLoad, and also the SQLXML technologies. In the next chapter, you’ll see some additional new technologies that were added to SQL Server 2005 to support XML and how some of the technologies you’ve learned about in this chapter have changed.

In this chapter, you saw many examples of using XML in SQL Server 2005. With the addition of a new native XML datatype, which allows you to store your XML data right alongside your relational data, and support for the XQuery language and native XML web services, SQL Server 2005 should provide the level of XML support you need for most applications.

Phew! In this chapter, you have seen how Reporting Services has matured in SQL Server 2005. We started by looking at what SSRS 2000 provided as a level set. Then, we went on to see what was new in SSRS 2005. In a little over a year, the SSRS team has added a lot of new functionality that will make any developer or DBA who has to create reports very happy. Finally, with the new integration with SQL Management Studio, tighter integration with Analysis Services, and newfound developer and end-user enhancements, you should be able to find a use for Reporting Services in any of your Business Intelligence projects.