Muutke küpsiste eelistusi

Practical Guide to Database Design 2nd edition [Pehme köide]

4.00/5 (1 hinnangut Goodreads-ist)
  • Formaat: Paperback / softback, 430 pages, kõrgus x laius: 254x178 mm, kaal: 760 g
  • Ilmumisaeg: 30-Jun-2020
  • Kirjastus: Chapman & Hall/CRC
  • ISBN-10: 0367571935
  • ISBN-13: 9780367571931
Teised raamatud teemal:
Practical Guide to Database Design 2nd editionSuurem pilt
  • Formaat: Paperback / softback, 430 pages, kõrgus x laius: 254x178 mm, kaal: 760 g
  • Ilmumisaeg: 30-Jun-2020
  • Kirjastus: Chapman & Hall/CRC
  • ISBN-10: 0367571935
  • ISBN-13: 9780367571931
Teised raamatud teemal:
Püsilink: https://www.kriso.ee/db/9780367571931.html
Märksõnad:

Fully updated and expanded from the previous edition, A Practical Guide to Database Design, Second Edition is intended for those involved in the design or development of a database system or application. It begins by illustrating how to develop a Third Normal Form data model where data is placed “where it belongs”. The reader is taken step-by-step through the Normalization process, first using a simple then a more complex set of data requirements. Next, usage analysis for each Logical Data Model is reviewed and a Physical Data Model is produced that will satisfy user performance requirements. Finally, each Physical Data Model is used as input to create databases using both Microsoft Access and SQL Server.



The book next shows how to use an industry-leading data modeling tool to define and manage logical and physical data models, and how to create Data Definition Language statements to create or update a database running in SQL Server, Oracle, or other type of DBMS.



One chapter is devoted to illustrating how Microsoft Access can be used to create user interfaces to review and update underlying tables in that database as well as tables residing in SQL Server or Oracle.



For users involved with Cyber activity or support, one chapter illustrates how to extract records of interest from a log file using PERL, then shows how to load these extracted records into one or more SQL Server “tracking” tables adding status flags for analysts to use when reviewing activity of interest. These status flags are used to flag/mark collected records as “Reviewed”, “Pending” (currently being analyzed) and “Resolved”. The last chapter then shows how to build a web-based GUI using PHP to query these tracking tables and allow an analyst to review new activity, flag items that need to be investigated, and finally flag items that have been investigated and resolved. Note that the book has complete code/scripts for both PERL and the PHP GUI.

