数据库中英文对照外文翻译文献

数据库中英文对照外文翻译文献
数据库中英文对照外文翻译文献

中英文对照外文翻译

Database Management Systems

A database (sometimes spelled data base) is also called an electronic database , referring to any collection of data, or information, that is specially organized for rapid search and retrieval by a computer. Databases are structured to facilitate the storage, retrieval , modification, and deletion of data in conjunction with various data-processing operations .Databases can be stored on magnetic disk or tape, optical disk, or some other secondary storage device.

A database consists of a file or a set of files. The information in these files may be broken down into records, each of which consists of one or more fields. Fields are the basic units of data storage , and each field typically contains information pertaining to one aspect or attribute of the entity described by the database . Using keywords and various sorting commands, users can rapidly search , rearrange, group, and select the fields in many records to retrieve or create reports on particular aggregate of data.

Complex data relationships and linkages may be found in all but the simplest databases .The system software package that handles the difficult tasks associated with creating ,accessing, and maintaining database records is called a database management system(DBMS).The programs in a DBMS package establish an interface between the database itself and the users of the database.. (These users may be applications programmers, managers and others with information needs, and various OS programs.)

A DBMS can organize, process, and present selected data elements form the database. This capability enables decision makers to search, probe, and query database contents in order to extract answers to nonrecurring and unplanned questions that aren’t available in regular reports. These questions might initially be vague and/or poorly defined ,but people can “browse” through the database until they have the needed information. In short, the DBMS will “manage” the stored data items and assemble the needed items from the common database in response to the queries of those who aren’t programmers.

A database management system (DBMS) is composed of three major parts:(1)a storage subsystem

that stores and retrieves data in files;(2) a modeling and manipulation subsystem that provides the means with which to organize the data and to add , delete, maintain, and update the data;(3)and an interface between the DBMS and its users. Several major trends are emerging that enhance the value and usefulness of database management systems;

Managers: who require more up-to-data information to make effective decision

Customers: who demand increasingly sophisticated information services and more current information about the status of their orders, invoices, and accounts.

Users: who find that they can develop custom applications with database systems in a fraction of the time it takes to use traditional programming languages.

Organizations : that discover information has a strategic value; they utilize their database systems to gain an edge over their competitors.

The Database Model

A data model describes a way to structure and manipulate the data in a database. The structural part of the model specifies how data should be represented(such as tree, tables, and so on ).The manipulative part of the model specifies the operation with which to add, delete, display, maintain, print, search, select, sort and update the data.

Hierarchical Model

The first database management systems used a hierarchical model-that is-they arranged records into a tree structure. Some records are root records and all others have unique parent records. The structure of the tree is designed to reflect the order in which the data will be used that is ,the record at the root of a tree will be accessed first, then records one level below the root ,and so on.

The hierarchical model was developed because hierarchical relationships are commonly found in business applications. As you have known, an organization char often describes a hierarchical relationship: top management is at the highest level, middle management at lower levels, and operational employees at the lowest levels. Note that within a strict hierarchy, each level of management may have many employees or levels of employees beneath it, but each employee has only one manager. Hierarchical data are characterized by this one-to-many relationship among data.

In the hierarchical approach, each relationship must be explicitly defined when the database is created. Each record in a hierarchical database can contain only one key field and only one relationship is allowed between any two fields. This can create a problem because data do not always conform to such a strict hierarchy.

Relational Model

A major breakthrough in database research occurred in 1970 when E. F. Codd proposed a fundamentally different approach to database management called relational model ,which uses a table as

its data structure.

The relational database is the most widely used database structure. Data is organized into related tables. Each table is made up of rows called and columns called fields. Each record contains fields of data about some specific item. For example, in a table containing information on employees, a record would contain fields of data such as a person’s last name ,first name ,and street address.

Structured query language(SQL)is a query language for manipulating data in a relational database .It is nonprocedural or declarative, in which the user need only specify an English-like description that specifies the operation and the described record or combination of records. A query optimizer translates the description into a procedure to perform the database manipulation.

Network Model

The network model creates relationships among data through a linked-list structure in which subordinate records can be linked to more than one parent record. This approach combines records with links, which are called pointers. The pointers are addresses that indicate the location of a record. With the network approach, a subordinate record can be linked to a key record and at the same time itself be a key record linked to other sets of subordinate records. The network mode historically has had a performance advantage over other database models. Today , such performance characteristics are only important in high-volume ,high-speed transaction processing such as automatic teller machine networks or airline reservation system.

Both hierarchical and network databases are application specific. If a new application is developed ,maintaining the consistency of databases in different applications can be very difficult. For example, suppose a new pension application is developed .The data are the same, but a new database must be created.

Object Model

The newest approach to database management uses an object model , in which records are represented by entities called objects that can both store data and provide methods or procedures to perform specific tasks.

The query language used for the object model is the same object-oriented programming language used to develop the database application .This can create problems because there is no simple , uniform query language such as SQL . The object model is relatively new, and only a few examples of object-oriented database exist. It has attracted attention because developers who choose an object-oriented programming language want a database based on an object-oriented model. Distributed Database

Similarly , a distributed database is one in which different parts of the database reside on physically separated computers . One goal of distributed databases is the access of information

without regard to where the data might be stored. Keeping in mind that once the users and their data are separated , the communication and networking concepts come into play .

Distributed databases require software that resides partially in the larger computer. This software bridges the gap between personal and large computers and resolves the problems of incompatible data formats. Ideally, it would make the mainframe databases appear to be large libraries of information, with most of the processing accomplished on the personal computer.

A drawback to some distributed systems is that they are often based on what is called a mainframe-entire model , in which the larger host computer is seen as the master and the terminal or personal computer is seen as a slave. There are some advantages to this approach . With databases under centralized control , many of the problems of data integrity that we mentioned earlier are solved . But today’s personal computers, departmental computers, and distributed processing require computers and their applications to communicate with each other on a more equal or peer-to-peer basis. In a database, the client/server model provides the framework for distributing databases.

