1 / 12

Database Design Methodologies for Microsoft SQL Server

SESSION CODE : DAT210. Database Design Methodologies for Microsoft SQL Server. Buck Woody Senior Microsoft SQL Server Specialist. buck.woody@microsoft.com http://blogs.msdn.com/buckwoody http://www.informit.com/guides/guide.aspx?g=sqlserver http://edge.technet.com/People/BuckWoody/

harris
Download Presentation

Database Design Methodologies for Microsoft SQL Server

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SESSION CODE: DAT210 Database Design Methodologies for Microsoft SQL Server Buck Woody Senior Microsoft SQL Server Specialist

  2. buck.woody@microsoft.com • http://blogs.msdn.com/buckwoody • http://www.informit.com/guides/guide.aspx?g=sqlserver • http://edge.technet.com/People/BuckWoody/ • http://facebook.com/buckwoody • http://twitter.com/buckwoody

  3. Session Description and Objectives Database design has the greatest impact on performance, reliability and security. Yet many IT professionals focus only on the physical model of the database. This session takes a simple set of requirements and decomposes the design process, using basic methodologies such as Entity Relationship Diagrams (ERD), Object-Role Modeling (ORM) and Unified Modeling Language (UML) to create an effective design. It covers the basic tools you can use for each of these approaches for SQL Server. Objective #1 Learn the process for decomposing requirements to a logical design that can be communicated to Business and Development teams. Objective #2 Understand the principals of Normalization and a simple process to Normalize. Objective #3 Understand various tools available to design and implement a database.

  4. Importance of Good Data Design Impacts Performance, Security, Storage and Integrity Design can be attributed to 50-75% of Project Issues Clear Communications with Business and Developers

  5. May be a Single Person Or Group Who Designs (and Why)? Business Person or Business Analyst • The Organization has strong talent in this area • Data viewed as a business asset • Data viewed as a “flow” pattern Developer • Mature development shop • No dedicated data staff • Formal ALM processes used DBA or Data Professional • Full-time Data Professional available • Data viewed holistically

  6. Design Process Create / Refine Business Requirements Break out Nouns Refine Nouns Define Relationships Define Datatypes Normalization A b C d 1 2 3 $ % # ^ :

  7. Design Methodologies • Object Role Modeling • (Mostly Business Analysts) • Unified Markup Language • (Mostly Developers) • Entity Relationship Diagram • (Mostly Data Professionals)

  8. Model Types • Conceptual • Platform Independent, Business Oriented, “Information Model” • Logical • Platform Independent, Flow and Developer Oriented • Physical • Platform Dependent, Performance, Sizing and Security

  9. Tools • Basic Shapes • Visio / 3rd Party Tools • Entity Framework / LINQ Note: Almost all modeling is not kept current

  10. References Link List: tinyurl.com/ycoqlvu

  11. © 2009 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

More Related