Introduction xiii
Author xv
Chapter 1 Overview Of Databases 1(14)
1.1 What's A "Database"?
1(1)
1.2 Guaranteed Accuracy And Availability Of Data
2(1)
1.2.1 Atomicity
2(1)
1.2.2 Consistency
3(1)
1.2.3 Isolation
3(1)
1.2.4 Durability
3(1)
1.3 Dynamic Alteration Of Design
3(2)
1.4 Dynamic Queries-any Data, Any Time
5(1)
1.5 Referential Integrity Enforcement
6(2)
1.6 Backup/Recovery
8(1)
1.7 Failover
9(1)
1.8 Typical Installation
10(3)
Questions
13(1)
References
14(1)
Chapter 2 Data Normalization 15(26)
2.1 Introduction
15(1)
2.2 The Language Of Normalization
16(1)
2.3 Creating The Entity/Attribute List
17(3)
2.3.1 The Order Entry Model
18(2)
2.4 Cleaning Up The Entity/Attribute List
20(4)
2.4.1 Problem Type 1-synonyms
20(1)
2.4.2 Problem Type 2-homonyms
20(1)
2.4.3 Problem Type 3-redundant Information
20(1)
2.4.4 Problem Type 4-mutually Exclusive Data
21(1)
2.4.5 Problem Type 1-synonyms
21(2)
2.4.6 Problem Type 2-homonyms
23(1)
2.4.7 Problem Type 3-redundant Information
23(1)
2.4.8 Problem Type 4-mutually Exclusive Data
23(1)
2.5 Normalization
24(11)
2.5.1 First Normal Form
25(4)
2.5.1.1 Requirement 1-keys To Create Uniqueness
25(1)
2.5.1.2 Requirement 2-attributes Can Have Only One Value
26(3)
2.5.2 Second Normal Form
29(2)
2.5.3 Third Normal Form
31(4)
2.6 Creating The Data Model
35(2)
2.7 Fourth Normal Form
37(1)
2.8 Fifth Normal Form
37(2)
Questions
39(1)
References
40(1)
Chapter 3 Database Implementation 41(34)
3.1 Logical To Physical Design
41(1)
3.2 Usage Path Analysis
42(2)
3.3 Table Key And Column Data Types
44(1)
3.4 Indexes
45(1)
3.5 Table Creation
46(27)
3.5.1 Using Microsoft Access
47(9)
3.5.2 Using SQL Server
56(16)
3.5.3 Using Oracle
72(1)
Questions
73(2)
Chapter 4 Normalization And Physical Design Exercise 75(18)
4.1 Introduction
75(1)
4.2 Creating The Entity/Attribute List
75(3)
4.3 Moving To Third Normal Form
78(10)
4.4 The Physical Data Model
88(3)
Questions
91(2)
Chapter 5 The Erwin Data Modeling Tool 93(24)
5.1 What Is A Data Modeling Tool?
93(1)
5.2 Why Do I Need A Data Modeling Tool?
93(1)
5.3 Reverse Engineering
93(1)
5.4 Change Management
94(1)
5.5 Download And Install Erwin Trial Software
95(1)
5.6 Create The University Logical Data Model
96(13)
5.7 Create The University Physical Data Model
109(5)
5.8 Create An SQL Server University Database
114(1)
Questions
115(1)
Reference
116(1)
Chapter 6 Using Microsoft Access 117(40)
6.1 Overview
117(1)
6.2 Modifications To The Database Design
118(1)
6.3 Loading Data Into Tables
118(1)
6.4 Creating Queries
119(10)
6.4.1 Create A Customer-Credit_card Query
119(6)
6.4.2 Create A Query Using SQL Commands
125(1)
6.4.3 Filtering Query Results
125(4)
6.5 Using Forms
129(17)
6.5.1 Create A Form To Update Advertised_items
129(12)
6.5.2 Create A Form To Add A New Customer
141(5)
6.5.3 Generating A Master Screen For Users
146(1)
6.6 Generating Reports
146(7)
6.6.1 Using Reports To View A Customer Order
146(7)
6.7 Deploying Access For A Team Of Users
153(2)
6.7.1 Linking To An SQL Server Or Oracle Database
155(1)
6.8 The Role Of Pass-Through Queries
155(1)
Questions
156(1)
Chapter 7 Using SQL Server 157(56)
7.1 Overview
157(1)
7.1.1 Advantages
157(1)
7.1.2 Change Management For SQL Server
157(1)
7.2 Database Creation/Installation
158(12)
7.2.1 Installation Planning
158(2)
7.2.2 Software Installation
160(10)
7.3 Creating Databases
170(14)
7.3.1 Create An SQLSvrLogs Database
171(3)
7.3.2 Create The University Database
174(57)
7.3.2.1 Table Definitions
174(3)
7.3.2.2 Creating Indexes
177(3)
7.3.2.3 Index Maintenance
180(1)
7.3.2.4 Referential Integrity Constraints
180(4)
7.4 User Roles
184(2)
7.5 Authorized Users
186(4)
7.6 Backup/Recovery
190(5)
7.7 Loading Data Into Tables
195(7)
7.8 Creating Views
202(2)
7.9 Manual Queries And Edits
204(3)
7.10 Using Stored Procedures
207(1)
7.11 Using SQL Server Agent
208(2)
Questions
210(3)
Chapter 8 Using Perl To Extract And Load Data 213(18)
8.1 Why Perl?
213(6)
8.2 Perl Versus Python
219(1)
8.3 Windows Versus Unix
219(2)
8.4 Review Key Matching Features
221(1)
8.5 Monitor SQL Server Logs
222(3)
8.6 Monitoring Windows Logs
225(1)
8.7 Other Applications And Uses
226(1)
8.8 Loading Data Into Tables
227(2)
8.9 Summary
229(1)
Questions
229(1)
Reference
230(1)
Chapter 9 Building User Interfaces 231(6)
9.1 Microsoft Access In A Typical Office Environment
231(1)
9.1.1 General Capabilities
231(1)
9.1.2 Advantages
232(1)
9.1.3 Disadvantages
232(1)
9.2 Use Microsoft Access As GUI
232(1)
9.2.1 General Capabilities
232(1)
9.2.2 Advantages
232(1)
9.2.3 Disadvantages
233(1)
9.3 .Net Framework
233(1)
9.3.1 General Capabilities
233(1)
9.3.2 Advantages
233(1)
9.3.3 Disadvantages
234(1)
9.4 PHP
234(1)
9.4.1 General Capabilities
234(1)
9.4.2 Advantages
234(1)
9.4.3 Disadvantages
235(1)
9.5 Java
235(1)
9.5.1 General Capabilities
235(1)
9.5.2 Advantages
235(1)
9.5.3 Disadvantages
235(1)
Questions
235(2)
Chapter 10 Creating The University Database Application 237(38)
10.1 Create Tables For University Environment
237(4)
10.2 Create Relationships To Enforce Referential Integrity
241(3)
10.3 Design A Screen To Add New Students
244(16)
10.4 Create A Screen To Enroll Students In A Class
260(8)
10.5 Create A Screen To Assign Grades
268(3)
10.6 Create Screens To Enter Midterm And Final Grades
271(1)
10.7 Create A "Main" Menu
271(1)
10.8 Developing Applications For University Administrators
272(1)
Questions
273(2)
Chapter 11 PHP Implementation And Use 275(22)
11.1 Why PHP?
275(1)
11.2 System Components
276(3)
11.3 Design Of Web-Based Interface
279(13)
11.3.1 User Logon Options
280(1)
11.3.2 User Authentication
281(2)
11.3.3 Home Page User Options
283(1)
11.3.4 Review/Check Warning Records
283(9)
11.3.5 Review/Check Error Records
292(1)
11.4 Script Logic
292(3)
11.4.1 Warning Records Logic
292(2)
11.4.2 Error Records Logic
294(1)
Questions
295(1)
References
296(1)
Appendix A: Warning Messages 297(12)
Appendix B: Error Messages 309(12)
Appendix C: University DDL 321(84)
Appendix D: Search For Terms 405(2)
Appendix E: SQL Server Log Check 407(2)
Index 409
Rex Hogan has over 40 years experience as a database administrator and as a software engineer. This includes over 17 years of experience with Southwestern Bell/AT&T where he became their lead database specialist. During this period, he also taught various undergraduate and graduate classes at Washington Universitys Center for the Study of Data Processing in St. Louis, MO. He then worked for TRW/Northrop Grumman for 16 years, primarily as a DBA/senior software engineer where he became a specialist in the rapid design and development of database systems and applications. Finally, he worked for five years as a computer scientist for the Air Force Office of Special Investigations, where he developed computer systems to monitor usage of USAF internet traffic. He has authored and co-authored several books, including A Practical Guide to Database Design (first edition), Diagnostic Techniques for IMS DataBases,and Managing IMS Databases.