大學(xué)畢業(yè)設(shè)計(jì)關(guān)于數(shù)據(jù)庫(kù)外文翻譯2篇_第1頁(yè)
大學(xué)畢業(yè)設(shè)計(jì)關(guān)于數(shù)據(jù)庫(kù)外文翻譯2篇_第2頁(yè)
大學(xué)畢業(yè)設(shè)計(jì)關(guān)于數(shù)據(jù)庫(kù)外文翻譯2篇_第3頁(yè)
大學(xué)畢業(yè)設(shè)計(jì)關(guān)于數(shù)據(jù)庫(kù)外文翻譯2篇_第4頁(yè)
大學(xué)畢業(yè)設(shè)計(jì)關(guān)于數(shù)據(jù)庫(kù)外文翻譯2篇_第5頁(yè)
已閱讀5頁(yè),還剩18頁(yè)未讀 繼續(xù)免費(fèi)閱讀

下載本文檔

版權(quán)說(shuō)明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請(qǐng)進(jìn)行舉報(bào)或認(rèn)領(lǐng)

文檔簡(jiǎn)介

1、重慶理工大學(xué)2013屆本科生畢業(yè)設(shè)計(jì)(論文)外文文獻(xiàn)翻譯原文:Structure of the Relational database « Database System Concepts » Part1: Relational DatabasesThe relational model is the basis for any relational database management system (RDBMS).A relational model has three core components: a collection of obj ects or rela

2、tions, operators that act on the objects or relations, and data integrity methods. In other words, it has a place to store the data, a way to create and retrieve the data, and a way to make sure that the data is logically consistent.A relational database uses relations, or two -dimensional tables, t

3、o store the information needed to support a business. Let's go over the basic components of a traditional relational database system and look at howa relational databaseisdesigned.Once youhave a solidunderstanding of what rows, columns, tables, and relationships are, you'llbe well on your wa

4、ytoleveragingthe powerof a relationaldatabase.Tables, Row, and ColumnsA table in a relational database, alternatively known as a relation, is a two-dimensional structure used to hold related information. A database consists of one or more related tables.Note: Don't confuse a relation with relati

5、onships. A relation is essentially a table, and a relationship is a way to correlate, join, or associate two tables.A row in a table is a collection or instance of one thing, such as one employee or one line item on an invoice. A column contains all the information of a single type, and the piece of

6、 data at the intersection of a row and a column, a field, is the smallest piece of information that can be retrieved with the database's query language. For example, a table with information about employees might have a column calledLAST_NAME that contains all of the employees' last names. D

7、ata is retrieved from a table by filtering on both the row and the column.Primary Keys, Datatypes, and Foreign KeysThe examples throughout this article will focus on the hypothetical work of Scott Smith, database developer and entrepreneur. He just started a new widget company and wants to implement

8、 a few of the basic business functions using the relational database to manage his Human Resources (HR) department.Relation: A two-dimensional structure used to hold related information, also known as a table.Note: Most of Scott's employees were hired away from one of his previous employers, som

9、e of whom have over 20 years of experience in the field. As a hiring incentive, Scott has agreed to keep the new employees' original hire date in the new database.Row:A group of one or more data elements in a database table that describes a person, place, or thing.Column:The component of a datab

10、ase table that contains all of the data of the same name and type across all rows.You'll learn about database design in the following sections, but let's assume for the moment that the majority of the database design is completed and some tables need to be implemented. Scott creates the EMP

11、table to hold the basic employee information, and it looks something like this:AMEJOB1 11 i.SAItJtnxnSMITHKLERK-DEC-SOROG*一硼ALLE1MJC'WARDALES MAX125C勃MANAGED骸KINJGPRESIDENT-XOV-R小FCRDanalyst德-DEC-R】Notice that some fields in the Commission (COMM) and Manager (MGR) columns do not contain a value;

12、 they are blank. A relational database can enforce the rule that fields in a column may or may not be empty. In this case, it makes sense for an employee who is not in the Sales department to have a blank Commission field. It also makes sense for the president of the company to have a blank Manager