One way to take advantage of many connected computers running database applications is to distribute the application into cooperating parts that are independent of one anther. A client is an end user or computer program that requests resources across a network. A server is a computer running software that fulfills those requests across a network . When the resources are data in a database ,the client/server model provides the framework for distributing database.

A file serve is software that provides access to files across a network. A dedicated file server is a single computer dedicated to being a file server. This is useful ,for example ,if the files are large and require fast access .In such cases, a minicomputer or mainframe would be used as a file server. A distributed file server spreads the files around on individual computers instead of placing them on one dedicated computer.

Advantages of the latter server include the ability to store and retrieve files on other computers and the elimination of duplicate files on each computer. A major disadvantage , however, is that individual read/write requests are being moved across the network and problems can arise when updating files. Suppose a user requests a record from a file and changes it while another user requests the same record and changes it too. The solution to this problems called record locking, which means that the first request makes others requests wait until the first request is satisfied . Other users may be able to read the record, but they will not be able to change it .

A database server is software that services requests to a database across a network. For example, suppose a user types in a query for data on his or her personal computer . If the application is designed with the client/server model in mind ,the query language part on the personal computer simple sends the query across the network to the database server and requests to be notified when the data are found.

Examples of distributed database systems can be found in the engineering world. Sun’s Network Filing System(NFS),for example, is used in computer-aided engineering applications to distribute data among the hard disks in a network of Sun workstation.

Distributing databases is an evolutionary step because it is logical that data should exist at the location where they are being used . Departmental computers within a large corporation ,for example, should have data reside locally , yet those data should be accessible by authorized corporate management when they want to consolidate departmental data . DBMS software will protect the security and integrity of the database , and the distributed database will appear to its users as no different from the non-distributed database .

In this information age, the data server has become the heart of a company. This one piece of software controls the rhythm of most organizations and is used to pump information lifeblood through the arteries of the network. Because of the critical nature of this application, the data server is also the one of the most popular targets for hackers. If a hacker owns this application, he can cause the company's "heart" to suffer a fatal arrest.

Ironically, although most users are now aware of hackers, they still do not realize how susceptible their database servers are to hack attacks. Thus, this article presents a description of the primary methods of attacking database servers (also known as SQL servers) and shows you how to protect yourself from these attacks.

You should note this information is not new. Many technical white papers go into great detail about how to perform SQL attacks, and numerous vulnerabilities have been posted to security lists that describe exactly how certain database applications can be exploited. This article was written for the curious non-SQL experts who do not care to know the details, and as a review to those who do use SQL regularly.

What Is a SQL Server?

A database application is a program that provides clients with access to data. There are many variations of this type of application, ranging from the expensive enterprise-level Microsoft SQL Server to the free and open source mySQL. Regardless of the flavor, most database server applications have several things in common.

First, database applications use the same general programming language known as SQL, or Structured Query Language. This language, also known as a fourth-level language due to its simplistic syntax, is at the core of how a client communicates its requests to the server. Using SQL in its simplest form, a programmer can select, add, update, and delete information in a database. However, SQL can also be used to create and design entire databases, perform various functions on the returned information, and even execute other programs.

To illustrate how SQL can be used, the following is an example of a simple standard SQL query and a more powerful SQL query:

Simple: "Select * from dbFurniture.tblChair"

This returns all information in the table tblChair from the database dbFurniture.

Complex: "EXEC master..xp_cmdshell 'dir c:\'"

This short SQL command returns to the client the list of files and folders under the c:\ directory of the SQL server. Note that this example uses an extended stored procedure that is exclusive to MS SQL Server.

The second function that database server applications share is that they all require some form of authenticated connection between client and host. Although the SQL language is fairly easy to use, at least in its basic form, any client that wants to perform queries must first provide some form of credentials that will authorize the client; the client also must define the format of the request and response.

This connection is defined by several attributes, depending on the relative location of the client and what operating systems are in use. We could spend a whole article discussing various technologies such as DSN connections, DSN-less connections, RDO, ADO, and more, but these subjects are outside the scope of this article. If you want to learn more about them, a little Google'ing will provide you with more than enough information. However, the following is a list of the more common items included in a connection request.

Database source

Request type

Database

User ID

Password

Before any connection can be made, the client must define what type of database server it is connecting to. This is handled by a software component that provides the client with the instructions needed to create the request in the correct format. In addition to the type of database, the request type can be used to further define how the client's request will be handled by the server. Next comes the database name and finally the authentication information.

All the connection information is important, but by far the weakest link is the authentication information—or lack thereof. In a properly managed server, each database has its own users with specifically designated permissions that control what type of activity they can perform. For example, a user account would be set up as read only for applications that need to only access information. Another account should be used for inserts or updates, and maybe even a third account would be used for deletes.

This type of account control ensures that any compromised account is limited in functionality. Unfortunately, many database programs are set up with null or easy passwords, which leads to successful hack attacks.

译文

数据库管理系统介绍

数据库(database,有时拼作data base)又称为电子数据库,是专门组织起来的一组数据或信息,其目的是为了便于计算机快速查询及检索。数据库的结构是专门设计的,在各种数据处理操作命令的支持下,可以简化数据的存储,检索,修改和删除。数据库可以存储在磁盘,磁带,光盘或其他辅助存储设备上。

数据库由一个或一套文件组成,其中的信息可以分解为记录,每一记录又包含一个或多个字段(或称为域)。字段是数据存取的基本单位。数据库用于描述实体,其中的一个字段通常表示与实体的某一属性相关的信息。通过关键字以及各种分类(排序)命令,用户可以对多条记录的字段进行查询,重新整理,分组或选择,以实体对某一类数据的检索,也可以生成报表。

所有数据库(最简单的除外)中都有复杂的数据关系及其链接。处理与创建,访问以及维护数据库记录有关的复杂任务的系统软件包叫做数据库管理系统(DBMS)。DBMS软件包中的程序在数据库与其用户间建立接口。(这些用户可以是应用程序员,管理员及其他需要信息的人员和各种操作系统程序)。

