M50401: Designing and Optimizing Database Solutions with Microsoft SQL Server 2008 Version: A Length: 5 Days Published: June 01, 2010 Language(s): English Audience(s): Developers Level: 300 Technology: Microsoft SQL Server 2008 Type: Course Delivery Method: Instructor-led (classroom) About this Course This five-day instructor-led course provides the knowledge and skills that IT Professionals need to design, optimize, and maintain SQL Server 2008 database. Audience Profile The audience of this course is developers who implement database solutions or perform development utilizing the programming features and functionality of SQL Server. Students taking this course are expected to have three or more years of experience working on databases for two or more of the following phases in the product lifecycle - design, development, deployment, optimization, maintenance, or support. They should possess a four-year college degree, BS or BA, in the computer field. The students should have experience in the following areas: oDeveloping databases oWriting Transact-SQL queries oDesigning, implementing and troubleshooting programming objects oDoing database performance tuning and optimization oDesigning databases at both the conceptual and logical levels oImplementing databases at the physical level oDesigning and troubleshooting the data access layer of an application oGathering business requirements At Course Completion After completing this course, students will be able to: oDesign a database design strategy oDesign a database for optimal performance oDesign security for a database oDesign programming objects oDesign queries for performance oDesign a transaction and concurrency strategy oDesign an XML strategy Before attending this course, students must have: oWorking knowledge of data storage. Specifically, they should know about row layout, fixed length field placement and varying length field placement. oKnowledge about index structures and index utilization. Specifically, they must understand the interaction between non-clustered indexes, clustered indexes and heaps. They must know why a covering index can improve performance. oHands-on database developer experience. Specifically, they should have three years of experience as a full-time database developer in an enterprise environment. oKnowledge about the locking model. Specifically, students should have an understanding of lock modes, lock objects and isolation levels and be familiar with process blocking. oUnderstanding of Transact-SQL syntax and programming logic. Specifically, students should be completely fluent in advanced queries, aggregate queries, subqueries, user-defined functions, cursors, control of flow statements, CASE expressions, and all types of joins. oKnowledge about the trade offs when backing out of the fully normalized design and designing for performance and business requirements in addition to being familiar with design models, such as Star and Snowflake schemas. They should be able to design a database to third normal form (3NF). oStrong monitoring and troubleshooting skills, including usage of monitoring tools. oBasic knowledge of the operating system and platform. That is, how the operating system integrates with the database, what the platform or operating system can do, and how interaction between the operating system and the database works. oBasic knowledge of application architecture. That is, how applications can be designed in three layers, what applications can do, how interaction between the application and the database works, and how the interaction between the database and the platform or operating system works. oKnowledge of using a data modeling tool. oKnowledge of SQL Server 2005 features, tools, and technologies. oHave a Microsoft Certified Technology Specialist: Microsoft SQL Server 2005 credential - or equivalent experience. In addition, it is recommended, but not required, that students have completed: oCourse 2779, Implementing a Microsoft SQL Server 2005 Database. oCourse 2780, Maintaining a Microsoft SQL Server 2005 Database. Course Outline Module 1: Designing a Conceptual Database Model This module explains the guidelines for designing a conceptual database model with a systematic perspective. A systematic approach involves formulating your database design process, following guidelines on how to gather and document database requirements, and following best practices when formulating a conceptual design. Finally, you will learn the guidelines for using Entity Framework. Lessons oOverview of Database Design oGathering Database Requirements oCreating a Conceptual Database Design oOverview of Entity Framework Lab : Designing a Conceptual Database Model oFormulating a Conceptual Database Design oCreating a Conceptual Database Design After completing this module, students will be able to: oExplain the key steps in the database design process. oGather database requirements. oDescribe the guidelines for creating a conceptual database design. oExplain the guidelines for creating a conceptual database design by using the Entity Framework. Module 2: Designing a Logical Database Model This module explains the best practices followed when you build a new logical database model. You will also learn the guidelines for normalization when designing an OLTP model and when designing a data warehouse database. Finally, you will learn to evaluate the existing logical model of a database. Lessons oGuidelines for Building a Logical Database Model oPlanning for OLTP Activity oEvaluating Logical Models Lab : Designing a Logical Database Model oCreating a Logical Database Model oNormalizing the Logical Database Model After completing this module, students will be able to: oExplain the guidelines for building a logical database model. oPlan for OLTP activity. oEvaluate Logical models. Module 3: Designing a Physical Database Model This module explains the guidelines to be followed when designing physical database objects and constraints. The module also covers the best practices for designing database tables and for designing data integrity. Lessons oSelecting Data Types oDesigning Database Tables oDesigning Data Integrity Lab : Designing a Physical Database Model oSpecifying Database Object Naming Standards oConverting a Logical Database Model into a Physical Database Model After completing this module, students will be able to: oDesign column data types. oDesign database tables. oDesign data integrity. Module 4: Designing Databases for Optimal Performance This module explains the considerations for designing indexes. The module also covers the guidelines for designing scalable databases, and choosing additional optimization techniques, including designing for plan guide and partition. Lessons oGuidelines for Designing Indexes oDesigning a Partitioning Strategy oDesigning a Plan Guide oDesigning Scalable Databases Lab : Designing Databases for Optimal Performance oApplying Optimization Techniques oCreating Plan Guides oDesigning a Partitioning Strategy After completing this module, students will be able to: oDesign indexes. oDesign a partitioning strategy. oDesign a plan guide. oDesign scalable databases. Module 5: Designing Security for SQL Server 2008 This module explains the best practices to be followed when designing for security in a database. The module will cover the guidelines for designing security for identity and access control, SQL development, database deployment. Finally, this module explains the guidelines for designing secure operations. Lessons oExploring Security in SQL Server 2008 oImplementing Identity and Access Control oGuidelines for Secure Development in SQL Server 2008 oGuidelines for Secure Deployment of SQL Server 2008 oGuidelines for Secure Operations Lab : Designing Security for SQL Server 2008 oDesigning Secure Development oImplementing Secure Operations oCopying an Unencrypted Database oImplementing Transparent Data Encryption oAttempting to Copy an Encrypted Database After completing this module, students will be able to: oExplore different aspects of security in SQL Server 2008. oImplement Identity and Access Control. oDescribe the guidelines for Secure development in SQL Server 2008. oDescribe the guidelines for secure deployment of SQL Server 2008. oDescribe the guidelines for secure operations. Module 6: Designing a Strategy for Database Access This module explains the best practices to be followed when designing a database access strategy. The module will cover the guidelines for designing views, stored procedures, and user defined function. Finally, this module explains the guidelines for CLR development. Lessons oGuidelines for Designing Secure Data Access oDesigning Views oDesigning Stored Procedures oDesigning User-Defined Functions Lab : Designing a Strategy for Database Access oDesigning Security for Data Retrieval Objects oDesigning Data Retrieval Objects After completing this module, students will be able to: oDescribe the guidelines for designing secure data access. oDesign views. oDesign T-SQL stored procedures. oDesign user-defined functions. Module 7: Designing Queries for Optimal Performance This module will explain the considerations for optimizing and tuning queries to improve performance. The module will cover the design considerations to refactor cursors into queries. Lessons oConsiderations for Optimizing Queries for Performance oRefactoring Cursors into Queries oExtending Set-Based Operations Lab : Designing Queries for Optimal Performance oOptimizing Query Performance oRefactoring Cursors into Queries After completing this module, students will be able to: oExplain the considerations for optimizing queries for performance. oRefactor cursors into queries. oExplain Set-Based Operations. Module 8: Designing a Transaction and Concurrency Strategy This module describes considerations and guidelines for defining a transaction strategy for a solution. It also shows the guidelines to specify isolation levels for data stores. Lessons oGuidelines for Defining Transactions oDefining Isolation Levels oGuidelines for Designing a Resilient Transaction Strategy Lab : Designing a Transaction and Concurrency Strategy oDetermining the Database Isolation Level oDetermining the Order of Object Access oDesigning Transactions After completing this module, students will be able to: oDescribe the guidelines for defining transactions. oDefine isolation levels. oDescribe the guidelines for designing a resilient transaction strategy. Module 9: Designing an XML Strategy This module describes the guidelines to design XML techniques. This module will cover the design considerations for XML storage, XQuery, XPath, and FOR XML clause. Finally, this module will cover the considerations for converting data between XML and relational formats. Lessons oDesigning XML Storage oDesigning an XML Query Strategy oDesigning a Data Conversion Strategy Lab : Designing an XML Strategy oDesigning an XML Data Storage Model oConverting Data Between XML and Relational Forms After completing this module, students will be able to: oDesign XML storage. oDesign an XML query strategy. oDesign data conversion between XML and Relational forms. Module 10: Designing SQL Server 2008 Components This module provides an overview of SQL Server 2008 architecture and the various considerations for choosing SQL Server components to be included in a solution. The module will also cover the considerations for designing service broker and full text search. Lessons oOverview of SQL Server 2008 Components oDesigning a Service Broker Architecture oDesigning the Service Broker Data Flow oDesigning the Service Broker Availability oExploring Full-Text Search oDesigning a Full-Text Search Strategy Lab : Designing SQL Server 2008 Components oAnalyzing the Organizational Needs oDesigning a Service Broker Solution Model oDesigning a Detailed Service Broker Solution oImplementing the Service Broker Solution After completing this module, students will be able to: oExamine the SQL Server 2008 architecture. oDesign a Service Broker architecture. oDesign the Service Broker data flow. oExplore full-text search. oDesign a full-text search strategy.