13、field, since that employee doesn't report to anyone.Field:The smallest piece of information that can be retrieved by the database query language. A field is found at the intersection of a row and a column in a database table.On the other hand, none of the fields in the Employee Number (EMPNO) co

14、lumn are blank. The company always wants to assign an employee number to an employee, and that number must be different for each employee. One of the features of a relational database is that it can ensure that a value is entered into this column and that it is unique. TheEMPNO column, in this case,

15、 is the primary key of the table.Primary Key:A column (or columns) in a table that makes the row in the table distinguishable from every other row in the same table.Notice the different datatypes that are stored in the EMP table: numeric values, character or alphabetic values, and date values.As you

16、 might suspect, the DEPTNO column contains the department number for the employee. But how do you know what department name is associated with what number? Scott created the DEPT table to hold the descriptions for the department codes in the EMP table.DJT1AOl.OC10ACCOLMIXGNEV Y口RK201DALLAS30SALESCHI

17、CAGO40OPEP.AT1DX5130 5 TONThe DEPTNO column in the EMP table contains the same values as the DEPTNO column in the DEPT table. In this case, the DEPTNO column in the EMP table is considered a foreign key to the same column in the DEPT table.A foreign key enforces the concept of referential integrity

18、in a relational database. The concept of referential integrity not only prevents an invalid department number from being inserted into the EMP table, but it also prevents a row in the DEPT table from being deleted if there are employees still assigned to that department.Foreign Key:A column (or colu

19、mns) in a table that drawsits valuesfrom a primary or unique key column in another table. A foreign key assists in ensuring the data integrity of a table. Referential IntegrityAmethod employed by a relational database system that enforces one-to-many relationships between tables.Data ModelingBefore

20、Scott created the actual tables in the database, he went through a design process known as data modeling. In this process, the developer conceptualizes and documents all the tables for the database.One of the common methods for mod eling a database is called ERA, which stands for entities, relations

21、hips, and attributes. The database designer uses an application that can maintain entities, their attributes, and their relationships. In general, an entity corresponds to a table in the database, and the attributes of the entity correspond to columns of the table.Data Modeling:A process of defining

22、 the entities, attributes, and relationships between the entities in preparation for creating the physical database.The data-modeling process involves defining the entities, defining the relationships between those entities, and then defining the attributes for each of the entities. Once a cycle is

23、complete, it is repeated as many times as necessary to ensure that the designer is capturing what is important enough to go into the database. Let's take a closer look at each step in the data-modeling process.Defining the EntitiesFirst, the designer identifies all of the entities within the sco

24、pe of the database application.The entities are the pers ons, places, or things that are important to the organization and need to be tracked in the database. Entities will most likely translate neatly to database tables. For example, for the first version of Scott's widget company database, he

25、identifies four entities: employees, departments, salary grades, and bonuses. These will become the EMP, DEPT, SALGRADE, and BONUS tables.Defining the Relationships Between EntitiesOnce the entities are defined, the designer can proceed with defining how each of the entities is related. Often, the d

26、esigner will pair each entity with every other entity and ask, "Is there a relationship between these two entities?" Some relationships are obvious; some are not.In the widget company database, there is most likely a relationshipbetween EMP and DEPT, but depending on the business rules, it

27、 is unlikely that the DEPT and SALGRADE entities are related. If the business rules were to restrict certain salary grades to certain departments, there would most likely be a new entity that defines the relationship between salary grades and departments. This entity would be known as an associative

28、 or intersection table and would contain the valid combinations of salary grades and departments.Associative Table:A database table that stores th e valid combinations of rows from two other tables and usually enforces a business rule. An associative table resolves a many -to-many relationship.In ge

29、neral, there are three types of relationships in a relational database:One-to-many The most common type of relationship is one-to-many.This means that for each occurrence in a given entity, the parent entity, there may be one or more occurrences in a second entity, the child entity, to which it is r

30、elated. For example, in the widget company database, the DEPT entity is a parent entity, and for each department, there could be one or more employees associated with that department. The relationship between DEPT and EMP is one -to-many.One-to-one In a one-to-one relationship, a row in a table is r

