Contents Overview 1 Introduction to Data Services 2 SQL Server 5 Active Directory 12 Demonstration: Active Directory 16 Logical Design of Data Services 22 Physical Design of Data Services 23 Market Purchasing 27 Best Practices 30 Lab 10: Data Services 31 Review 35 Module 10: Data Services Information in this document is subject to change without notice. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted. Complying with all applicable copyright laws is the responsibility of the user. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation. If, however, your only means of access is electronic, permission to print one copy is hereby granted. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.  2000 Microsoft Corporation. All rights reserved. Microsoft, Active Directory, ActiveX, BackOffice, BizTalk, FrontPage, Microsoft Press, MSDN, MS-DOS, PowerPoint, Visio, Visual Basic, Visual C++, Visual InterDev, Visual J++, Visual Studio, Win32, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. Program Managers: Rhy Mednick, Susie Parrent Instructional Designer: Susie Parrent Subject Matter Experts: David Chesnut, Sam Gill (TechnoWiz), Michel Pahud Media Management: David Mahlmann Editing Manager: Lynette Skinner Editor: Mick Alberts, Jennifer Linn Production Manager: Miracle Davis Print Coordinators: Linda Lu Cannon (Write Stuff), Marlene Lambert (Online Training Solutions, Inc.) Build Coordinator: Eric Wagoner Graphic Artist: Scott Serna Test Lead: Eric Myers Manufacturing Manager: John Williams Group Product Manager: Juan Fernando Rivera Lead Product Manager, System Services and Infrastructure: Edward Dudenhoefer Manufacturing Manager: Rick Terek Operations Coordinator: John Williams Manufacturing Support: Laura King; Kathy Hershey Lead Product Manager, Release Management: Bo Galford Group Manager, Courseware Infrastructure: David Bramble General Manager: Robert Stewart Module 10: Data Services iii Instructor Notes This module provides students with an introduction to data services. Every enterprise application needs to save data in a data store. In this module, two types of data stores are considered: relational and hierarchical. After completing this module, students will be able to: ! Identify the important features of a data service, and in particular those of Microsoft ® SQL Server ™ and Active Directory ™ . ! Describe storage and retrieval for data services. ! Describe how a data service works with data. ! Describe how a data service maintains data integrity. ! Describe how a data service handles distribution. ! Describe the physical design of a data services layer and how to apply technologies to implement it. Materials and Preparation This section provides the materials and preparation tasks that you need to teach this module. Required Materials To teach this module, you need the following materials: ! Microsoft PowerPoint ® file 1910A_10.ppt ! Module 10: Data Services ! Lab 10: Data Services Preparation Tasks To prepare for this module, you should: ! Read all of the materials for this module. ! Complete the lab. Presentation: 75 Minutes Lab: 30 Minutes iv Module 10: Data Services Module Strategy Use the following strategy to present this module: ! Introduction to Data Services The purpose of this section is to introduce students to the data services layer. The purpose of the data services layer is to facilitate the storage of data on different types of data storage providers. In this module, you will introduce students to two types of storage capabilities: relational and hierarchical. Emphasize to students that these are not the only two types of data service providers. Examples of other data service providers are online analytical processing (OLAP) server for data warehousing and Microsoft Exchange for workflow application storage. ! SQL ServerThe purpose of this section is to review with students the salient features of SQL Server. In the topic “SQL Server Storage and Retrieval,” emphasize that denormalizing is one of the key physical design activities associated with relational database design. To improve retrieval performance, you would denormalize your table structure. ! Active DirectoryThe purpose of this section is to review with students the salient features of Active Directory. The first two topics in this section explain the requirements of hierarchical data storage and how the Active Directory design meets those requirements. This section contains a demonstration of two utility applications that allow Active Directory browsing. The first utility, ADSVW, allows browsing of the Active Directory schema, while the second utility, ADSIEdit, allows browsing and modification of Active Directory objects. ! Logical Design of Data ServicesThe purpose of this topic is to point out to students that while there are not currently design patterns that apply to the logical design of data services, there are other models that can facilitate the logical design of data services. ! Physical Design of Data servicesThe purpose of this section is to describe the key considerations in the physical design of SQL Server and Active Directory. The first topic in this section provides some general guidelines about when one type of data store is preferred over the other (relational vs. hierarchical). ! Market Purchasing The purpose of this section is to discuss the logical and physical designs of the data services layer of Market Purchasing and to explain the choices made. The logical design of the relational data services is reflected in an entity relationship diagram (ERD). The logical design of the hierarchical data services is presented as a schema. You can use the SQL Server Enterprise Manager to open the Market Purchasing database and show students the actual implementation for the physical design. Using the Enterprise Manager, you can show how the tables are designed and how the constraints and indexes are configured. Module 10: Data Services v ! Best Practices There are four important best practices associated with data services: • The logical design should specify SQL Server as the preferred data service for relational, volatile data. All volatile entities, such as requisitions, vendors, and so on, are stored on a database data service provider. • The logical design should specify Active Directory as the preferred data service for hierarchical, non-volatile data. Non-volatile, highly redundant data sets such as requestor are stored in Active Directory. • The physical design of the SQL Server data service should use stored procedures for data set retrieval and data modification. The physical design should also use triggers to maintain data integrity. • The design of an Active Directory schema should include both a class design and an object design. While defining a class design is a requirement, defining an object design allows the Active Directory services to better index the directory to enable faster searches. Lab Strategy ! Lab 10: Data Services The purpose of Lab 10 is for students to experiment with designing a specialized query. The query is a hierarchical query that will require the Data Shape Provider to implement the query in the physical design. The physical design is the hardest part of the lab because students must derive the query to pass to the Data Shape Provider. Microsoft MSDN ® Library provides documentation for creating Data Shape Provider queries. However, it is also acceptable for students to use a pseudocode solution. Discuss with students their answers to Lab 10. Module 10: Data Services 1 # ## # Overview ! Introduction to Data Services ! SQL Server ! Active Directory ! Logical Design of Data Services ! Physical Design of Data Services ! Market Purchasing ! Best Practices In this module, you will learn about the data services layer. This module focuses primarily on Microsoft ® SQL Server ™ and Active Directory ™ as two key technologies of a data services layer. After completing this module, you will be able to: ! Identify the important features of a data service, and in particular those of SQL Server and Active Directory. ! Describe storage and retrieval for data services. ! Describe how a data service works with data. ! Describe how a data service maintains data integrity. ! Describe how a data service handles distribution. ! Describe the physical design of a data services layer and how to apply technologies to implement it. Topic Objective To provide an overview of the module topics and objectives. Lead-in In this module, you will learn about the data services layer and how to create a physical design for it. 2 Module 10: Data Services # ## # Introduction to Data Services ! The Business Problem ! Business Requirements The data services layer objects and business logic objects allow the data access layers to retrieve and modify data from the underlying data storage systems. In this section, the data services layer will be placed in the proper context of the business problem. This discussion will be followed by a presentation on the business requirements of a data services layer. Topic Objective To provide an overview of the section topics and objectives. Lead-in In this section, you will learn what makes up a data service. Module 10: Data Services 3 The Business Problem Data Access Layer Connected Business Logic Layer Disconnected Business Logic Layer Facade Layer Web Services Facade Business Facade Transactional DAL Nontransactional DAL User Services Data Services The data services layer is accessed by the transactional or nontransactional data access layer (DAL). The data services layer consists of data service providers that provide many services, including data definition, data manipulation and retrieval, logging, archiving, transactions, and so forth. The data services components are the requests for services that are initiated by the DAL components and passed to the data service providers. A data service provider processes the request and returns a result to the DAL. In this module, you will learn about the characteristics of these requests as they pertain to different types of data service providers. Topic Objective To provide background about the business problem. Lead-in In this topic, you will learn about the business problem presented to designers who need to implement a data services layer. 4 Module 10: Data Services Business Requirements ! Relational ! Hierarchical The data services layer satisfies the requirements of business applications for data storage and retrieval. Specifically, the requirement is that data services provide a service beyond simple file I/O to be considered a data service. In general, two types of services can been identified as data service providers: back-end relational database servers, such as SQL Server, and hierarchical directory services that can manage application information, such as Active Directory. The next two sections of this module will explore these technologies in more detail. There are, however, other data service providers that can be used in an application, including data warehouses such as OLAP (online analytical processing) Server and electronic mail data stores such as Microsoft Exchange Server. These types of data stores might not be applicable to a general type of business application and therefore are not discussed in detail in this course. In SQL Server 2000, the name OLAP Server has been changed to Analysis Services. For more information about using data warehouses, see Course 1502B, Designing and Implementing a Data Warehouse Using Microsoft SQL Server 7.0. For more information about using workflow, see Course 1593A, Building Collaborative Solutions by Using Microsoft Outlook 2000 and Course 2017A, Creating Digital Dashboards. Mail data stores are applicable to general business applications when used for sending messages. For example, the Market Purchasing application is designed to send e-mail messages to managers to let them know that there are requisitions awaiting approval. However, for simplicity, the Market Purchasing sample does not currently implement e-mail delivery. Topic Objective To provide information about the business requirements of data services. Lead-in In this topic, you will learn about the two types of business requirements: relational and hierarchical. Note Note [...]... Directory service closest to its node 22 Module 10: Data Services Logical Design of Data Services Topic Objective To provide information about the logical design of data services Lead-in In this topic, you will learn about data modeling, which is of primary importance to data services ! Data Modeling ! Schema The first thing that you should note with respect to the data services layer is that there are no... both relational data and hierarchical data In the case of hierarchical data modeling, the result is typically a schema for the hierarchical structure Module 10: Data Services # Physical Design of Data Services Topic Objective To provide information about the physical design of data services Lead-in In this section, you will learn about the key considerations in the physical design of data services ! General... says that 20 percent of the data is accessed 80 percent of the time Specifically, the 20 percent of the data that is frequently accessed is the current data Separating older data, by archiving it, from current data can enhance the performance of a physical design 8 Module 10: Data Services Using SQL Server to Work with Data Topic Objective To provide a review of working with data ! Lead-in In this topic,... the data 9 10 Module 10: Data Services Data Integrity Topic Objective To provide an overview of data integrity ! In this topic, you will learn how to create a physical design with data integrity Constraints ! Lead-in Triggers In the physical design of a database, include data integrity: the rules that govern the consistency and accuracy of the data In general, there are four types of data integrity:... design of a data service There are, however, other models that facilitate the logical design of data services For further information on data modeling, refer to Course 1609A, Designing Data Services and Data Models All of the data models are based on an approach that focuses on defining the data entities, defining their attributes, and defining the relationships between entities The result of data modeling... general observations regarding the choice of a data services provider: relational vs hierarchical, and dynamic structures 23 24 Module 10: Data Services General Considerations Topic Objective To provide some general physical design considerations for data services Lead-in In this topic, you will learn the general physical design considerations for data services ! Relational vs Hierarchical ! Dynamic... unnecessary Module 10: Data Services 25 SQL Server Key Considerations Topic Objective To provide an overview of the key considerations for the physical design of database data services that use SQL Server ! ! In this topic, you will learn the key physical design issues of data services that use SQL Server Performance ! Lead-in Volatility Reliability The key considerations for the physical design of a database... Purchasing data services ! Market Purchasing Logical Design ! Market Purchasing Physical Design In this section, you will learn how the logical and physical design guidelines were applied to the data services layer of Market Purchasing 27 28 Module 10: Data Services Market Purchasing Logical Design Topic Objective To provide an overview of the logical design for the Market Purchasing data services Lead-in... defined for maintaining data consistency Module 10: Data Services 11 SQL Server Distribution Topic Objective To provide an overview of data distribution Lead-in ! In this topic, you will learn the key physical design issues of data distribution Transactional Replication $ ! Snapshot Replication $ ! Use when data modification can be separated from data retrieval Use for data- sensitive information Merge Replication... business logic or DAL components to ensure high reliability 26 Module 10: Data Services Active Directory Key Considerations Topic Objective To provide an overview of the key considerations for the physical design of database data services that use Active Directory ! ! In this topic, you will learn the key physical design issues of data services that use Active Directory Availability ! Lead-in Performance . 30 Minutes iv Module 10: Data Services Module Strategy Use the following strategy to present this module: ! Introduction to Data Services The. Module 10: Data Services 1 # ## # Overview ! Introduction to Data Services ! SQL Server ! Active Directory ! Logical Design of Data Services ! Physical