没有合适的资源?快使用搜索试试~ 我知道了~
首页数据库设计与新技术应用:逻辑设计指南(第五版)
数据库设计与新技术应用:逻辑设计指南(第五版)
需积分: 16 3 下载量 72 浏览量
更新于2024-07-24
收藏 3.28MB PDF 举报
"《数据库建模与设计:逻辑设计第五版》是一本深度讲解数据库系统管理和设计技术的重要参考书籍。它在新的技术和商业需求背景下,详细探讨了如何构建和设计数据库应用。在本书中,读者可以了解到: 1. 关系数据模型和SQL系统的核心:第五版强调了关系数据模型在商业应用中的主导地位,特别是对于那些使用SQL(结构化查询语言)的系统,提供了清晰的解释和实用的设计规则。 2. 扩展技术的应用:除了基本的数据库系统,书中还涵盖了数据仓库(Data Warehousing)、在线分析处理(OLAP)以及数据挖掘等现代技术,帮助设计师理解如何在大规模企业数据整合中运用这些技术。 3. 实操案例与成长路径:书中提供了丰富的实例和实际案例研究,不仅适合初学者学习基础设计原则,也适合经验丰富的设计师开发大型工业级系统,通过实例引导读者从新手到专家的转变。 4. 全面的信息模型和设计指南:涵盖了UML(统一建模语言)和XML(可扩展标记语言)等多种建模工具,确保设计的通用性。 5. 面向现实世界的实用价值:无论是在企业知识管理、业务流程变化,还是IT服务管理等领域,这本书都能为创建大型企业数据模型提供即时可用的指导。 6. 专业作者阵容:作者团队包括业内知名专家,如Joe Celko、Terry Halpin、Tony Morgan等人,他们的经验和洞察力使得本书内容权威且深入。 《数据库建模与设计:逻辑设计第五版》是一本综合性和实践性强的资源,无论是对数据库初学者还是经验丰富的设计师,都是提升数据库设计技能、适应技术变迁的理想选择。"
资源详情
资源推荐
a. Conceptual data modeling. The data requirements are
analyzed and modeled by using an ER or UML dia-
gram that includes many features we will study in
Chapters 2 and 3, for example, semantics for optional
relationships, ternary relationships, supertypes, and
subtypes (categories). Processing requirements are
typically specified using natural language expressions
or SQL commands along with the frequency of occur-
rence. Figure 1.2 (S
tep II.a) shows a
possible ER
Information Requirements
Determine requirements
Logical Design
[multiple views]
Model Integrate views
[single view]
Transform to SQL tables
Normalize
Physical Design
Select indexes
[special requirements]
Denormalize
[else]
Implementation
Implement
[else]
Monitor and detect changing requirements
[defunct]
Figure 1.1 The database life
cycle.
4 Chapter 1 INTRODUCTION
model representation of the product/customer data-
base in the mind of the end user.
b. View integration. Usually, when the design is large and
more than one person is involved in requirements anal-
ysis, multiple views of data and relationships occur,
resulting in inconsistencies due to variance in taxon-
omy, context, or perception. To eliminate redundancy
and inconsistency from the model, these views must
Customers
Retail
salesperson
view
Customer view
Integration of retail salesperson’s and customer’s views
customer
customer
customer
N
1
N
N
N
N
11
1N
for
places
places
order
order
orders
salesperson
1N
N
NN
N
product
product
fills-out
sold-by
served-by
served-by
Products
Orders
Salespersons
Database Life Cycle
Step I Information Requirements (reality)
Step II Logical design
Step II.b View integration
Step II.a Conceptual data modeling
salesperson
Figure 1.2 Life cycle
results, step by step
(continued on following
page).
Chapter 1 INTRODUCTION 5
be “rationalized” and consolidated into a single global
view. View integration requires the use of ER semantic
tools such as identification of synonyms, aggregation,
and generalization. In Figure 1.2 (Step II.b), two possi-
ble views of the product/customer database are merged
into a single global view based on common data for
customer and order. View integration is also important
when applications have to be integrated, and each may
be written with its own view of the database.
Step II.c Transformation of the conceptual data model to SQL tables
Step II.d Normalization of SQL tables
Step III Physical Design
create table customer
Customer
Decomposition of tables and removal of update anomalies.
Salesperson SalesVacations
Product
Salesperson
sales-name
Order Order-product
order-no
order-no
sales-name cust-no
prod-no
addr job-leveldept
sales-name addr
Indexing
Clustering
Partitioning
Materialized views
Denormalization
job-leveldept
vacation-days
vacation-daysjob-level
cust-no
prod-no prod-name qty-in-stock
cust-name
..........
(cust
–
no integer,
cust
–
name char(15),
cust
–
addr char(30),
sales
–
name char(15),
prod
–
no integer,
primary key (cust
–
no),
foreign key (sales
–
name)
references salesperson,
foreign key (prod
–
no)
references product):
Figure 1.2, cont’d
Further life cycle results,
step by step.
6 Chapter 1 INTRODUCTION
c. Transformation of the conceptual data model to SQL
tables. Based on a categorization of data modeling con-
structs and a set of mapping rules, each relationship
and its associated entities are transformed into a set of
DBMS-specific candidate relational tables. We will
show these transformations in standard SQL in Chapter
5. Redundant tables are eliminated as part of this pro-
cess. In our example, the tables in Step II.c of Figure 1.2
are the r
esult of transformation of the integrated ER
model in Step II.b .
d. Norm
aliza tion of tables. Given a
table (R), a set of
attributes (B) is functio nally dependent on another
set of attributes (A) if, at each instant of time, each
A value is associated with exactly one B value. Func-
tional dependencies (FDs) are derived from the con-
ceptual d ata m ode l d iagra m a nd the semantics of
data relationships in the requirements analy sis. They
represent the dependencies among data elements
that are unique i dent ifiers (keys ) of e ntiti es. Addi-
tional FDs, which repre sen t the dependencies
between key and nonkey attributes within entities,
canbederivedfromtherequirementsspecification.
Candidate relational tables associated with all
derived FDs are normalized (i.e., modified by
decomposing or spli tting tables into smaller tables)
using standard normalization techniques. Finally,
redundancies in the data that occur in normalized
candidate tables are analyzed further for possibl e
elimination, with the constraint that data integrity
must be preserved. An example of normalization of
the Salesperson table into the new Salesperson and
SalesVacations tables is shown in
Figure 1.2 from
S
tep II.c t
o Step II.d.
We note here that database tool vendors tend to use
the term logical model to refer to
the conceptual data
model, and they use the term physical model to refer
to the DBMS-specific implementation model (e.g.,
SQL tables). We also note that many conceptual data
models are obtained not from scratch, but from the
process of reverse engineering from an existing
DBMS-specific schema (Silberschatz et al., 2010).
Chapter 1 INTRODUCTION 7
III. Physical design. The physical design step involves the
selection of indexes (access methods), partitioning,
and clustering of data. The logical design methodology
in Step II simplifies the approach to designing large rela-
tional databases by reducing the number of data
dependencies that need to be analyzed. This is accom-
plished by inserting the conceptual data modeling and
integration steps (Steps II.a and II.b of Figure 1.2)
into
the t
raditional relational design approach. The objective
of these steps is an accurate representation of reality.
Data integrity is preserved through normalization of the
candidate tables created when the conceptual data
model is transformed into a relational model. The pur-
pose of physical design is to then optimize performance.
As part of the physical design, the global schema can
sometimes
be refined in limited
ways to reflect pro-
cessing (query and transaction) requirements if there
are obvious large gains to be made in efficiency. This
is called denormalization. It consists of selecting domi-
nant processes on the basis of high frequency, high vol-
ume, or explicit priority; defining simple extensions to
tables that will improve query performance; evaluating
total cost for query, update, and storage; and consider-
ing the side effects, such as possible loss of integrity.
This is particularly important for online analytical pro-
cessing (OLAP) applications.
IV.Database implementation, monitoring, and modifica-
tion. Once the design is completed, the database can be
created through implementation of the formal schema
using the data definition language (DDL) of a DBMS. Then
the data manipulation language (DML) can be used to
query and update the database, as well as to set up indexes
and establish constraints, such as referential integrity.
The language SQL contains both DDL and DML con-
structs; for example, the create table command represents
DDL, and the select command represents DML.
As the database begins operation, monitoring
indicates whether performance requirements are being
met. If they are not being satisfied, modifications should
be made to improve performance. Other modifications
may be necessary when requirements change or end
8 Chapter 1 INTRODUCTION
剩余334页未读,继续阅读
halfho
- 粉丝: 0
- 资源: 18
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- ASP.NET数据库高级操作:SQLHelper与数据源控件
- Windows98/2000驱动程序开发指南
- FreeMarker入门到精通教程
- 1800mm冷轧机板形控制性能仿真分析
- 经验模式分解:非平稳信号处理的新突破
- Spring框架3.0官方参考文档:依赖注入与核心模块解析
- 电阻器与电位器详解:类型、命名与应用
- Office技巧大揭秘:Word、Excel、PPT高效操作
- TCS3200D: 可编程色彩光频转换器解析
- 基于TCS230的精准便携式调色仪系统设计详解
- WiMAX与LTE:谁将引领移动宽带互联网?
- SAS-2.1规范草案:串行连接SCSI技术标准
- C#编程学习:手机电子书TXT版
- SQL全效操作指南:数据、控制与程序化
- 单片机复位电路设计与电源干扰处理
- CS5460A单相功率电能芯片:原理、应用与精度分析
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功