31、elated to only one or none of the rows in a second table. This relationship type is often used for subtyping. For example, an EMPLOYEEtable mayhold the information common to all employees, while the FULLTIME, PARTTIME, and CONTRACTOR tables hold informationunique tofull-time employees, part-time emp

32、loyees, and contractors, respectively.These entities would be considered subtypes of an EMPLOYEE and maintain a one-to-one relationship with the EMPLOYEE table. These relationships are not as common as one -to-many relationships, because if one entity has an occurrence for a corresponding row in ano

33、ther entity, in most cases, the attributes from both entities should be in a single entity.Many-to-many In a many-to-many relationship, one row of a table may be related to man y rows of another table, and vice versa. Usually, when this relationship is implemented in the database, a third entity is

34、defined as an intersection table to contain the associations between the two entities in the relationship. For example, in a database used for school class enrollment, the STUDENT table has a many -to-many relationship with the CLASS table one student may take one or more classes, and a given class

35、may have one or more students. The intersection table STUDENT_CLASS would contain the comb inations of STUDENT and CLASS to track which students are in which classes.Once the designer has defined the entity relationships, the next step is to assign the attributes to each entity. This is physically i

36、mplemented using columns, as shown here for th e SALGRADE table as derived from the salary grade entity.After the entities, relationships, and attributes have been defined, the designer may iterate the data modeling many more times. When reviewing relationships, new entities may be discovered. For e

37、xample, when discussing the widget inventory table and its relationship to a customer order, the need for a shipping restrictions table may arise.(;R.DL1.05 Al1|70012002not3140)工OOP42-0015610DW12500Once the design process is complete, the physical database tables may be created. Logical database des

38、ign sessions should not involve physical implementation issues, but once the design has gone through an iteration or two, it's the DBA's job to bring the designers "down to earth." As a result, the design may need to be revisited to balance the ideal database implementation versus

39、the realities of budgets andschedules.譯文:關(guān)系數(shù)據(jù)庫(kù)的結(jié)構(gòu)數(shù)據(jù)庫(kù)系統(tǒng)結(jié)構(gòu)第一章: 關(guān)系數(shù)據(jù)庫(kù) 關(guān)系模型是任何關(guān)系數(shù)據(jù)庫(kù)管理系統(tǒng)(RDBMS的基礎(chǔ)。一個(gè)關(guān) 系模型有二個(gè)核心組件:對(duì)象或關(guān)系的集合,作用于對(duì)象或關(guān)系上的 操作,以及數(shù)據(jù)完整性規(guī)則。換句話說(shuō),關(guān)系數(shù)據(jù)庫(kù)有一個(gè)存儲(chǔ)數(shù)據(jù) 的地方,一種創(chuàng)建和檢索數(shù)據(jù)的方法,以及一種確認(rèn)數(shù)據(jù)的邏輯一致 性的方法。一個(gè)關(guān)系數(shù)據(jù)庫(kù)使用關(guān)系或二維表來(lái)存儲(chǔ)支持某個(gè)事物所需的 信息。讓我們了解一下一個(gè)傳統(tǒng)的關(guān)系數(shù)據(jù)庫(kù)系統(tǒng)的基本組件并目學(xué) 習(xí)如何設(shè)計(jì)一個(gè)關(guān)系數(shù)據(jù)庫(kù)。一旦你對(duì)于行、歹U、表和關(guān)聯(lián)是什么有 了深刻理解,你就能夠充分發(fā)揮

40、關(guān)系數(shù)據(jù)庫(kù)的強(qiáng)大功能。表,行和列在關(guān)系數(shù)據(jù)庫(kù)中,一個(gè)表(或者說(shuō)一個(gè)關(guān)系)是一個(gè)用于保存相 關(guān)信息的二維結(jié)構(gòu)。一個(gè)數(shù)據(jù)庫(kù)由一個(gè)或者多個(gè)相關(guān)聯(lián)的表組成。注意:不要混淆了關(guān)系和關(guān)聯(lián)。一個(gè)關(guān)系實(shí)際上是一個(gè)表,而一 個(gè)關(guān)聯(lián)指的是一種連接、結(jié)合或聯(lián)合兩個(gè)表的方式。表中的一行是一種事物的集合或?qū)嵗热缫粋€(gè)員工或發(fā)票上的 一項(xiàng)。表中的一列包含了一類(lèi)信息;而且行列交叉點(diǎn)上的數(shù)據(jù),字段, 即是能夠用數(shù)據(jù)庫(kù)查詢語(yǔ)言檢索到的最小片信息。舉個(gè)例子來(lái)說(shuō),一 個(gè)員工信息表可能有一個(gè)“名字”歹I,列中就包含所有員工的名字。 數(shù)據(jù)是通過(guò)對(duì)行、列進(jìn)行過(guò)濾而從表中檢索出來(lái)的。主碼、數(shù)據(jù)類(lèi)型和外碼本篇文章均以假設(shè)的斯科特史密斯的工