DBMS可组织,处理和表示从数据库中选出的数据元。该功能使决策者能搜索,探查和查询数据库的内容,从而对在正规报告中没有的,不再出现的且无法预料的问题做出回答。这些问题最初可能是模糊的并且(或者)是定义不恰当的,但是人们可以浏览数据库直到获得所需的信息。简言之,DBMS将“管理”存储的数据项,并从公共数据库中汇集所需的数据项以回答非程序员的询问。

DBMS由3个主要部分组成:(1)存储子系统,用来存储和检索文件中的数据;(2)建模和操作子系统,提供组织数据以及添加,删除,维护,更新数据的方法;(3)用户和DBMS之间的接口。在提高数据库管理系统的价值和有效性方面正在展现以下一些重要发展趋势;

1.管理人员需要最新的信息以做出有效的决策。

2.客户需要越来越复杂的信息服务以及更多的有关其订单,发票和账号的当前信息。

3.用户发现他们可以使用传统的程序设计语言,在很短的一段时间内用数据库系统开发客户应用程序。

4.商业公司发现了信息的战略价值,他们利用数据库系统领先于竞争对手。

数据库模型

数据库模型描述了在数据库中结构化和操纵数据的方法,模型的结构部分规定了数据如何被描述(例如树,表等):模型的操纵部分规定了数据添加,删除,显示,维护,打印,查找,选择,排序和更新等操作。

分层模型

第一个数据库管理系统使用的是分层模型,也就是说,将数据记录排列成树形结构。一些记录时根目录,在其他所有记录都有独立的父记录。树形结构的设计反映了数据被使用的顺序,也就是首先访问处于树根位置的记录,接下来是跟下面的记录,等等。

分层模型的开发是因为分层关系在商业应用中普遍存在,众所周知,一个组织结构图表就描述了一种分层关系:高层管理人员在最高层,中层管理人员在较低的层次,负责具体事务的雇员在最底层。值得注意的是,在一个严格的分层结构体系中,在每个管理层下可能有多个雇员或多个层次的雇员,但每个雇员只有一个管理者。分层结构数据的典型特征是数据之间的一对多关系。

在分层方法中,当数据库建立时,每一关系即被明确地定义。在分层数据库中的每一记录只能包含一个关键字段,任意两个字段之间只能有一种关系。由于数据并不总是遵循这种严格的分层关系,所以这样可能会出现一些问题。

关系模型

在1970年,数据库研究取得了重大突破。E.F.Codd提出了一种截然不同的数据库管理方法,使用表作为数据结构,称之为关系模型.

关系数据库是使用最广的数据结构,数据被组织成关系表,每个表由称作记录的行和称作字段的列组成。每个记录包含了专用项目的字段值。例如,在一个包含雇员信息的表中,一个记录包含了像一个人姓名和地址这样的字段的值。

结构化查询语言(SQL)是一种在关系型数据库中用于处理数据的查询语言。它是非过程化语言或者说是描述性的,用户只须指定一种类似于英语的描述,用来确

定操作,记录或描述记录组合。查询优化器将这种描述翻译为过程执行数据库操作。

网状模型

网状模型在数据之间通过链接表结构创建关系,子记录可以链接到多个父记录。这种将记录和链接捆绑到一起的方法叫做指针,他是指向一个记录存储位置的存储地址。使用网状方法,一个子记录可以链接到一个关键记录,同时,它本身也可以作为一个关键记录。链接到其他一系列子记录。在早期,网状模型比其他模型更有性能优势;但是在今天,这种优势的特点只有在自动柜员机网络,航空预定系统等大容量和高速处理过程中才是最重要的。

分层和网状数据库都是专用程序,如果开发一个新的应用程序,那么在不同的应用程序中保持数据库的一致性是非常困难的。例如开发一个退休金程序,需要访问雇员数据,这一数据同时也被工资单程序访问。虽然数据是相同的,但是也必须建立新的数据库。

对象模型

最新的数据库管理方法是使用对象模型,记录由被称作对象的实体来描述,可以在对象中存储数据,同时提供方法或程序执行特定的任务。

对象模型使用的查询语言与开发数据库程序所使用的面向对象的程序设计语言是相同的,因为没有像SQL这样简单统一的查询语言,所以会产生一些问题。对象模型相对较新,仅有少数几个面向对象的数据库实例。它引起了人们的关注,因为选择面向对象程序设计语言的开发人员希望有一个基于在对象模型基础上的数据库。

分布式数据库

类似的,分布式数据库指的是数据库的各个部分分别存储在物理上相互分开的计算机上。分布式数据库的一个目的是访问数据信息时不必考虑其他位置。注意,一旦用户和数据分开,通信和网络则开始扮演重要角色。

分布式数据库需要部分常驻于大型主机上的软件,这些软件在大型机和个人计算机之间建立桥梁,并解决数据格式不兼容的问题。在理想情况下,大型主机上的数据库看起来像是一个大的信息仓库,而大部分处理则在个人计算机上完成。

分布式数据库系统的一个缺点是它们常以主机中心模型为基础,在这种模型中,大型主机看起来好像是雇主,而终端和个人计算机看起来好像是奴隶。但是这种方法

也有许多优点:由于数据库的集中控制,前面提到的数据完整性和安全性的问题就迎刃而解了。当今的个人计算机,部门级计算机和分布式处理都需要计算机之间以及应用程序之间在相等或对等的基础上相互通信,在数据库中客户机/服务器模型为分布式数据库提供了框架结构。

利用相互连接的计算机上运行的数据库应用程序的一种方法是将程序分解为相互独立的部分。客户端是一个最终用户或通过网络申请资源的计算机程序,服务器是一个运行着的计算机软件,存储着那些通过网络传输的申请。当申请的资源是数据库中的数据时,客户机/服务器模型则为分布式数据库提供了框架结构。

