did-you-know? rent-now

Amazon no longer offers textbook rentals. We do!

did-you-know? rent-now

Amazon no longer offers textbook rentals. We do!

We're the #1 textbook rental company. Let us show you why.

9780321180599

First Look at SQL Server 2005 for Developers : 'Yukon' Beta for Developers

by ; ;
  • ISBN13:

    9780321180599

  • ISBN10:

    0321180593

  • Format: Paperback
  • Copyright: 2004-01-01
  • Publisher: Addison-Wesley Professional
  • Purchase Benefits
  • Free Shipping Icon Free Shipping On Orders Over $35!
    Your order must be $35 or more to qualify for free economy shipping. Bulk sales, PO's, Marketplace items, eBooks and apparel do not qualify for this offer.
  • eCampus.com Logo Get Rewarded for Ordering Your Textbooks! Enroll Now
List Price: $49.99

Summary

bull; Written by acknowledged experts, with unprecedented cooperation from Microsoft bull; The next version of SQL Server will be the biggest change in years, and there is a great deal of intense interest in what exactly those changes will be bull; This will enable developers to start working with the beta, so they will be ready once the final product is available

Table of Contents

Forewordp. xxi
Forewordp. xxv
Forewordp. xxvii
About the Authorsp. xxix
Prefacep. xxxi
Acknowledgmentsp. xxxvii
Introductionp. 1
The .NET Runtime and the Microsoft Platformp. 1
.NET's Effects on SQL Serverp. 3
The SQL: 1999 Standard--Extending the Relational Modelp. 8
User-Defined Types and SQL Serverp. 10
XML--Data and Document Storagep. 13
Web Services--XML as a Marshaling Formatp. 19
Client Access--And Then There Are Clientsp. 20
ObjectSpaces--Objects on the Middle Tier or Clientp. 23
Extending SQL Server into the Platform--Service Broker and Notification Servicesp. 24
Where Are We?p. 26
Hosting the Runtime: SQL Server as a Runtime Hostp. 27
Why Care How Hosting Works?p. 27
What Is a .NET Runtime Host?p. 28
SQL Server as a Runtime Hostp. 29
Loading the Runtime--Processes and AppDomainsp. 35
Safe Code--How the Runtime Makes It Safer to Run "Foreign Code"p. 37
Where the Code Lives--Storing .NET Assemblies (Create Assembly)p. 39
Assembly Dependencies--When Your Assemblies Use Other Assembliesp. 42
Assemblies and SQL Schemas--Who Owns Assemblies (Information Schema)p. 44
Maintaining User Assemblies (Alter Assembly, Drop Assembly)p. 48
Specification Compliancep. 51
Conclusionsp. 52
Where Are We?p. 52
Procedures and Functions in .NET Languagesp. 53
Extending SQL Serverp. 53
CLR Methods in SQL Serverp. 55
System.Data.SqlTypesp. 60
Proceduresp. 75
Scalar-Valued Functionsp. 81
Table-Valued Functionsp. 86
Triggersp. 92
Where Are We?p. 93
The In-Process Data Providerp. 95
The SQL Server Programming Modelp. 95
Context--The SqlContext Classp. 99
Connectionsp. 102
Commands--Making Things Happenp. 106
SqlExecutionContext and SqlDefinitionp. 110
Obtaining Resultsp. 112
Transactionsp. 115
Pipep. 121
Exception Handlingp. 123
SqlTriggerContextp. 126
Where Are We?p. 129
User-Defined Types and Aggregatesp. 131
Why Do We Need User-Defined Types?p. 131
Alias Typesp. 132
Overview of User-Defined Typesp. 133
Creating a User-Defined Typep. 135
Implementing a User-Defined Typep. 136
Implementing LDimp. 142
Should Objects Be Represented by User-Defined Types?p. 162
User-Defined Aggregatesp. 165
Where Are We?p. 173
Securityp. 175
New Security Features in SQL Server 2005p. 175
Optional Features Are Turned Off by Defaultp. 177
A Quick Review of SQL Server Security Concepts with Enhancementsp. 178
SQL Server Password Policies and Credentialsp. 186
Separation of Users and Schemasp. 189
Specifying Execution Context for Procedural Codep. 194
SQL Server Permissions and the New Objectsp. 197
Assembly Permissions--Who Can Catalog and Use an Assembly?p. 198
Permissions, Visibility, UDTs, and User-Defined Aggregatesp. 202
What Can .NET Code Do from within SQL Server: Safety Levelsp. 204
Where Are We?p. 209
T-SQL Enhancementsp. 211
Improvements to Transact-SQLp. 211
SNAPSHOT Isolationp. 212
Statement-Level Recompilationp. 222
DDL Triggersp. 226
Event Notificationsp. 231
Large Value Data Typesp. 235
T-SQL Language Enhancementsp. 236
Transaction Abort Handlingp. 263
Where Are We?p. 264
XML in the Database: The XML Data Typep. 265
The XML Data Typep. 265
Using the XML Data Type in Tablesp. 266
Using XML Data Variables and Parametersp. 271
Typed and Untyped XML--Cataloging and Using XML Schema Collectionsp. 272
Creating an Index on an XML Columnp. 282
XML Type Functionsp. 283
SELECT ... FOR XML Enhancementsp. 284
Mapping SQL and XML Data Typesp. 294
OpenXML Enhancementsp. 297
Using XMl Bulk Load inside the Databasep. 299
ANSI SQL Standard Compliancep. 300
Where Are We?p. 304
XML Query Languages: XQuery and XPathp. 305
What Is XQuery?p. 305
An Introduction to XQueryp. 307
Comparing and Contrasting XQuery and SQLp. 318
Using XQuery with the XML Data Typep. 321
XML DML--Updating XML Columnsp. 337
Special Considerations When Using XQuery inside SQL Serverp. 343
Where Are We?p. 345
SQL Server as a Platform for Web Servicesp. 347
Mixing Databases and Web Servicesp. 347
HTTP Endpoint Declarationp. 349
Endpoint Statep. 351
Parameters That Relate to Serving HTTPp. 351
Security Choices and XML Web Servicesp. 353
Defining Access through HTTPp. 358
HTTP Endpoint Metadata Viewsp. 361
XML Input and Output Types from SQL Server Web Servicesp. 361
Using the XML Data Type and Web Servicesp. 372
Accessing HTTP Endpoints with .NET Codep. 374
Where Are We?p. 381
ADO and ADO.NET Enhancementsp. 383
User-Defined Types and Relational Data Access APIsp. 383
Using .NET UDTs in ADO.NETp. 384
Fetching UDT Data from a DataReaderp. 385
Using the SqlMetaData Classp. 389
Using .NET UDTs in ODBC, OLE DB, and ADO Clientsp. 392
Supporting and XML Data Type in ADO and ADO.NET Clientsp. 399
Using the New Types with the .NET DataSet and SqlDataAdapterp. 403
Comparing the Client and Server Model for Stored Proceduresp. 407
Where Are We?p. 407
SQL Client Enhancementsp. 409
ADO.NET 2.0 and the SqlClient Data Providerp. 409
Multiple Active Resultsetsp. 413
Notification Supportp. 418
Asynchronous Supportp. 422
Snapshot Isolationp. 427
Bulk Import in SqlClientp. 429
Miscellaneous Featuresp. 432
Where Are We?p. 434
Client-Side XML: SQLXML and Mappingp. 437
The Common Query Abstractionp. 438
Mapping between Different Data Modelsp. 441
XML Queries over XML Views of Relational Datap. 448
Using XQuery Command with SQL Server or XML Documentsp. 450
Client versus SQL Server XQuery Functionalityp. 453
SqlXml Bulk Load and the SqlXmlRowsetAdapterp. 454
SqlXml DBObjectp. 456
Where Are We?p. 457
ObjectSpacesp. 459
Introduction to Object-Relational Mappingp. 459
A Simple ObjectSpaces Applicationp. 462
Data Manipulation Classes in the ObjectSpaces APIp. 469
Accessing a Database with the ObjectSpacep. 469
Patterns and Mappingp. 471
Maintaining Object Identity and Statep. 480
Reading Objects with an ObjectReaderp. 484
ObjectSetp. 486
The ObjectSpaces Query Modelp. 488
OPath Language Essentialsp. 490
Manipulating Graphs of Related Objects--Optimizationsp. 495
Beyond the ObjectSpace Class--Customizationsp. 501
Where Are We?p. 502
SQL Server Service Brokerp. 503
Messaging Applicationsp. 503
SQL Server Service Broker Overviewp. 505
Service Broker Applications Guidelinesp. 518
Service Broker Examplep. 519
Message Typep. 519
Contractsp. 523
Queuesp. 524
Servicesp. 529
Dialogsp. 531
Service Programsp. 536
Routesp. 547
Securityp. 549
Where Are We?p. 555
Notification Servicesp. 557
What Is SQL Server Notification Services?p. 557
Notification Applicationsp. 559
Components of SQl Server Notification Servicesp. 561
Notification Applications Design Patternsp. 565
Notification Services Delivery Featuresp. 566
Terms Used in Notification Servicesp. 566
Designing, Coding, and Generating a Notification Services Applicationp. 567
A Sample Notification Applicationp. 569
Instance and Application Configuration Filesp. 570
Eventsp. 580
Subscribers and Subscriptionsp. 592
Notificationsp. 600
Distributor and Formattersp. 603
Deliveryp. 605
Where Are We?p. 609
Wrap-up: Relations, XML, Objects, and Servicesp. 611
Lots of New Featuresp. 611
Data Models, Programming, and SQL Serverp. 612
Any Functionality at Any Tierp. 613
So Which Tier and What Data Model?p. 615
The Database as Part of the Platformp. 618
.NET 101p. 621
The Common Language Runtimep. 621
Assemblies and Modulesp. 624
The CLR Type Systemp. 629
Members of Typesp. 637
Memory Managementp. 641
Tools Integrationp. 645
SQL Server Management Studiop. 645
Visual Studio 2005p. 655
Bibliographyp. 663
Indexp. 665
Table of Contents provided by Rittenhouse. All Rights Reserved.