41、廠為例,他是數(shù)據(jù)庫(kù)的 建立者和企業(yè)的主辦人。他剛開(kāi)辦了一個(gè)飾品公司并目想要使用關(guān)系 數(shù)據(jù)庫(kù)的幾項(xiàng)基本功能來(lái)管理人力資源部門(mén)。關(guān)系:用來(lái)保存相關(guān)信息的一個(gè)二維結(jié)構(gòu)(也就是表)。注意:大多數(shù)斯科特的雇員都是雇自過(guò)去的從業(yè)者,他們中有些 人在這個(gè)領(lǐng)域己經(jīng)有20年的經(jīng)驗(yàn)了。出于雇用的目的,斯科特同意 在新數(shù)據(jù)庫(kù)中維持新進(jìn)員工最初的雇傭日期。行:在一個(gè)數(shù)據(jù)庫(kù)表中的一組單數(shù)據(jù)或多數(shù)據(jù)元素,用于描述一 個(gè)人、地方或事物。歹I:列是數(shù)據(jù)庫(kù)表的組件,它包含所有行中同名和同類(lèi)型的所有 數(shù)據(jù)。你會(huì)在下面章節(jié)學(xué)到如何設(shè)計(jì)數(shù)據(jù)庫(kù),現(xiàn)在讓我們假設(shè)數(shù)據(jù)庫(kù)大 部分己經(jīng)設(shè)計(jì)完成并且有一些表需要被執(zhí)行。斯科特創(chuàng)建了 EMP表來(lái)

42、保存基本的員工信息,就像這樣:Q L%號(hào)工科營(yíng)曜人二FJ此同史« Pi公計(jì)791JC17 J2-HUHOU2O2-4SIiEjuJD推用地乃帕22-2-MII2WSOD配必4圖3017-11-HI10福特苣任 B- 32-HI30口你可能注意到傭金列和管理人列中有一些單元格中沒(méi)有值;它們 是空值。一個(gè)關(guān)系數(shù)據(jù)庫(kù)能夠規(guī)定列中的一個(gè)單元格是否為空。如此, 可以明確那些非銷(xiāo)售部的員工傭金單元為空。同樣也明確了公司董事 長(zhǎng)的管理人單元為空,因?yàn)檫@個(gè)員工不需要向任何人匯報(bào)工作。單元格:是數(shù)據(jù)庫(kù)查詢語(yǔ)言所能夠檢索到的最小片信息。一個(gè)單 元格就是一個(gè)數(shù)據(jù)庫(kù)表的行和列交叉形成的。另一方面,沒(méi)有哪個(gè)員

43、工的員工編號(hào)單元為空。公司總是希望為 每個(gè)員工分配一個(gè)員工號(hào),并目這個(gè)號(hào)碼必須是每個(gè)員工都不同的。 關(guān)系數(shù)據(jù)庫(kù)的一個(gè)特性能夠確定某列的鍵入值必須為單值。如此,員 工編號(hào)列便是這個(gè)表的主碼。主碼:主碼即是表中的一列(或多列),使每一行能夠區(qū)別于同 表中的其他行留意一下EMP表中存儲(chǔ)的不同數(shù)據(jù)類(lèi)型:數(shù)值型,字符型或字母 型,以及日期型。如你所想,部門(mén)成員列保存的是員工所在部門(mén)的編號(hào)。但是你如 何知道哪個(gè)部門(mén)名稱對(duì)應(yīng)哪個(gè)部門(mén)編號(hào)呢?斯科特建立了 DEPT表來(lái) 具體描述EMP表中提到的部門(mén)編號(hào)的情況。*門(mén)弘除1 口激計(jì)時(shí)附行堀達(dá)扣方30情化佃,加.40a.%:;泣上統(tǒng):EMP表中的部門(mén)編號(hào)列同DEPT