文件服务器指的是一个通过网络提供文件访问的软件,专门的文件服务器是一台被指定为文件服务器的计算机。这是非常有用的,例如,如果文件比较大而且需要快速访问,在这种情况下,一台微型计算机或大型主机将被用作文件服务器。分布式文件服务器将文件分散到不同的计算机上,而不是将它们集中存放到专门的文件服务器上。

后一种文件服务器的优点包括在其他计算机上存储和检索文件的能力,并可以在每一台计算机上消除重复文件。然而,一个重要的缺点是每个读写请求需要在网络上传播,在刷新文件时可能出现问题。假设一个用户申请文件中的一个数据并修改它,同时另外一个用户也申请这个数据并修改它,解决这种问题的方法叫做数据锁定,即第一个申请使其他申请处于等待状态,直到完成第一个申请,其他用户可以读取这个数据,但不能修改。

数据库服务器是一个通过网络为数据库申请提供服务的软件,例如,假设某个用户在他的个人计算机上输入了一个数据查询命令,如果应用程序按照客户机/服务器模型设计,那么这个人计算机上的查询语言通过网络传送数据库服务器上,当发现数据时发出通知。

在工程界也有许多分布式数据库的例子,如SUN公司的网络文件系统(NFS)被应用到计算机辅助工程应用程序中,将数据分散到由SUN工作站组成的网络上的不同硬盘之间。

分布式数据库是革命性的进步,因为把数据存放在被使用位置上是很合乎常理的。例如一个大公司不同部门之间的计算机,应该将数据存储在本地,然而,当被授

外文翻译-数据库管理系统—剖析

Database Management System Source:Database and Network Journal Author:David Anderson You know that a data is a collection of logically related data elements that may be structured in various ways to meet the multiple processing and retrieval needs of orga nizations and individuals. There’s nothing new about data base-early ones were chiseled in stone, penned on scrolls, and written on index cards. But now database are commonly recorded on magnetically media, and computer programs are required to perform the necessary storage and retrieval operations. The system software package that handles the difficult tasks associated with created, accessing, and maintaining database records is in a DBMS package establish an interface between the database itself and the users of the database. (These users may be applications programmers, managers and others with information needs, and various OS programmers.) A DBMS can organize, process, and present selected data elements from the database. This capability enables decision makers to search. Probe, and query data contents in order to extract answers to nonrecurring and unplanned questions that aren’t available in regular reports. These questions might initially be vague and/or poorly defined, but people can “browse” through the database until they have the needed information. In short, the DBMS will “manage” the stored data items and assemble the needed items from the common database in response to the queries of those who aren’t programmers. In a file-oriented system, users needing special information may communicate their needs to a programmers, who, when time permits, will information. The availability of a DBMS, however, offers users a much faster alternative communications patch (see figure). Special, direct, and other file processing approaches ate used to organize and structure data in single files. But a DBMS is able to integrate data elements from several files to answer specific user inquiries fir information. This means that the DBMS is able to structure and tie together the logically related data from several large files. Logical structures. Identifying these logical relationships is a job of the data administrator. A data definition language is used for this purpose. The DBMS may

SQL数据库外文翻译--数据库的工作

Working with Databases This chapter describes how to use SQL statements in embedded applications to control databases. There are three database statements that set up and open databases for access: SET DATABASE declares a database handle, associates the handle with an actual database file, and optionally assigns operational parameters for the database. SET NAMES optionally specifies the character set a client application uses for CHAR, VARCHAR, and text Blob data. The server uses this information to transli terate from a database?s default character set to the client?s character set on SELECT operations, and to transliterate from a client application?s character set to the database character set on INSERT and UPDATE operations. g CONNECT opens a database, allocates system resources for it, and optionally assigns operational parameters for the database.All databases must be closed before a program ends. A database can be closed by using DISCONNECT, or by appending the RELEASE option to the final COMMIT or ROLLBACK in a program. Declaring a database Before a database can be opened and used in a program, it must first be declared with SET DATABASE to: CHAPTER 3 WORKING WITH DATABASES. Establish a database handle. Associate the database handle with a database file stored on a local or remote node.A database handle is a unique, abbreviated alias for an actual database name. Database handles are used in subsequent CONNECT, COMMIT RELEASE, and ROLLBACK RELEASE statements to specify which databases they should affect. Except in dynamic SQL (DSQL) applications, database handles can also be used inside transaction blocks to qualify, or differentiate, table names when two or more open databases contain identically named tables. Each database handle must be unique among all variables used in a program. Database handles cannot duplicate host-language reserved words, and cannot be InterBase reserved words.The following statement illustrates a simple database declaration:

英文版excel中英文对照表

