Contents ix XML Data Type Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Exist(XQuery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Modify(XML DML) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Query(XQuery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Value(XQuery, [node ref]) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 XML Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Primary XML Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Secondary XML Indexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Using the For XML Clause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 For XML Raw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 For XML Auto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 For XML Explicit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Type Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 FOR XML Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Nested FOR XML Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 Inline XSD Schema Generation . . . . . . . . . . . . . . . . . . . . . . . . . . 242 OPENXML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 XML Bulk Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Native HTTP SOAP Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Creating SOAP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 Using SOAP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 Chapter 8 Developing Database Applications with ADO . . . . . . . . . . . . . . . . 255 An Overview of OLE DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 OLE DB Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 ADO (ActiveX Data Objects) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258 OLE DB and ADO Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 ADO Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 An Overview of Using ADO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 Adding the ADO Reference to Visual Basic . . . . . . . . . . . . . . . . . . . . . . . . . 263 Using ADO Objects with Visual Basic . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 Connecting to SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Retrieving Data with the ADO Recordset . . . . . . . . . . . . . . . . . . . . . . 281 Executing Dynamic SQL with the ADO Connection Object . . . . . . . . . . . . . . 305 Modifying Data with ADO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Executing Stored Procedures with Command Objects . . . . . . . . . . . . . . . . 316 Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 x Microsoft SQL Server 2005 Developer’s Guide Advanced Database Functions Using ADO . . . . . . . . . . . . . . . . . . . . . . . . . 320 Batch Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Using Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 Chapter 9 Reporting Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 Reporting Services Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Reporting Services Components . . . . . . . . . . . . . . . . . . . . . . . . . . 327 Installing Reporting Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 Report Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 Report Server Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Report Server Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 Report Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 Reporting Services Configuration and Management Tools . . . . . . . . . . . . . . . . . 341 Reporting Services Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . 342 Report Server Command-Prompt Utilities . . . . . . . . . . . . . . . . . . . . . 344 Report Authoring Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Report Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 Report Model Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Report Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Programmability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Using URL Access in a Window Form . . . . . . . . . . . . . . . . . . . . . . . . 359 Integrating Reporting Services Using SOAP . . . . . . . . . . . . . . . . . . . . . 361 Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 RDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Accessing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Using URL Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 URL Access Through a Form POST Method . . . . . . . . . . . . . . . . . . . . . 363 Report Authoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 Development Stages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363 Creating a Reporting Services Report . . . . . . . . . . . . . . . . . . . . . . . 364 Deploying a Reporting Services Report . . . . . . . . . . . . . . . . . . . . . . . 369 Running a Reporting Services Report . . . . . . . . . . . . . . . . . . . . . . . 369 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Chapter 10 SQL Server Integration Services . . . . . . . . . . . . . . . . . . . . . . . 373 An Overview of SQL Server Integration Services . . . . . . . . . . . . . . . . . . . . . . 374 Data Transformation Pipeline (DTP) . . . . . . . . . . . . . . . . . . . . . . . . 375 Data Transformation Runtime (DTR) . . . . . . . . . . . . . . . . . . . . . . . . 376 Contents xi Creating Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Using the SSIS Import and Export Wizard . . . . . . . . . . . . . . . . . . . . . 377 Using the SSIS Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Using Breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 Using Checkpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 Using Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 Package Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Deploying Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399 Creating Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 Using the Package Deployment Utility . . . . . . . . . . . . . . . . . . . . . . . 403 Programming with the SQL Server Integration Services APIs . . . . . . . . . . . . . . . . 404 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 Chapter 11 Developing BI Applications with ADOMD.NET . . . . . . . . . . . . . . . 415 Analysis Services Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 XML for Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 Analysis Management Objects (AMO) Overview . . . . . . . . . . . . . . . . . . 417 ADOMD.NET Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 AMO Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 ADOMD.NET Object Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 Building a BI Application with ADOMD.NET . . . . . . . . . . . . . . . . . . . . . . . . 421 Adding a Reference for ADOMD.NET . . . . . . . . . . . . . . . . . . . . . . . . 422 Using the AdomdConnection Object . . . . . . . . . . . . . . . . . . . . . . . . 423 Using the AdomdCommand Object . . . . . . . . . . . . . . . . . . . . . . . . . 427 Using the AdomdDataAdapter Object . . . . . . . . . . . . . . . . . . . . . . . 434 Using the CubeDef Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 Chapter 12 Developing with SMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 Using SMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 Adding SMO Objects to Visual Studio . . . . . . . . . . . . . . . . . . . . . . . . 441 Creating the Server Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 Using SMO Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 SMO Property Collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 SMO Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 Building the SMO Sample Application . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 Creating the Server Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460 Listing the Registered SQL Systems . . . . . . . . . . . . . . . . . . . . . . . . 461 Connecting to the Selected SQL Server System . . . . . . . . . . . . . . . . . . . 461 xii Microsoft SQL Server 2005 Developer’s Guide Listing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463 Listing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 Listing Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465 Retrieving Column Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 Creating Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 Transferring Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 Showing T-SQL Script for Tables . . . . . . . . . . . . . . . . . . . . . . . . . . 472 SMO Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 Chapter 13 Using sqlcmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477 sqlcmd Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478 Command Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478 Command-Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479 sqlcmd Extended Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 484 sqlcmd Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484 Developing sqlcmd Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485 Developing sqlcmd Scripts with Query Editor . . . . . . . . . . . . . . . . . . . . 485 Using sqlcmd Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487 Using sqlcmd Script Nesting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488 Using sqlcmd Variables and T-SQL Statements . . . . . . . . . . . . . . . . . . . 489 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490 Appendix SQL Profiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 Starting SQL Profiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 Starting, Pausing, and Stopping a Trace . . . . . . . . . . . . . . . . . . . . . . . . . . 496 Replaying a Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 Showplan Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 xiii Acknowledgments T his book is the successor to the SQL Server 2000 Developer’s Guide, which was extremely successful thanks to all of the supportive SQL Server developers who bought that edition of the book. Our first thanks go to all of the people who encouraged us to write another book about Microsoft’s incredible new relational database server: SQL Server 2005. Making a book is definitely a team effort, and this book is the epitome of that. We’d like to extend our deepest gratitude to the team at McGraw-Hill/Osborne, who helped to guide and shape this book as it progressed through its many stages. First, we’d like to thank Wendy Rinaldi, editorial director, for her encouragement in getting this project launched and her on-going support. We’d also like to thank acquisitions coordinator Alex McDonald for spearheading the effort to bring this project home. The book’s content benefited immensely from the efforts of project editor Carolyn Welch, technical reviewer Karl Hilsmann, and copy editor Bob Campbell. We’d also like to thank Tom Rizzo and Bill Baker from Microsoft for helping us to understand better where the product is headed and the emerging importance of BI and SQL Server 2005. Copyright © 2006 by The McGraw-Hill Companies. Click here for terms of use. Introduction S QL Server 2005 is a feature-rich release that provides a host of new tools and technologies for the database developer. This book is written to help database developers and DBAs become productive immediately with the new features and capabilities found in SQL Server 2005. This book covers the entire range of SQL Server 2005 development technologies from server side development using T-SQL to client side development using ADO, ADO.Net, and ADOMD.NET. In addition, it shows how to develop applications using the new SQL Server 2005 Notification Services, SQL Server Service Broker, Reporting Services, and SQL Server Integration Services subsystems. The development management landscape for SQL Server 2005 has changed tremendously in SQL Server 2005, so Chapter 1 starts off by providing a guided tour of the new development and management tools in SQL Server 2005. Although SQL Server 2005 certainly embodies a huge number of significant changes, some things have stayed the same and one of those things is the fact that T-SQL is still the native development language for SQL Server 2005 and is the core for all SQL Server 2005 database development. Chapter 2 shows you how to use the new T-SQL development tools found in both SQL Server 2005 and Visual Studio 2005 as well as how to create both T-SQL DDL and DML solutions. Chapter 3 dives into the new SQL CLR integration capabilities of SQL Server 2005. The integration of the .NET CLR runtime with SQL Server 2005 is one of the biggest new changes in SQL Server 2005. This chapter shows you how to create and use all of the new SQL CLR database objects, including stored procedures, functions, triggers, user-defined types, and user-defined aggregates. Chapter 4 introduces the new SQL Server Service Broker subsystem that provides the basis for building asynchronous applications. Both the SQL Service Broker chapter and the Notification Services chapter (Chapter 5) provide an overview of the new subsystem and then go on to show how they are used in a sample application. ADO.NET is Microsoft’s core data access technology, and Chapter 6 illustrates how to use all the primary ADO.NET objects to create robust data applications. The integration of XML with the relational database engine is another one of the big enhancements in SQL Server 2005. Chapter 7 shows how to use the new XML data type for both typed and untyped data as well as xiv Copyright © 2006 by The McGraw-Hill Companies. Click here for terms of use. how to create Web Services that expose SQL Server stored procedures for heterogeneous platform integration. While most of this book concentrates on the newest .NET and XML-based technologies, the majority of SQL Server client applications are written in ADO and VB6. Chapter 8 illustrates all of the primary ADO techniques for building SQL Server database applications. Two of the hottest technologies in SQL Server 2005 are Reporting Services and the end-user oriented Report Builder report designer application. Chapter 9 dives into both of these new features, showing you how to build reports using Reporting Services as well as how to set up data models for use with Report Builder. Chapter 10 introduces the new SQL Server Integration Services subsystem. SQL Server Integration Services completely replaces the older DTS subsystem, and this chapter shows you how to build and deploy SSIS packages using the designer and the SSIS API. Chapter 11 illustrates building client Business Intelligence applications for Analysis Services using the new ADOMD.NET data access programming framework. SQL Server 2005 also introduces another completely new management framework called System Management Objects (SMO), which replaces the older Distributed Management Objects (DMO) object framework that was used in earlier versions of SQL Server. In Chapter 12 you can see how SMO can be used to build your own customized SQL Server management applications. SQL Server 2005 also provides an entirely new command line interface called sqlcmd that replaces the older isql and osql utilities. In Chapter 13 you can see how to develop management and data access scripts using the sqlcmd tool. Finally, this book concludes with an introduction to using SQL Profiler. SQL Profiler is key tool for both troubleshooting application performance as well as fine-tuning your data access queries. All of the code presented in this book is available for download from McGraw-Hill/ Osborne’s web site at www.osborne.com, and from our web site at www.teca.com. SQL Server 2005’s Design Goals SQL Server 2005 faces a much different challenge today than it did in the eighties when SQL Server was first announced. Back then ease-of-use was a priority and having a database scaled to suit the needs of a small business or a department was adequate. Today SQL Server is no longer a departmental database. It’s a full-fledged enterprise database capable of providing the data access functionality to the largest of organizations. To meet these enterprise demands, Microsoft has designed SQL Server 2005 to be highly scalable. In addition, it must also be secure; it must be able to be easily integrated with other platforms; it must be a productive development platform; and it must provide good return on investment. Introduction xv xvi Microsoft SQL Server 2005 Developer’s Guide Scalability Scalability used to be an area where Microsoft SQL Server was criticized. With its roots as a departmental system and the limitations found in the Microsoft SQL Server 6.5 and earlier releases, many businesses didn’t view SQL Server as a legitimate player in the enterprise database market. However, all that has changed. Beginning with the release of SQL Server 7, Microsoft made great strides in the scalability of the SQL Server platform. Using distributed partitioned views, SQL Server 7 jumped to the top of the TPC-C, and, in fact, its scores were so overwhelming that SQL Server 7 was a contributing factor to the TPC (Transaction Processing Councils) decision to break the transactional TPC-C test into clustered and nonclustered divisions. Although Microsoft and SQL Server 7 owned the clustered TPC-C score, demonstrating its ability to scale out across multiple systems, there was still some doubt about the platform’s ability to scale up on a single platform. That too changed with the launch of Windows Server 2003 and the announcement of SQL Server 2000 Enterprise Edition 64-bit where Microsoft announced that for the first time Microsoft SQL Server reached the top of the nonclustered TPC-C scores. Today, with the predominance of web-based applications, scalability is more important than ever. Unlike traditional client/server and intranet applications, where you can easily predict the number of application users, web applications open up the door for very large numbers of users and rapid changes in resource requirements. SQL Server 2005 embodies the accumulation of Microsoft’s scalability efforts, and builds on both the ability to scale out using distributed partitioned views as well as the ability to scale up using its 64-bit edition. Its TPC-C scores clearly demonstrate that SQL Server 2005 can deal with the very largest of database challenges—even up to the mainframe level. And the SQL Server 2005’s self-tuning ability enables the database to quickly optimize its own resources to match usage requirements. Security While scalability is the stepping stone that starts the path toward enterprise-level adoption, security is the door that must be passed to really gain the trust of the enterprise. In the past, SQL Server, like many other Microsoft products, has been hit by a couple of different security issues. Both of these issues tended to be related to implementation problems rather than any real code defects. A study by one research firm showed that up to 5,000 SQL Server systems were deployed on the Internet with a blank sa password, allowing easy access to any intruders who wanted to compromise the information on those systems. Later, in 2002, the SQL Slammer virus exploited a SQL Server known vulnerability for which Microsoft had previously released a fix and even incorporated that fix into a general service pack. In the first case, SQL Server essentially had the answer to this issue, supporting both standard security as well as Windows authentication; the users simply didn’t take some very basic security steps. In the second case, Microsoft had generated a fix to a known problem but that fix wasn’t widely applied. Plus, there was another basic security issue with this incident in which one of the ports on the firewall that should have been closed was left open by the businesses that were stricken by this virus. To address these types of security challenges, SQL Sever 2005 has been designed following Microsoft’s new security framework, sometimes called SD3 where the product is secure by design, secure by default, and secure by deployment. What this means for SQL Server 2005 is that the product is initially designed with an emphasis on security. Following up on their Trustworthy Computing initiative, Microsoft embarked on extensive security training for all of their developers and conducted code reviews and performed a comprehensive thread analysis for SQL Server 2005. In addition, all of the security fixes that were incorporated into the SP3 of SQL Server 2000 were rolled into SQL Server 2005. Next, secure by default means that when the product is installed Microsoft provides secure default values in the installation process whereby if you just follow the defaults you will end up with a secure implementation. For example, in the case of the sa password, the installation process prompts you to provide a strong password for the sa account. While you can select to continue the installation with a blank password, you have to explicitly select this path as well as respond to the Microsoft dialogs warning you about the dangers of using a blank password. Finally, SQL Server 2005 is secure by deployment, which means that Microsoft is providing tools and training for customers to help create secure deployments for SQL Server 2005. Here, Microsoft provides tools like the Microsoft Baseline Security Analysis, which can scan for known security vulnerabilities, in addition to a collection of white papers that are designed to educate customers on the best practices for creating secure implementations for a variety of different deployment scenarios. Integration In today’s corporate computing environment it’s rarely the case where only one vendor’s products are installed in a homogenous setting. Instead, far more often, multiple dissimilar platforms simultaneously perform a variety of disparate tasks, and one of an organization’s main challenges is exchanging information between these different platforms. SQL Server 2005 provides a number of different mechanisms to facilitate application and platform interoperability. For application interoperability, SQL Server 2005 supports the industry standard HTTP, XML, and SOAP protocols. It also allows stored procedures to be exposed as web services and provides a level 4 Introduction xvii xviii Microsoft SQL Server 2005 Developer’s Guide JDBC driver, allowing SQL Server to be used as a back-end database for Java applications. For platform interoperability, SQL Server 2005 sports an all-new redesigned Integration Services as well as heterogeneous database replication to Access, Oracle, and IBM DB2 UDB systems. Productivity Productivity is one of the other primary ingredients that enterprises require, and this is probably the area where SQL Server 2005 has made the biggest strides. The new release of SQL Server 2005 integrates the .NET Framework CLR into the SQL Server database engine. This new integration allows database objects like stored procedures, triggers, and user-defined functions to be created using any .NET compliant language including C#, VB.NET managed C++, and J#. Prior to this release SQL Server only supported the procedural T-SQL language for database programmability. The integration of the .NET Framework brings with it a fully object-oriented programming model that can be used to develop sophisticated data access and business logic routines. Being able to write database objects using the .NET languages also facilitates the ability to easily move those database objects between the database and the data access layer of an n-tiered web application. Although the big news with this release is the .NET Framework, Microsoft has continued to enhance T-SQL, as well as bring several new capabilities to their procedural language and the reassurance to developers and DBAs that they have no plans for dropping support for T-SQL in the future. In addition, SQL Server 2005 answers the question of productivity from the DBA’s perspective as well. The management console has been redesigned and integrated into a Visual Studio .NET integrated development environment. All of the dialogs are now fully modal, allowing the DBA to easily switch between multiple management tasks. Return on Investment One of the primary challenges for IT enterprises today is driving cost out of their businesses. That often means doing more with less, and SQL Server provides the tools that most businesses need to do more with the assets they already have. SQL Server 2005 is far more than just a relational database; its tightly integrated Business Intelligence (BI) toolset, including the built-in Analysis Services and Reporting Services, brings more value to the table than any other database platform. BI gives companies the ability to analyze data and make better business decisions—decisions that can make your company money as well as save your company money. Since the release of SQL Server 7, with its integrated OLAP Services (later renamed as Analysis Services), SQL Server has become the leading product in the BI market. . new SQL Server 2005 Notification Services, SQL Server Service Broker, Reporting Services, and SQL Server Integration Services subsystems. The development management landscape for SQL Server 2005. xvii xviii Microsoft SQL Server 2005 Developer’s Guide JDBC driver, allowing SQL Server to be used as a back-end database for Java applications. For platform interoperability, SQL Server 2005 sports. in both SQL Server 2005 and Visual Studio 2005 as well as how to create both T -SQL DDL and DML solutions. Chapter 3 dives into the new SQL CLR integration capabilities of SQL Server 2005. The