Buck Woody Senior Microsoft SQL Server Specialist SESSION CODE: DAT210.

Slides:



Advertisements
Similar presentations
1.
Advertisements

Systems Development Environment
Database Systems: Design, Implementation, and Management Tenth Edition
Building Better Websites Jean-Luc David Developer Advisor Microsoft Canada
Chapters 7 & 9 System Scope
Building Enterprise Applications Using Visual Studio ®.NET Enterprise Architect.
Chapter 6 Methodology Conceptual Databases Design Transparencies © Pearson Education Limited 1995, 2005.
The Microsoft Technical Roadshow 2006 Welcome and Introduction Kevin McDaniel Developer & Platform Evangelism Group Microsoft Ltd
SQL Server 2005: Analysis Services and DTS Tim Sneath Architectural Engineer, Microsoft
Lecture Fourteen Methodology - Conceptual Database Design
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Graeme Scott – Technology Solution Professional Reduce Infrastructure Costs & Increase Productivity with SQL Server 2008.
Enterprise Business Information Model Enterprise Data Services.
SQL Server Developer Tools, Codename “Juneau” Database Services Sanjay Nagamangalam Principal Program Manager SQL Server Manageability.
CSE314 Database Systems Data Modeling Using the Entity- Relationship (ER) Model Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson Ed Slide Set.
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
Database Design, Application Development, and Administration, 5 th Edition Copyright © 2011 by Michael V. Mannino All rights reserved. Chapter 2 Introduction.
Slide 12.1 © The McGraw-Hill Companies, CS 4310: Software Engineering Lecture 7 Systems Analysis Object-Oriented Design.
Modelling information systems
The Importance of Communication Effective communication techniques for data management professionals A presentation by Mike Nicewarner.
D402 Extending your LOB Solution with Microsoft EPM Larry Duff Senior Consultant Microsoft Corporation.
Integrating Security Design Into The Software Development Process For E-Commerce Systems By: M.T. Chan, L.F. Kwok (City University of Hong Kong)
Methodology - Conceptual Database Design Transparencies
Methodology Conceptual Databases Design
1 Chapter 15 Methodology Conceptual Databases Design Transparencies Last Updated: April 2011 By M. Arief
Networking ITTC with TT:CLEAR Xiaohua ZHANG Tsinghua University, Beijing, China.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
3rd Country Training, K.Subieta: System Engineering and Databases. Lecture 3, Slide 1 February 20, 2004 Lecture 3: Introduction to Software Analysis and.
DEV 303 Visual Studio "Whidbey" Enterprise Tools: Source Control and Work Item Tracking Brian Harry Product Unit Manager Microsoft Visual Studio.
Information System Development Courses Figure: ISD Course Structure.
Intro – Part 2 Introduction to Database Management: Ch 1 & 2.
Methodology - Conceptual Database Design
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
SQL Server SQL Azure Visual Studio“Quadrant” SQL Server Modeling Services Entity Framework ADO.NET“M”/EDM Data Services …
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
Visual Studio 2005 Team Edition for Software Architects: Developing Service-Oriented Systems Bill Gibson Senior Program Manager Enterprise Tools Microsoft.
Microsoft Dynamics NAV 2009 and Architecture Overview Name Title Microsoft Corporation.
Database Design – Lecture 4 Conceptual Data Modeling.
Rahul Garg National Technology Specialist Microsoft Australia SOA303.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Giles Davies Testers are from Venus.
DEV311 Delving into Visual Studio 2005 Team Edition for Software Testers Ed Glas Group Manager, Web and Load Testing Microsoft Corporation.
Jemerson Pedernal IT 2.1 FUNDAMENTALS OF DATABASE APPLICATIONS by PEDERNAL, JEMERSON G. [BS-Computer Science] Palawan State University Computer Network.
Making The Most Of RFID In Your Applications Anush Kumar DATL01 Program Manager Microsoft Corporation
EMEA Beat Schwegler Architect Microsoft EMEA HQ Ingo Rammer Principal Consultant thinktecture
Language Integrated Query Mike Taulty Developer & Platform Group Microsoft Ltd
INDEPENDENT RESEARCH ON SQL SERVER 2012 Noel Yuhanna, Principal Analyst, Forrester Research Jeffrey North, Principal Consultant, Forrester Research.
Architecting Real-World Enterprise Application. Agenda CPR - Background Challenges in the Architecture Architecture Details Q & A Summary.
2 Behind every great site, there is great data Eric Nelson Developer Evangelist Microsoft UK
Performance Testing Using VSTS Saravana Kumar Microsoft MVP, VSTS Hewlett Packard Saravana Kumar Microsoft MVP, VSTS Hewlett Packard.
2 ADO.NET Data Services for the Web Mike Flasko Program Manager, Microsoft “Project Astoria”
Building Enterprise Applications Using Visual Studio®
Roles in the Database Environment
Methodology Conceptual Databases Design
5/11/2018.
Entity- Relationship (ER) Model
DEV260 Microsoft Visual Studio 2005 Team System: Managing the Software Lifecycle with Visual Studio 2005 Team System Bindia Hallauer Senior Product Manager.
Methodology Conceptual Database Design
Get Started with Common Data Model (CDM) and PowerApps
Extensible Platform Microsoft Dynamics 365
Tech Ed 2004 © 2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express.
DAT381 Team Development with SQL Server 2005
Microsoft Connect /17/2019 9:55 PM
Jochen Seemann Program Manager Enterprise Tools Microsoft Corporation
Methodology Conceptual Databases Design
Microsoft Build /27/2019 2:26 PM © 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY,
ADO.NET Entity Framework
Building Data-Driven Applications Using "Quadrant" and "M"
Outline Context for database development Goals of database development
Presentation transcript:

Buck Woody Senior Microsoft SQL Server Specialist SESSION CODE: DAT210

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.

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

May be a Single Person Or Group Business Person or Business Analyst Developer DBA or Data Professional The Organization has strong talent in this areaThe Organization has strong talent in this area Data viewed as a business assetData viewed as a business asset Data viewed as a “flow” patternData viewed as a “flow” pattern Mature development shopMature development shop No dedicated data staffNo dedicated data staff Formal ALM processes usedFormal ALM processes used Full-time Data Professional availableFull-time Data Professional available Data viewed holisticallyData viewed holistically

1.Create / Refine Business Requirements 2.Break out Nouns 3.Refine Nouns 4.Define Relationships 5.Define Datatypes Normalization

Object Role Modeling (Mostly Business Analysts) Unified Markup Language (Mostly Developers) Entity Relationship Diagram (Mostly Data Professionals)

1.Conceptual Platform Independent, Business Oriented, “Information Model” 2.Logical Platform Independent, Flow and Developer Oriented 3.Physical Platform Dependent, Performance, Sizing and Security

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

Link List: tinyurl.com/ycoqlvu

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