英文版Excel 中英文对照表 激活(activate) 数组(array) 数组公式(array formula) 相关联的数据透视表(associated PivotTable report )自动套用格式(autoformat) 坐标轴(asix) 基础地址(base address) “合并计算”表(consolidation table) 比较条件(comparison criteria) 比较运算符(comparison operator) 常量(constant) 单元格引用(cell reference) 当前区域(current region) 分类轴(category asix) 分类字段(category field) 复制区域(copy area) 计算列(calculated column) 计算项(calculated item) 计算字段(数据库)(calculated field) 计算字段(数据透视表)(calculated field) 列标题(column heading) 列字段(column field) 条件(criteria) 条件窗格((criteria pane) 条件格式(conditional format) 图表工作表(chart sheet) 图表区(chart area) 修订记录(change history) 约束条件(constraints) 证书验证机构(certifying authority) 自定义计算(custom calculation) 垂直线(drop lines) 从属单元格(dependents) 明细数据(detail data) 默认工作表模板(default worksheet template) 默认工作簿模板(default workbook template) 默认启动工作簿(default startup workbook ) 目标区域(destination area) 数据标签 (data label) 数据标志(data marker) 数据表(data table) 数据表单(data form) 数据窗格(data pane)

(完整版)数据库重要术语(中英文)

单词汇总(数据库专业一点的词汇其实主要就是每章后面review items的内容,在这里简单列一 下,如果你实在没时间看书,至少这些单词要认识。): 1. 数据库系统:database system(DS),database ma nageme nt system(DBMS) 2. 数据库系统(DS),数据库管理系统(DBMS) 3. 关系和关系数据库table= relation,column = attribute 属性,domain, atomic domain, row= tuple , relati onal database, relati on schema, relati on in sta nee, database schema, database in sta nee; 4. 表=关系,列=属性属性,域,原子域,排=元组,关系型数据库,关系模式,关系实例,数 据库模式,数据库实例; 1. key 们:super key, can didate key, primary key, foreig n key, referencing relati on, referen ced relati on; 2. 超码,候选码,主码,外码,参照关系,被参照关系 5. 关系代数(relational algebra): selection, project, natural join, Cartesian product, set operations, union, in tersect, set differe nee ( except\m in us), Ren ame, assig nment, outer join, group ing, tuple relati on calculus 6. (关系代数):选择,项目,自然连接,笛卡尔积,集合运算,集,交集,集合差(除负), 重命名,分配,外连接,分组,元组关系演算 7. sql组成: DDL :数据库模式定义语言,关键字:create DML :数据操纵语言,关键字:Insert、delete、update DCL :数据库控制语言,关键字:grant、remove DQL :数据库查询语言,关键字:select 8. 3. SQL 语言:DDL,DML,DCL,QL,sql query structure, aggregate functions, nested subqueries, exists(as an operator), uni que(as an operator), scalar subquery, asserti on, in dex(i ndices), catalogs, authorization, all privileges, granting, revoking , grant option, trigger, stored procedure, stored fun cti on 4. SQL语言:DDL,DML,DCL,QL,SQL查询结构,聚合函数,嵌套子查询,存在(如运 营商),独特的(如运营商),标量子查询,断言指数(指数) ,目录,授权,所有权限,授 予,撤销,GRANT OPTION,触发器,存储过程,存储函数 8. 表结构相关:Integrity constraints, domain constraints, referential integrity constraints 9. 完整性约束,域名约束,参照完整性约束 5. 数据库设计(ER 模型):Entity-Relationship data model, ER diagram, composite attribute, sin gle-valued and multivalued attribute, derived attribute, binary relati on ship set, degree of relati on ship set, mapp ing card in ality, 1-1, 1-m, m-n relati on ship set (one to one, one to many, many to many), participati on, partial or total participati on, weak en tity sets, discrim in ator attributes, specialization and generalization 6. 实体关系数据模型,ER图,复合属性,单值和多值属性,派生属性,二元关系集,关系集, 映射基数的程度,1-1,1-米,MN关系集合(一对一,一对多,多对多) ,参与部分或全部参与,弱实体集,分辨符属性,特化和概化 10. 函数依赖理论:functional dependence, normalization, lossless join (or lossless) decomposition, First Normal Form (1NF), the third normal form (3NF), Boyce-codd normal form (BCNF), R satisfies F, F

企业数据建模外文翻译文献

企业数据建模外文翻译文献 (文档含中英文对照即英文原文和中文翻译) 翻译: 信息系统开发和数据库开发 在许多组织中,数据库开发是从企业数据建模开始的,企业数据建模确定了组织数据库的范围和一般内容。这一步骤通常发生在一个组织进行信息系统规划的过程中,它的目的是为组织数据创建一个整体的描述或解释,而不是设计一个特定的数据库。一个特定的数据库为一个或多个信息系统提供数据,而企业数据模型(可能包含许多数据库)描述了由组织维护的数据的范围。在企业数据建模时,你审查当前的系统,分析需要支持的业务领域的本质,描述需要进一步抽象的数据,并且规划一个或多个数据库开发项目。图1显示松谷家具公司的企业数据模型的一个部分。 1.1 信息系统体系结构 如图1所示,高级的数据模型仅仅是总体信息系统体系结构(ISA)一个部分或一个组

织信息系统的蓝图。在信息系统规划期间,你可以建立一个企业数据模型作为整个信息系统体系结构的一部分。根据Zachman(1987)、Sowa和Zachman(1992)的观点,一个信息系统体系结构由以下6个关键部分组成: 数据(如图1所示,但是也有其他的表示方法)。 操纵数据的处理(着系可以用数据流图、带方法的对象模型或者其他符号表示)。 网络,它在组织内并在组织与它的主要业务伙伴之间传输数据(它可以通过网络连接和拓扑图来显示)。 人,人执行处理并且是数据和信息的来源和接收者(人在过程模型中显示为数据的发送者和接收者)。 执行过程的事件和时间点(它们可以用状态转换图和其他的方式来显示)。 事件的原因和数据处理的规则(经常以文本形式显示,但是也存在一些用于规划的图表工具,如决策表)。 1.2 信息工程 信息系统的规划者按照信息系统规划的特定方法开发出信息系统的体系结构。信息工程是一种正式的和流行的方法。信息工程是一种面向数据的创建和维护信息系统的方法。因为信息工程是面向数据的,所以当你开始理解数据库是怎样被标识和定义时,信息工程的一种简洁的解释是非常有帮助的。信息工程遵循自顶向下规划的方法,其中,特定的信息系统从对信息需求的广泛理解中推导出来(例如,我们需要关于顾客、产品、供应商、销售员和加工中心的数据),而不是合并许多详尽的信息请求(如一个订单输入屏幕或按照地域报告的销售汇总)。自顶向下规划可使开发人员更全面地规划信息系统,提供一种考虑系统组件集成的方法,增进对信息系统与业务目标的关系的理解,加深对信息系统在整个组织中的影响的理解。 信息工程包括四个步骤:规划、分析、设计和实现。信息工程的规划阶段产生信息系统体系结构,包括企业数据模型。 1.3 信息系统规划 信息系统规划的目标是使信息技术与组织的业务策略紧密结合,这种结合对于从信息系统和技术的投资中获取最大利益是非常重要的。正如表1所描述的那样,信息工程方法的规划阶段包括3个步骤,我们在后续的3个小节中讨论它们。 1.确定关键性的规划因素

数据库外文参考文献及翻译.

数据库外文参考文献及翻译 数据库外文参考文献及翻译数据库管理系统——实施数据完整性一个数据库,只有用户对它特别有信心的时候。这就是为什么服务器必须实施数据完整性规则和商业政策的原因。执行SQL Server的数据完整性的数据库本身,保证了复杂的业务政策得以遵循,以及强制性数据元素之间的关系得到遵守。因为SQL Server的客户机/服务器体系结构允许你使用各种不同的前端应用程序去操纵和从服务器上呈现同样的数据,这把一切必要的完整性约束,安全权限,业务规则编码成每个应用,是非常繁琐的。如果企业的所有政策都在前端应用程序中被编码,那么各种应用程序都将随着每一次业务的政策的改变而改变。即使您试图把业务规则编码为每个客户端应用程序,其应用程序失常的危险性也将依然存在。大多数应用程序都是不能完全信任的,只有当服务器可以作为最后仲裁者,并且服务器不能为一个很差的书面或恶意程序去破坏其完整性而提供一个后门。SQL Server使用了先进的数据完整性功能,如存储过程,声明引用完整性(DRI),数据类型,限制,规则,默认和触发器来执行数据的完整性。所有这些功能在数据库里都有各自的用途;通过这些完整性功能的结合,可以实现您的数据库的灵活性和易于管理,而且还安全。声明数据完整性声明数据完整原文请找腾讯3249114六,维-论'文.网 https://www.360docs.net/doc/2e11612032.html, 定义一个表时指定构成的主键的列。这就是所谓的主键约束。SQL Server使用主键约束以保证所有值的唯一性在指定的列从未侵犯。通过确保这个表有一个主键来实现这个表的实体完整性。有时,在一个表中一个以上的列(或列的组合)可以唯一标志一行,例如,雇员表可能有员工编号( emp_id )列和社会安全号码( soc_sec_num )列,两者的值都被认为是唯一的。这种列经常被称为替代键或候选键。这些项也必须是唯一的。虽然一个表只能有一个主键,但是它可以有多个候选键。 SQL Server的支持多个候选键概念进入唯一性约束。当一列或列的组合被声明是唯一的, SQL Server 会阻止任何行因为违反这个唯一性而进行的添加或更新操作。在没有故指的或者合适的键存在时,指定一个任意的唯一的数字作为主键,往往是最有效的。例如,企业普遍使用的客户号码或账户号码作为唯一识别码或主键。通过允许一个表中的一个列拥有身份属性,SQL Server可以更容易有效地产生唯一数字。您使用的身份属性可以确保每个列中的值是唯一的,并且值将从你指定的起点开始,以你指定的数量进行递增(或递减)。(拥有特定属性的列通常也有一个主键或唯一约束,但这不是必需的。)第二种类型的数据完整性是参照完整性。 SQL Server实现了表和外键约束之间的逻辑关系。外键是一个表中的列或列的组合,连接着另一个表的主键(或着也可能是替代键)。这两个表之间的逻辑关系是关系模型的基础;参照完整性意味着这种关系是从来没有被违反的。例如,一个包括出版商表和标题表的简单的select例子。在标题表中,列title_id (标题编号)是主键。在出版商表,列pub_id (出版者ID )是主键。 titles表还包括一个pub_id列,这不是主键,因为出版商可以发布多个标题。相反, pub_id是一个外键,它对应着出版商表的主键。如果你在定义表的时候声明了这个关系, SQL Server由双方执行它。首先,它确保标题不能进入titles表,或在titles表中现有的pub_id无法被修改,除非有效的出版商ID作为新pub_id出现在出版商表中。其次,它确保在不考虑titles表中对应值的情况下,出版商表中的pub_id的值不做任何改变。以下两种方法可

数据库方面中英文对照

本科毕业设计(论文) 英文翻译 题目创业平台设计与实现 学生姓名 专业班级网 学号 院(系) 指导教师(职称) 完成时间 2008 年6 月6 日

英文原文 An Overview of Servlet and JSP Technology Gildas Avoine and Philippe Oechslin EPFL, Lausanne, Switzerland 1.1 A Servlet's Job Servlets are Java programs that run on Web or application servers, acting as a middle layer between requests coming from Web browsers or other HTTP clients and databases or applications on the HTTP server. Their job is to perform the following tasks, as illustrated in Figure 1-1. Figure 1-1 1.Read the explicit data sent by the client. The end user normally enters this data in an HTML form on a Web page. However, the data could also come from an applet or a custom HTTP client program. 2.Read the implicit HTTP request data sent by the browser. Figure 1-1 shows a single arrow going from the client to the Web server (the layer where servlets and JSP execute), but there are really two varieties of data: the explicit data that the end user enters in a form and the behind-the-scenes HTTP information. Both varieties are critical. The HTTP information includes cookies, information about media types and compression schemes the browser understands, and so on. 3.Generate the results. This process may require talking to a database, executing an RMI or EJB call, invoking a Web service, or computing the response directly. Your real data may be in a relational database. Fine. But your database probably doesn't speak HTTP or return results in HTML, so the Web browser can't talk directly to the database. Even if it could, for security reasons, you probably would not want it to. The same argument applies to most other applications. You need the Web middle layer to extract the incoming data from the HTTP stream, talk to

外文文献翻译 An Introduction to Database Management System

英文翻译 数据库管理系统的介绍 Raghu Ramakrishnan 数据库(database,有时被拼作data base)又称为电子数据库,是专门组织起来的一组数据或信息,其目的是为了便于计算机快速查询及检索。数据库的结构是专门设计的,在各种数据处理操作命令的支持下,可以简化数据的存储、检索、修改和删除。数据库可以存储在磁盘、磁带、光盘或其他辅助存储设备上。 数据库由一个或一套文件组成,其中的信息可以分解为记录,每一条记录又包含一个或多个字段(或称为域)。字段是数据存取的基本单位。数据库用于描述实体,其中的一个字段通常表示与实体的某一属性相关的信息。通过关键字以及各种分类(排序)命令,用户可以对多条记录的字段进行查询,重新整理,分组或选择,以实体对某一类数据的检索,也可以生成报表。 所有数据库(除最简单的)中都有复杂的数据关系及其链接。处理与创建,访问以及维护数据库记录有关的复杂任务的系统软件包叫做数据库管理系统(DBMS)。DBMS软件包中的程序在数据库与其用户间建立接口。(这些用户可以是应用程序员,管理员及其他需要信息的人员和各种操作系统程序)DBMS可组织、处理和表示从数据库中选出的数据元。该功能使决策者能搜索、探查和查询数据库的内容,从而对正规报告中没有的,不再出现的且无法预料的问题做出回答。这些问题最初可能是模糊的并且(或者)是定义不恰当的,但是人们可以浏览数据库直到获得所需的信息。简言之,DBMS将“管理”存储的数据项和从公共数据库中汇集所需的数据项用以回答非程序员的询问。 DBMS由3个主要部分组成:(1)存储子系统,用来存储和检索文件中的数据;(2)建模和操作子系统,提供组织数据以及添加、删除、维护、更新数据的方法;(3)用户和DBMS之间的接口。在提高数据库管理系统的价值和有效性方面正在展现以下一些重要发展趋势: 1.管理人员需要最新的信息以做出有效的决策。 2.客户需要越来越复杂的信息服务以及更多的有关其订单,发票和账号的当前信息。

数据库设计外文翻译

外文翻译: 索引 原文来源:Thomas Kyte.Expert Oracle Database Architecture .2nd Edition. 译文正文: 什么情况下使用B*树索引? 我并不盲目地相信“法则”(任何法则都有例外),对于什么时候该用B*索引,我没有经验可以告诉你。为了证明为什么这个方面我无法提供任何经验,下面给出两种等效作法:?使用B*树索引,如果你想通过索引的方式去获得表中所占比例很小的那些行。 ?使用B *树索引,如果你要处理的表和索引许多可以代替表中使用的行。 这些规则似乎提供相互矛盾的意见,但在现实中,他们不是这样的,他们只是涉及两个极为不同的情况。有两种方式使用上述意见给予索引: ?作为获取表中某些行的手段。你将读取索引去获得表中的某一行。在这里你想获得表中所占比例很小的行。 ?作为获取查询结果的手段。这个索引包含足够信息来回复整个查询,我们将不用去查询全表。这个索引将作为该表的一个瘦版本。 还有其他方式—例如,我们使用索引去检索表的所有行,包括那些没有建索引的列。这似乎违背了刚提出的两个规则。这种方式获得将是一个真正的交互式应用程序。该应用中,其中你将获取其中的某些行,并展示它们,等等。你想获取的是针对初始响应时间的查询优化,而不是针对整个查询吞吐量的。 在第一种情况(也就是你想通过索引获得表中一小部分的行)预示着如果你有一个表T (使用与早些时候使用过的相一致的表T),然后你获得一个像这样查询的执行计划: ops$tkyte%ORA11GR2> set autotrace traceonly explain ops$tkyte%ORA11GR2> select owner, status 2 from t 3 where owner = USER; Execution Plan ---------------------------------------------------------- Plan hash value: 1049179052 ------------------------------------------------------------------ | Id | Operation | Name | Rows | Bytes | ------------------------------------------------------------------ | 0 | SELECT STATEMENT | | 2120 | 23320 | | 1 | TABLE ACCESS BY INDEX ROWID |T | 2120 | 23320 | | *2 | INDEX RANGE SCAN | DESC_T_IDX | 8 | | ------------------------------------------------------------------ Predicate Information (identified by operation id): --------------------------------------------------- 2 - access(SYS_OP_DESCEND("OWNER")=SYS_OP_DESCEND(USER@!)) filter(SYS_OP_UNDESCEND(SYS_OP_DESCEND("OWNER"))=USER@!) 你应该访问到该表的一小部分。这个问题在这里看是INDEX (RANGE SCAN) 紧跟在

数据库(中英文翻译)

原文: Planning the Database It is important to plan how the logical storage structure of the database will affect system performance and various database management operations. For example, before creating any tablespaces for your database, you should know how many data files will make up the tablespace,what type of information will be stored in each tablespace, and on which disk drives the datafiles will be physically stored. When planning the overall logical storage of the database structure, take into account the effects that this structure will have when the database is actually created and running. You may have database objects that have special storage requirements due to type or size. In distributed database environments, this planning stage is extremely important. The physical location of frequently accessed data dramatically affects application performance. During the planning stage, develop a backup strategy for the database. You can alter the logical storage structure or design of the database to improve backup efficiency. Backup strategies are introduced in a later lesson. These are the types of questions and considerations, which you will encounter as a DBA, and this course (in its entirety) is designed to help you answer them. Databases: Examples Different types of databases have their own specific instance and storage requirements. Your Oracle database software includes templates for the creation of these different types of databases. Characteristics of these examples are the following: ? Data Warehouse: Store data for long periods and retrieve them in read operations. ? Transaction Processing: Accommodate many, but usually small, transactions. ? General Purpose: Work with transactions and store them for a medium length of time.

大学毕业设计仓库管理系统数据库计算机外文参考文献原文及翻译

河北工程大学毕业论文(设计)英文参考文献原文复印件及译文 数据仓库 数据仓库为商务运作提供结构与工具,以便系统地组织、理解和使用数据进行决策。大量组织机构已经发现,在当今这个充满竞争、快速发展的世界,数据仓库是一个有价值的工具。在过去的几年中,许多公司已花费数百万美元,建立企业范围的数据仓库。许多人感到,随着工业竞争的加剧,数据仓库成了必备的最新营销武器——通过更多地了解客户需求而保住客户的途 径。“那么”,你可能会充满神秘地问,“到底什么是数据仓库?” 数据仓库已被多种方式定义,使得很难严格地定义它。宽松地讲,数据仓库是一个数据库,它与组织机构的操作数据库分别维护。数据仓库系统允许将各种应用系统集成在一起,为统一的历史数据分析提供坚实的平台,对信息处理提供支持。 按照W. H. Inmon,一位数据仓库系统构造方面的领头建筑师的说法,“数 (1) 视图。 (2)

般文件和联机事务处理记录,集成在一起。使用数据清理和数据集成技术,确保命名约定、编码结构、属性度量的一致性等。 (3)时变的:数据存储从历史的角度(例如,过去5-10 年)提供信息。数据仓库中的关键结构,隐式或显式地包含时间元素。 (4) 非易失的:数据仓库总是物理地分离存放数据;这些数据源于操作环境下的应用数据。由于这种分离,数据仓库不需要事务处理、恢复和并行控制机制。通常,它只需要两种数据访问:数据的初始化装入和数据访问。 概言之,数据仓库是一种语义上一致的数据存储,它充当决策支持数据模型的物理实现,并存放企业决策所需信息。数据仓库也常常被看作一种体系结构,通过将异种数据源中的数据集成在一起而构造,支持结构化和启发式查询、分析报告和决策制定。 “好”,你现在问,“那么,什么是建立数据仓库?” 根据上面的讨论,我们把建立数据仓库看作构造和使用数据仓库的过程。数据仓库的构造需要数据集成、数据清理、和数据统一。利用数据仓库常常需要一些决策支持技术。这使得“知识工人”(例如,经理、分析人员和主管)能够使用数据仓库,快捷、方便地得到数据的总体视图,根据数据仓库中的信息做出准确的决策。有些作者使用术语“建立数据仓库”表示构造数据仓库的过程,而用术语“仓库DBMS”表示管理和使用数据仓库。我们将不区分二者。 “组织机构如何使用数据仓库中的信息?”许多组织机构正在使用这些信息支持商务决策活动,包括: (1)、增加顾客关注,包括分析顾客购买模式(如,喜爱买什么、购买时间、预算周期、消费习惯); (2)、根据季度、年、地区的营销情况比较,重新配置产品和管理投资,调整生产策略; (3)、分析运作和查找利润源; (4)、管理顾客关系、进行环境调整、管理合股人的资产开销。 从异种数据库集成的角度看,数据仓库也是十分有用的。许多组织收集了形形色色数据,并由多个异种的、自治的、分布的数据源维护大型数据库。集成这些数据,并提供简便、有效的访问是非常希望的,并且也是一种挑战。数据库工业界和研究界都正朝着实现这一目标竭尽全力。 对于异种数据库的集成,传统的数据库做法是:在多个异种数据库上,建立一个包装程序和一个集成程序(或仲裁程序)。这方面的例子包括IBM 的数据连接程序和Informix的数据刀。当一个查询提交客户站点,首先使用元数据字典对查询进行转换,将它转换成相应异种站点上的查询。然后,将这些查询

(完整版)数据库重要术语(中英文)

单词汇总(数据库专业一点的词汇其实主要就是每章后面review items的内容,在这里简单列一下,如果你实在没时间看书,至少这些单词要认识。): 1.数据库系统:database system(DS),database management system(DBMS) 2.数据库系统(DS),数据库管理系统(DBMS) 3.关系和关系数据库table= relation,column = attribute属性,domain, atomic domain, row= tuple, relational database, relation schema, relation instance, database schema, database instance; 4.表=关系,列=属性属性,域,原子域,排=元组,关系型数据库,关系模式,关系实例,数 据库模式,数据库实例; 1.key们: super key, candidate key, primary key, foreign key, referencing relation, referenced relation; 2.超码,候选码,主码,外码,参照关系,被参照关系 5.关系代数(relational algebra):selection, project, natural join, Cartesian product, set operations, union, intersect, set difference ( except\minus), Rename, assignment, outer join, grouping, tuple relation calculus 6.(关系代数):选择,项目,自然连接,笛卡尔积,集合运算,集,交集,集合差(除\负), 重命名,分配,外连接,分组,元组关系演算 7. sql组成: DDL:数据库模式定义语言,关键字:create DML:数据操纵语言,关键字:Insert、delete、update DCL:数据库控制语言,关键字:grant、remove DQL:数据库查询语言,关键字:select 8. 3.SQL语言:DDL,DML,DCL,QL,sql query structure, aggregate functions, nested subqueries, exists(as an operator), unique(as an operator), scalar subquery, assertion, index(indices), catalogs, authorization, all privileges, granting, revoking, grant option, trigger, stored procedure, stored function 4.SQL语言:DDL,DML,DCL,QL,SQL查询结构,聚合函数,嵌套子查询,存在(如运 营商),独特的(如运营商),标量子查询,断言指数(指数),目录,授权,所有权限,授予,撤销,GRANT OPTION,触发器,存储过程,存储函数 9.表结构相关:Integrity constraints, domain constraints, referential integrity constraints 10.完整性约束,域名约束,参照完整性约束 5.数据库设计(ER 模型):Entity-Relationship data model, ER diagram, composite attribute, single-valued and multivalued attribute, derived attribute,binary relationship set, degree of relationship set, mapping cardinality,1-1, 1-m, m-n relationship set (one to one, one to many, many to many), participation, partial or total participation, weak entity sets, discriminator attributes, specialization and generalization 6.实体关系数据模型,ER图,复合属性,单值和多值属性,派生属性,二元关系集,关系集, 映射基数的程度,1-1,1-米,MN关系集合(一对一,一对多,多对多),参与部分或全部参与,弱实体集,分辨符属性,特化和概化 11.函数依赖理论:functional dependence, normalization, lossless join (or lossless) decomposition, First Normal Form (1NF), the third normal form (3NF), Boyce-codd normal form (BCNF), R satisfies F, F holds on R, Dependency preservation保持依赖, Trivial, closure of a set of functional dependencies函数依赖集的闭包, closure of a set of attributes属性集闭包,

相关文档
最新文档