没有合适的资源?快使用搜索试试~ 我知道了~
首页数据库原理与SQL汉化复习指南:应用与设计
数据库原理与SQL汉化复习指南:应用与设计
需积分: 0 0 下载量 11 浏览量
更新于2024-07-01
收藏 20.1MB PDF 举报
本资源是一份针对数据库系统的教材汉化资料,由咸鱼咸等多位作者合作完成,遵循Creative Commons Attribution-NonCommercial-ShareAlike (CC BY-NC-SA)协议。教材覆盖了数据库系统原理的基础知识和实践应用,共分为三章。 第一章主要介绍了数据库的基础概念,包括课程目标和数据库的特征。章节详细讨论了单用户和多用户数据库应用,以及电子商务背景下数据库的应用。这部分强调了数据库系统由数据库应用程序、DBMS(数据库管理系统)和数据库本身构成。个人数据库系统如Microsoft Access与企业级数据库系统,如用于企业级应用的数据库系统,进行了对比。数据库设计是本章的重要内容,涉及现有数据的设计、新系统开发和数据库的重新设计。 第二章着重于SQL语言的介绍,这是数据库操作的核心工具。章节目标是让学生理解SQL语言的背景和分类,以及如何通过CapeCodd Outdoor Sports数据集进行实际操作,如提取零售数据和理解完整的数据提取模式。SQL的使用,包括基础的SELECT-FROM-WHERE语法,以及如何在MySQL环境下执行和保存查询。 第三章深入探讨SQL的技巧,不仅限于基本查询,还包括如何对单个表进行复杂的查询,以及在MySQLWorkbench中提交和运行SQL语句。这部分内容对于掌握SQL的实际运用非常关键。 通过这份教材,读者可以系统地学习数据库系统的基础理论,了解SQL语言的操作方法,并能在实践中提升数据库管理技能。无论是初学者还是进阶者,都能从中找到适合的学习材料。
资源详情
资源推荐
In all but the simplest system development projects, the step from user requirements to
database design is too big. Accordingly, the development team proceeds in two steps.
First, the team creates a data model from the requirements statements and then
transforms that data model into a database design. You can think of a data model as a
blueprint that is used as a design aid on the way to a database design, which is the basis
for constructing the actual database in a DBMS product.
在除最简单的系统开发项目之外的所有项目中,从用户需求到数据库设计的步骤跨度都太大了。 因此,开发团队
分两个步骤进行。
首先,团队根据需求声明创建数据模型,
然后,将该数据模型转换为数据库设计。
您可以将数据模型视为一个蓝图,该蓝图可以用作数据库设计过程中的设计辅助,这是在DBMS产品中构建实际数
据库的基础。
1.6.3. 数据库重新设计
c. Database Redesign
Database redesign also requires that databases are designed. As shown in Figure 1-22,
there are two common types of database redesign.
该方式还需要设计数据库。 如图1-22所示,有两种常见的数据库重新设计类型。
In the first, a database is adapted to new or changing requirements. This process
sometimes is called database migration. In the migration process, tables may be created,
modified, or removed; relationships may be altered; data constraints may be changed; and
so forth.
The second type of database redesign involves the integration of two or more databases.
This type of redesign is common when adapting or removing legacy systems. It is also
common for enterprise application integration, when two or more previously separate
information systems are adapted to work with each other.
在第一种设计类型,数据库适应新的或不断变化的需求。 此过程有时称为数据库迁移。 在迁移过程中,可以创
建,修改或删除表。 关系可能会改变,数据约束可能会改变等等。
数据库重新设计的第二种类型涉及两个或多个数据库的集成。 适应或删除旧系统时,这种重新设计很常见。 当两
个或多个以前分开的信息系统相互配合工作时,企业应用程序集成也很常见。
1.7. 本课程要学习的内容
略
1.8. 数据库处理简史
Database processing emerged around 1970 and has been continuously evolving and
changing since then. This continual change has made it a fascinating and thoroughly
enjoyable field in which to work. Figure 1-25 summarizes the major eras of database
processing.
数据库处理始于1970年左右,自那时以来一直在不断发展和变化。 这种持续的变化使它成为一个引人入胜且令人
愉悦的工作领域。 图1-25总结了数据库处理的主要时代。
1.8.1. 早期
a. The Early Years
The need for data integration drove the development of the first database technology.
By 1973, several commercial DBMS products had emerged. These products were in use by
the mid-1970s. The DBMS products: ADABAS, System2000, Total, IDMS, and IMS. Of those
five, only ADABAS and IMS are still in use, and neither of them has substantial market share
today.
Those early DBMS products varied in the way that they structured data relationships.
数据集成的需求推动了第一个数据库技术的发展。
到1973年,出现了几种商业DBMS产品。 这些产品在1970年代中期开始使用。 DBMS产品:ADABAS,
System2000,Total,IDMS和IMS。 在这五种产品中,只有ADABAS和IMS仍在使用中,它们在今天并没有占据可
观的市场份额。
那些早期的DBMS产品在结构化数据关系方面的方式各不相同。
1.8.2. 关系模型的出现和主导
b. The Emergence and Dominance of the Relational Model
In 1970, a then–little-known IBM engineer named E. F. Codd published a paper in the
Communications of the ACM3 in which he applied the concepts of a branch of
mathematics called relational algebra to the problem of “shared data banks,” as
databases were then known.
The results of this work are now the relational model for databases, and all relational
database DBMS products are built on this model.
1970年,当时名不经传的IBM工程师E.F. Codd在ACM3通讯中发表了一篇论文,其中他将数学上一个称为关系代
数的分支概念应用于“共享数据库”问题
这项工作的结果现在是数据库的关系模型,并且所有关系数据库DBMS产品都建立在该模型上。
Over time, Codd convinced IBM management to develop relational-model DBMS products.
The result was IBM’s DB2 and its variants, which are still very popular today.
Meanwhile, other companies were considering the relational model as well, and by 1980,
several more relational DBMS products had been released. The most prominent and
important of those was Oracle Corporation’s Oracle Database . Oracle Database achieved
success for many reasons, one of which was that it would run on just about any computer
and just about any operating system.
随着时间的流逝,科德说服IBM管理层开发关系模型DBMS产品。 结果就是IBM的DB2及其变体,今天仍然非常流
行。
同时,其他公司也在考虑关系模型,到1980年,又发布了更多关系DBMS产品。 其中最突出和最重要的是Oracle
Corporation的Oracle Database。 Oracle数据库之所以获得成功,有很多原因,其中之一就是它可以在几乎任何
计算机和任何操作系统上运行。
1.8.3. 关系后发展
c. Post-Relational Developments
By 1990, some vendors had developed object-oriented DBMS (OODBMS or ODBMS)
products. These products were designed to make it easy to store the data encapsulated in
OOP objects.
Several special-purpose OODBMS products were developed, and Oracle added OOP
constructs to Oracle to enable the creation of a hybrid (混合) called an object-relational
DBMS.
到1990年,一些供应商已经开发了面向对象的DBMS(OODBMS或ODBMS)产品。 这些产品旨在简化存储在
OOP对象中的数据的存储。
也开发了几种专用的OODBMS产品,并且Oracle向Oracle添加了OOP构造,以支持创建对象关系DBMS。
OODBMS never caught on, and today that category(类别) of DBMS products is fading
away.There were two reasons for their lack of acceptance.
First, using an OODBMS required that the relational data be converted from relational
format to object-oriented format. By the time OODBMS emerged, billions upon billions of
bytes of data were stored in relational format in organizational databases. No company
was willing to undergo the expensive travail of converting those databases to be able to
use the new OODBMS.
Second, object-oriented databases had no substantial advantage over relational databases
for most commercial database processing. As you will see in the next chapter, SQL is not
object oriented. But it works, and thousands of developers have created programs that use
it.
Conclusion: Without a demonstrable advantage over relational databases, no organization
was willing to take on the task of converting its data to OODBMS format.
OODBMS从未流行开来,如今,DBMS产品的类别(类别)正在逐渐消失。它们缺乏接受的原因有两个。
首先,使用OODBMS要求将关系数据从关系格式转换为面向对象的格式。 到OODBMS出现时,数十亿亿字节的
数据以关系格式存储在组织数据库中。 没有一家公司愿意为将这些数据库转换为能够使用新的OODBMS而付出昂
贵的代价。
其次,对于大多数商业数据库处理而言,面向对象的数据库相比关系数据库并没有实质性的优势。 正如将在下一
章中看到的那样,SQL不是面向对象的。 但是它有效,成千上万的开发人员创建了基于它的程序。
结论:在关系数据库上没有明显优势的情况下,没有组织愿意承担将其数据转换为OODBMS格式所带来的代价。
Meanwhile, the Internet took off. By the mid-1990s, it was clear that the Internet was one
of the most important phenomena in history. It changed, forever, the ways that customers
and businesses relate to each other.
Early Web sites were nothing more than online brochures(小册子), but within a few years,
dynamic(动态) Web sites that involved querying and processing databases began to
appear.
However, one substantial problem existed. HTTP(Hypertext Transfer Protocol ) is a
stateless protocol(无状态协议); (进一步解释何谓无状态协议)a server receives a request
from a user, processes the request, and then forgets about the user and the request. Many
database interactions are multistage(多级). A customer views products, adds one or
more to a shopping cart, views more products, adds more to the shopping cart, and
eventually checks
out. A stateless protocol cannot be used for such applications.
同时,互联网开始腾飞。到1990年代中期,互联网已明显的成为历史上最重要的现象之一。 它永远改变了客户和
企业之间相互联系的方式。
早期的网站只不过是网上小册子,而是在短短几年内,出现了涉及查询和处理数据库的动态网站。
但是,存在一个实质性的问题。 HTTP(超文本传输协议)是无状态协议; 服务器收到用户的请求,处理该请
求,然后忘记用户和该请求。 然而许多数据库交互是多阶段的。 客户查看产品,将一个或多个添加到购物车,查
看更多产品,将更多添加到购物车,最后结帐。 无状态协议不能用于此类应用程序。
剩余177页未读,继续阅读
AshleyK
- 粉丝: 22
- 资源: 315
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- 计算机人脸表情动画技术发展综述
- 关系数据库的关键字搜索技术综述:模型、架构与未来趋势
- 迭代自适应逆滤波在语音情感识别中的应用
- 概念知识树在旅游领域智能分析中的应用
- 构建is-a层次与OWL本体集成:理论与算法
- 基于语义元的相似度计算方法研究:改进与有效性验证
- 网格梯度多密度聚类算法:去噪与高效聚类
- 网格服务工作流动态调度算法PGSWA研究
- 突发事件连锁反应网络模型与应急预警分析
- BA网络上的病毒营销与网站推广仿真研究
- 离散HSMM故障预测模型:有效提升系统状态预测
- 煤矿安全评价:信息融合与可拓理论的应用
- 多维度Petri网工作流模型MD_WFN:统一建模与应用研究
- 面向过程追踪的知识安全描述方法
- 基于收益的软件过程资源调度优化策略
- 多核环境下基于数据流Java的Web服务器优化实现提升性能
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功