44、表中的部門(mén)編號(hào)列有著相同的值。 既然如此,EMP表中的部門(mén)編號(hào)列便被看作是與DEPT表中相同列對(duì) 應(yīng)的外碼。外碼加強(qiáng)了關(guān)系數(shù)據(jù)庫(kù)中參考完整性的概念。參考完整性的概念 不只可以阻止無(wú)效的部門(mén)編號(hào)被插入EMP表中,而且在某部門(mén)仍有員 工的情況下,可以防止DEPT表中該部門(mén)的信息被刪除。外碼:表中的一列(或多列),它的值來(lái)自于其他表的主碼列或 單值列。一個(gè)外碼有助于確定表中數(shù)據(jù)的完整性。參考完整性:是關(guān)系數(shù)據(jù)庫(kù)用來(lái)加強(qiáng)表問(wèn)一對(duì)多關(guān)聯(lián)的一種方 式。數(shù)據(jù)建模在斯科特于數(shù)據(jù)庫(kù)中創(chuàng)建真實(shí)表之前,他要經(jīng)過(guò)一個(gè)稱作數(shù)據(jù)建 模的過(guò)程。在這個(gè)過(guò)程中,數(shù)據(jù)庫(kù)創(chuàng)建者定義和填寫(xiě)數(shù)據(jù)庫(kù)中所有表。 有一種為數(shù)據(jù)庫(kù)建模的方式叫

45、作ERA,它可以表示出實(shí)體、實(shí)體間的 關(guān)聯(lián)和實(shí)體的屬性。數(shù)據(jù)庫(kù)設(shè)計(jì)者使用一個(gè)能夠支持實(shí)體、實(shí)體屬性 和實(shí)體間關(guān)聯(lián)的應(yīng)用程序。通常,一個(gè)實(shí)體對(duì)應(yīng)數(shù)據(jù)庫(kù)中的一個(gè)表, 而實(shí)體的屬性對(duì)應(yīng)于表中的列。數(shù)據(jù)建模:一個(gè)定義實(shí)體、實(shí)體屬性和實(shí)體間關(guān)聯(lián)的過(guò)程,從而 為建立物理數(shù)據(jù)庫(kù)做準(zhǔn)備。數(shù)據(jù)建模過(guò)程包括定義實(shí)體、定義實(shí)體問(wèn)關(guān)聯(lián)以及定義每個(gè)實(shí)體 的屬性的過(guò)程。一旦一個(gè)周期完成,就需要不斷重復(fù)直到設(shè)計(jì)者抓住 了重點(diǎn),足以開(kāi)始建立數(shù)據(jù)庫(kù)。讓我們進(jìn)一步了解為數(shù)據(jù)庫(kù)建模過(guò)程 的步驟。定義實(shí)體首先,設(shè)計(jì)者確定數(shù)據(jù)庫(kù)應(yīng)用程序范圍內(nèi)的所有實(shí)體。實(shí)體是人、 地方或事物,它們對(duì)于整個(gè)團(tuán)體是重要的且需要被記錄在數(shù)據(jù)庫(kù)中。 實(shí)體將被

