- Microsoft ® SQL Server ™ 2005. - any other use of the work is strictly prohibited. - Michael Otey is Senior Technical Editor of SQL Server Magazine and co-author of SQL Server 2000 Developer’s Guide, SQL Server 7 Developer’s Guide, and ADO.NET: The Complete Reference. - She has extensive experience developing commercial software products, and is the co-author of ADO.NET: The Complete Reference.. - SQL Server Management Studio. - The SQL Server Management Studio User Interface. - SQL Server Management Studio User Interface Windows. - SQL Server 2005 Administrative Tools. - Understanding CLR and SQL Server 2005 Database Engine. - Chapter 4 SQL Server Service Broker. - SQL Server Service Broker Architecture. - SQL Server Service Broker DDL and DML. - Enabling SQL Server Broker. - Sample SQL Server Service Broker Application. - SQL Server Service Broker Activation. - Building a .NET Subscription/Event Application. - Firing the Data Event Using .NET. - Chapter 6 Developing Database Applications with ADO.NET. - The ADO.NET Architecture. - ADO.NET Namespaces. - Namespaces for the .NET Data Providers. - Core Classes for the .NET Data Providers. - Core Classes in the ADO.NET System.Data Namespace. - Using the .NET Framework Data Provider for SQL Server. - The .NET Framework Data Provider for SQL Server Connection String Keywords. - Connecting to SQL Server. - Chapter 10 SQL Server Integration Services. - An Overview of SQL Server Integration Services. - Programming with the SQL Server Integration Services APIs. - Chapter 11 Developing BI Applications with ADOMD.NET. - ADOMD.NET Overview. - ADOMD.NET Object Model. - Building a BI Application with ADOMD.NET. - Adding a Reference for ADOMD.NET. - Connecting to the Selected SQL Server System. - 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.. - 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.. - 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. - 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. - 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 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. - SQL Server 2005 also provides an entirely new command line interface called sqlcmd that replaces the older isql and osql utilities. - All of the code presented in this book is available for download from McGraw-Hill/. - 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. - Today SQL Server is no longer a departmental database. - To meet these enterprise demands, Microsoft has designed SQL Server 2005 to be highly scalable. - 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. - 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. - 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.. - 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. - 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. - 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. - 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.. - 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 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. - 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. - 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. - 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.
Xem thử không khả dụng, vui lòng xem tại trang nguồn hoặc xem
Tóm tắt