Web site optimization - Current Head . Chapter 9: Planning and Preparation
Current Head . Chapter 9: Planning and Preparation Through Analysis This chapter analyzes a relational database model for the case study (the online auction house company) from a company operational capacity (what a company does for a living). Analysis is the process of describing what is required of a relational database model discovering what is the information needed in a database (what all the basic tables are). . Chapter 10: Creating and Refining Tables During the Design Phase This chapter describes the design of a relational database model for the case study. Where analysis describes what is needed, design describes how it will be done. Where analysis described basic tables in terms of company operations, design defines relationships between tables, by the application of normalization and Normal Form, to analyzed information. . Chapter 11: Filling in the Details with a Detailed Design This chapter continues the design process for the online auction house company case study refining fields in tables. Field design refinement includes field content, field formatting, and indexing on fields. . Chapter 12: Business Rules and Field Settings This chapter is the final of four chapters covering the case study design of the relational database model for the online auction house company. Business rules application to design encompasses stored procedures, as well as specialized and very detailed field formatting and restrictions. . Part IV: Advanced Topics Part IV contains a single chapter that covers details on advanced database structures (such as materialized views), followed by brief information on hardware resource usage (such as RAID arrays). . Appendices Appendix A contains exercise answers for all exercises found at the end of many chapters ion this book. Appendix B contains a single Entity Relationship Diagram (ERD) for many of the relational database models included in this book. What You Need to Use This Book This book does not require the use on any particular software tool either database vendor-specific or front-end application tools. The topic of this book is relational database modeling, meaning the content of the book is not database vendor-specific. It is the intention of this book to provide non-database vendor specific subject matter. So if you use a Microsoft Access database, dBase database, Oracle Database, MySQL, Ingres, or any relational database it doesn t matter. All of the coding in this book is written intentionally to be non-database specific, vendor independent, and as pseudo code, most likely matching American National Standards Institute (ASNI) SQL coding standards. You can attempt to create structures in a database if you want, but the scripts may not necessarily work in any particular database. For example, with Microsoft Access, you don t need to create scripts to create tables. Microsoft Access uses a Graphical User Interface (GUI), allowing you to click, drag, drop, and type in table and field details. Other databases may force use of scripting to create tables. The primary intention of this book is to teach relational database modeling in a step-by-step process. It is not about giving you example scripts that will work in any relational database. There is no such thing as universally applicable scripting even with the existence of ANSI SQL standards because none of the relational database vendors stick to ANSI standards. xx Introduction
You need excellent and relaible webhost company to host your web applications? Then pay a visit to Inexpensive Web Hosting services.