46、巧妙的轉(zhuǎn)化為數(shù)據(jù)表。比如,在第一版斯科特飾品公司數(shù)據(jù) 庫(kù)中,他定義了四個(gè)實(shí)體:?jiǎn)T工、部門(mén)、工資水平和獎(jiǎng)金。它們將稱 為EMP(員工)表,DEPT(部門(mén))表,SALGRADE(工資水平)表和BONUS (獎(jiǎng)金)表。定義實(shí)體間的關(guān)聯(lián)一旦定義了實(shí)體,設(shè)計(jì)者就能夠繼續(xù)定義每個(gè)實(shí)體間是如何關(guān)聯(lián) 的。通常,設(shè)計(jì)者通常將每個(gè)實(shí)體同其他實(shí)體配對(duì),并目考慮:“兩 者之間是否存在關(guān)聯(lián)呢?”實(shí)體問(wèn)的某些關(guān)聯(lián)是明顯的,某些不是。在飾品公司數(shù)據(jù)庫(kù)中,員工實(shí)體和部門(mén)實(shí)體間極可能存在關(guān)聯(lián), 而依據(jù)事物間的關(guān)系原則,部門(mén)實(shí)體跟工資水平實(shí)體間似乎就沒(méi)有關(guān) 聯(lián)了。如果事物間的關(guān)系原則是用來(lái)約束某個(gè)部門(mén)的工資水平的,就 可能需要一

47、個(gè)新的實(shí)體來(lái)說(shuō)明工資水平和部門(mén)之間的關(guān)聯(lián)。這個(gè)實(shí)體 被稱作關(guān)系表或交表,其中包含工資水平和部門(mén)之間的有效聯(lián)合。關(guān)系表:是一個(gè)數(shù)據(jù)庫(kù)表,其中保存著另外兩個(gè)表的行(記錄) 問(wèn)的有效結(jié)合,并且通常強(qiáng)調(diào)了事物間的關(guān)系原則。關(guān)聯(lián)表處理的是 一個(gè)多對(duì)多關(guān)聯(lián)。通常,關(guān)系數(shù)據(jù)庫(kù)間有二種關(guān)聯(lián)方式:一對(duì)多關(guān)聯(lián):最常見(jiàn)的關(guān)聯(lián)是一對(duì)多關(guān)聯(lián)。意思是對(duì)于每個(gè)給出 的現(xiàn)有實(shí)體(即父實(shí)體)都有一個(gè)或多個(gè)現(xiàn)有的另一個(gè)實(shí)體(即子實(shí) 體)與之相關(guān)聯(lián)。舉個(gè)例子來(lái)說(shuō),在飾品公司數(shù)據(jù)庫(kù)中,部門(mén)實(shí)體是 一個(gè)父實(shí)體,而每個(gè)部門(mén)中,都有一個(gè)或多個(gè)員工屬于該部門(mén)。這樣, 部門(mén)實(shí)體和員工實(shí)體間的關(guān)聯(lián)就是一對(duì)多關(guān)聯(lián)。一對(duì)一關(guān)聯(lián):在一個(gè)一對(duì)一關(guān)聯(lián)中,

48、表中的一行只關(guān)聯(lián)另一個(gè)表中的一行甚至0行。這種關(guān)聯(lián)類(lèi)型通常用于子類(lèi)型數(shù)據(jù)中。例如,一 個(gè)員工表可能保存了所有員工的信息,而全職表、兼職表和承包人表 則分別保存全職員工、兼職員工和承包人的信息。這些實(shí)體被認(rèn)為是 員工表的子表,并目同員工表維持一對(duì)一關(guān)聯(lián)。這種關(guān)系不像一對(duì)多 關(guān)聯(lián)那么常見(jiàn),因?yàn)槿绻粋€(gè)實(shí)體與另一個(gè)實(shí)體總有對(duì)應(yīng)行,在大多 數(shù)情況下,兩個(gè)實(shí)體中的屬性只在一個(gè)實(shí)體內(nèi)出現(xiàn)就可以了。多對(duì)多關(guān)聯(lián):在多對(duì)多關(guān)聯(lián)中,表的一行可能對(duì)應(yīng)另一個(gè)表的許 多行,反之亦然。通常,當(dāng)這些關(guān)聯(lián)在數(shù)據(jù)庫(kù)中被執(zhí)行時(shí),往往再定 義第三個(gè)實(shí)體用來(lái)保存前兩個(gè)實(shí)體間的所有關(guān)聯(lián)。例如,在一個(gè)學(xué)籍 注冊(cè)數(shù)據(jù)庫(kù)中,學(xué)生表與班級(jí)表之