Supplemental Materials

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

Excerpts

After my last book,Essential ADO.NET, was handed in to the publisher ten days before .NET 1.0 shipped, I swore I'd never write another. To keep up with a technology while it was developing and the product features were being refined on an almost daily basis was too big an energy sink. Then, less than a year later, I caught wind of a new version of SQL Server, code-named Yukon. As with each version of SQL Server before it,since Microsoft's original 4.21 offering, there were lots of features for DBAs--high-availability features, tuning features, scalability features, andso on. A new, fast-growing field calledbusiness intelligencewas being developed,and SQL Server was on the cusp of this. The features in this business intelligence area of Yukon were truly astounding. But the biggest changes that caught my eye were those in the developer area. I was hooked. Transact-SQL has served us developers well all these years and continues to work quite well, thank you. This book lists the enhancements to this procedural dialect of SQL, and that chapter ended up to be much longer (because of the number of enhancements) than I originally thought. In the last few years, I'd been spending a lot of time in the XML space and done a lot of thinking about the differences and similarities between the XML and relational models. I liked the formal W3C standardization process for XML, slow as it seems at times. I started to investigate the ANSI SQL standards in earnest, though I'd read them before, and realized that SQL has a rich and deep foundation, starting with SQL-86 and up to the last mainstream standard, SQL-92, and past that to SQL:1999. But in 2002 there were specifications in progress to define how XML would be integrated into a relational database. There was a synergy with the XML work I'd been doing lately. I heard there would be XML functionality in Yukon, including an XML data type, XML schema validation, and an implementation of the emerging standard query language for XML, XQuery. In addition, beginning with the object-oriented graphical user interface on the NeXT computer, I'd spent a lot of the last ten years using object-oriented techniques. And Yukon promised to integrate the .NET runtime into the database engine itself. Not that SQL Server internals were to be written in .NET, but that .NET would be directly accessible as a language for stored procedures and user-defined functions. I could use object-oriented programming techniques with my database programming as well. This might be a big assist to the procedural programming in T-SQL I was already doing, in those cases where I needed it. I'd read about using object-oriented languages in the ANSI SQL specifications. Finally, there was the rumor that .NET classes might be available in SQL Server as types that the server knew about. I'd read the ANSI spec for that too. I justhadto see this product. So we had been working on writing this book since late 2002 when I met with Eric Brown in Redmond, Washington, and we got the OK and the software. Since 2002 we'd badgered the SQL Server and Webdata teams with copious questions about not only how the software worked but why it was designed that way. They were very understanding about our persistence,but sometimes I felt that I was being a bit of a pest. When we started to teach the class in earnest, we tried to pay them back with information about how software vendors and others thought the features would be useful. At that time, Niels and I were writing, and Dan was reviewing and making suggestions; however, Dan got hooked too. We almost published in the beta 1 time frame, but held back. There were too many major enhancements to the way things actually worked, and we'd written about how things worked too early. Readers would think things worked the old way instead of the improved way. And there were more enhancements coming in beta 2. We held off writing and went for another revision. We were perm

Rewards Program