49、間有一個(gè)多對(duì)多關(guān)聯(lián)一一一個(gè)學(xué)生 可能聽(tīng)一門(mén)或多門(mén)課程,并目一個(gè)班級(jí)也可能有一個(gè)或多個(gè)學(xué)生。而 學(xué)生班級(jí)關(guān)系表中就包含了學(xué)生和班級(jí)之間的關(guān)系,以表明哪個(gè)學(xué) 生在哪個(gè)班。指定實(shí)體屬性一旦設(shè)計(jì)者定義了實(shí)體間關(guān)聯(lián),下一步就是去指定每個(gè)實(shí)體的屬 性。這是實(shí)現(xiàn)列的使用,如右圖所示由工資水平實(shí)體所建立的工資水 平表。1辿任圾島池酷亂歷,戰(zhàn)-7001n制工1如口0020()1jCUIJ二3ml里mono吐懶重復(fù)步驟:我們?nèi)匀辉谠卦诙x了實(shí)體、關(guān)聯(lián)以及屬性之后,設(shè)計(jì)者往往要多重復(fù)幾次數(shù) 據(jù)建模過(guò)程。當(dāng)我們?cè)诨仡欔P(guān)聯(lián)時(shí),就會(huì)發(fā)現(xiàn)需要建立新的實(shí)體。比 如,當(dāng)討論飾品庫(kù)存表和與它相關(guān)的客戶訂單時(shí),就會(huì)發(fā)現(xiàn)需要制定

50、一個(gè)送貨約束表。一旦設(shè)計(jì)過(guò)程完成,下面將要建立實(shí)際的數(shù)據(jù)庫(kù)表。邏輯數(shù)據(jù)庫(kù)的設(shè)計(jì)過(guò)程不會(huì)牽涉實(shí)際執(zhí)行中的問(wèn)題。然而,一旦設(shè)計(jì)進(jìn)入到實(shí)際 的運(yùn)作,數(shù)據(jù)庫(kù)管理員就會(huì)很快讓設(shè)計(jì)者從理想回到現(xiàn)實(shí)中來(lái)。結(jié)果, 設(shè)計(jì)就可能需要再次構(gòu)想以求得理想的數(shù)據(jù)庫(kù)存運(yùn)行與預(yù)算和進(jìn)度 之間的平衡。Database Management SystemSource : Database and Network JournalAuthor : David AndersonYou know that a data is a collectionof logically related dataelements that may

51、be structured in various wa ys to meet the multiple processing and retrieval needs of organizations and individuals. There' snothing 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,

52、 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

53、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 dat

54、a contents in order to extract answers to nonrecurring and unplanned questions that aren ' tavailable in regular reports. These questions might initially b e vague and/or poorly defined, but people can “ browse " through the database until they have the needed information. In short, the DBM

55、S will“manage' the stored data itemsand 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 needingspecialinformationmay communicate their needsto aprogrammers,who,when time permits, willinformatio

56、n.Theavailability 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 integratedata elements fromseveral files to answer speci

57、fic userinquiries 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. T

58、he DBMS may then Employ one of the following logical structuring techniques during storage access, and retrieval operation: list structures, hierarchical (tree) structures, and network structures, relational structures.1. List structures. In this logical approach, records are linked together by the use of pointers. A pointer is a data item in one record that identifies the storage location

溫馨提示

  • 1. 本站所有資源如無(wú)特殊說(shuō)明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請(qǐng)下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請(qǐng)聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁(yè)內(nèi)容里面會(huì)有圖紙預(yù)覽,若沒(méi)有圖紙預(yù)覽就沒(méi)有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 人人文庫(kù)網(wǎng)僅提供信息存儲(chǔ)空間,僅對(duì)用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對(duì)用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對(duì)任何下載內(nèi)容負(fù)責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請(qǐng)與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時(shí)也不承擔(dān)用戶因使用這些下載資源對(duì)自己和他人造成任何形式的傷害或損失。

最新文檔

評(píng)論

0/150

提交評(píng)論