數(shù)據(jù)庫管理外文翻譯

1、<p><b>　　數(shù)據(jù)庫管理</b></p><p>　　數(shù)據(jù)庫（有時拼成Database）也稱為電子數(shù)據(jù)庫，是指由計算機特別組織的用下快速查找和檢索的任意的數(shù)據(jù)或信息集合。數(shù)據(jù)庫與其它數(shù)據(jù)處理操作協(xié)同工作，其結(jié)構(gòu)要有助于數(shù)據(jù)的存儲、檢索、修改和刪除。數(shù)據(jù)庫可存儲在磁盤或磁帶、光盤或某些輔助存儲設(shè)備上。</p><p>　　一個數(shù)據(jù)庫由一個文件或文件集合組

2、成。這些文件中的信息可分解成一個個記錄，每個記錄有一個或多個域。域是數(shù)據(jù)庫存儲的基本單位，每個域一般含有由數(shù)據(jù)庫描述的屬于實體的一個方面或一個特性的信息。用戶使用鍵盤和各種排序命令，能夠快速查找、重排、分組并在查找的許多記錄中選擇相應(yīng)的域，建立特定集上的報表。</p><p>　　數(shù)據(jù)庫記錄和文件的組織必須確保能對信息進行檢索。早期的系統(tǒng)是順序組織的（如:字母順序、數(shù)字順序或時間順序）；直接訪問存儲設(shè)備的研制成功

3、使得通過索引隨機訪問數(shù)據(jù)成為可能。用戶檢索數(shù)據(jù)庫信息的主要方法是query（查詢）。通常情況下，用戶提供一個字符串，計算機在數(shù)據(jù)庫中尋找相應(yīng)的字符序列，并且給出字符串在何處出現(xiàn)。比如，用戶必須能在任意給定時間快速處理內(nèi)部數(shù)據(jù)。而且，大型企業(yè)和其它組織傾向于建立許多獨立的文件，其中包含相互關(guān)聯(lián)的甚至重疊的數(shù)據(jù)，這些數(shù)據(jù)、處理活動經(jīng)常需要和其它文件的數(shù)據(jù)相連。為滿足這些要求，開發(fā)郵各種不同類型的數(shù)據(jù)庫管理系統(tǒng)，如：非結(jié)構(gòu)化的數(shù)據(jù)庫、層次型數(shù)

4、據(jù)庫、網(wǎng)絡(luò)型數(shù)據(jù)庫、關(guān)系型數(shù)據(jù)庫、面向?qū)ο笮蛿?shù)據(jù)庫。</p><p>　　在非結(jié)構(gòu)化的數(shù)據(jù)庫中，按照實體的一個簡單列表組織記錄；很多個人計算機的簡易數(shù)據(jù)庫是非結(jié)構(gòu)的。層次型數(shù)據(jù)庫按樹型組織記錄，每一層的記錄分解成更小的屬性集。層次型數(shù)據(jù)庫在不同層的記錄集之間提供一個單一鏈接。與此不同，網(wǎng)絡(luò)型數(shù)據(jù)庫在不同記錄集之間提供多個鏈接，這是通過設(shè)置指向其它記錄集的鏈或指針來實現(xiàn)的。網(wǎng)絡(luò)型數(shù)據(jù)庫的速度及多樣性使其在企業(yè)中得到

5、廣泛應(yīng)用。當文件或記錄間的關(guān)系不能用鏈表達時，使用關(guān)系型數(shù)據(jù)庫。一個表或一個“關(guān)系”，就是一個簡單的非結(jié)構(gòu)列表。多個關(guān)系可通過數(shù)學(xué)關(guān)系提供所需信息。面向?qū)ο蟮臄?shù)據(jù)庫存儲并處理更復(fù)雜的稱為對象的數(shù)據(jù)結(jié)構(gòu)，可組織成有層次的類，其中的每個類可以繼承層次鏈中更高一級類的特性，這種數(shù)據(jù)庫結(jié)構(gòu)最靈活，最具適應(yīng)性。</p><p>　　很多數(shù)據(jù)庫包含自然語言文本信息，可由個人在家中使用。小型及稍大的數(shù)據(jù)庫在商業(yè)領(lǐng)域中占有越來越

6、重要的地位。典型的商業(yè)應(yīng)用包括航班預(yù)訂、產(chǎn)品管理、醫(yī)院的醫(yī)療記錄以及保險公司的合法記錄。最大型的數(shù)據(jù)庫通常用天政府部門、企業(yè)、大專院校等。這些數(shù)據(jù)庫存有諸如摘要、報表、成文的法規(guī)、通訊錄、報紙、雜志、百科全書、各式目錄等資料。索引數(shù)據(jù)庫包含參考書目或用于找到相關(guān)書籍、期刊及其它參考文獻的索引。目前有上萬種可公開訪問的數(shù)據(jù)庫，內(nèi)容包羅萬象，從法律、醫(yī)學(xué)、工程到新聞、時事、游戲、分類廣告、指南等?？茖W(xué)家、醫(yī)生、律師、財經(jīng)分析師、股票經(jīng)紀人等

7、專家和各類研究者越來越多地依賴這些數(shù)據(jù)庫從大量的信息中做快速的查找訪問。</p><p>　　數(shù)據(jù)庫管理系統(tǒng)的組織技術(shù)</p><p>　　順序的、直接的以及其他的文件處理方式常用于單個文件中數(shù)據(jù)的組織和構(gòu)造，而DBMS可綜合幾個文件的數(shù)據(jù)項以回答用戶對信息的查詢，這就意味著DBMS能夠訪問和檢索非關(guān)鍵記錄字段的數(shù)據(jù)，即DBMS能夠?qū)讉€大文件夾中邏輯相關(guān)的數(shù)據(jù)組織并連接在一起。</

8、p><p>　　邏輯結(jié)構(gòu)。確定這些邏輯關(guān)系是數(shù)據(jù)管理者的任務(wù)，由數(shù)據(jù)定義語言完成。DBMS在存儲、訪問和檢索操作過程中可選用以下邏輯構(gòu)造技術(shù)：</p><p>　　鏈表結(jié)構(gòu)。在該邏輯方式中，記錄通過指針鏈接在一起。指針是記錄集中的一個數(shù)據(jù)項，它指出另一個邏輯相關(guān)的記錄的存儲位置，例如，顧客主文件中的記錄將包含每個顧客的姓名和地址，而且該文件中的每個記錄都由一個賬號標識。在記賬期間，顧客可在不同

9、時間購買許多東西。公司保存一個發(fā)票文件以反映這下地交易，這種情況下可使用鏈表結(jié)構(gòu)，以顯示給定時間內(nèi)未支付的發(fā)票。顧客文件中的每個記錄都包含這樣一個字段，該字段指向發(fā)票文件中該顧客的第一個發(fā)票的記錄位置，該發(fā)票記錄又依次與該顧客的下一個發(fā)票記錄相連，此鏈接的最后一個發(fā)票記錄由一個作為指針的特殊字符標識。</p><p>　　層次（樹型）結(jié)構(gòu)。該邏輯方式中，數(shù)據(jù)單元的多級結(jié)構(gòu)類似一棵“倒立”的樹，該樹的樹根在頂部，而

10、樹枝向下延伸。在層次（樹型）結(jié)構(gòu)中存在主-從關(guān)系，惟一的根數(shù)據(jù)下是從屬的元或節(jié)點，而每個元或樹枝都只有一個所有者，這樣，一個customer（顧客）擁有一個invoice（發(fā)票），而invoice（發(fā)票）又有從屬項。在樹型結(jié)構(gòu)中，樹枝不能相連。</p><p>　　網(wǎng)狀結(jié)構(gòu)。網(wǎng)狀結(jié)構(gòu)不像樹型結(jié)構(gòu)那樣不允許樹枝相連，它允許節(jié)點間多個方向連接，這樣，每個節(jié)點都可能有幾個所有者，中央電視臺它又可能擁有任意多個其他數(shù)據(jù)單

11、元。數(shù)據(jù)管理軟件允許從文件的任一記錄開始提取該結(jié)構(gòu)中的所需信息。</p><p>　　關(guān)系型結(jié)構(gòu)。關(guān)系型結(jié)構(gòu)由許多表格組成，數(shù)據(jù)則以“關(guān)系”的形式存儲在這些表中。例如，可建立一些關(guān)系表，將大學(xué)課程同任課教師及上課地點連接起來。為了找到英語課的上課地點和教師名，首先查詢課程/教師關(guān)系表得到名字（為“Fitt”），再查詢課程/地點關(guān)系表得到地點（“Main 142”），當然，也可能有其他關(guān)系。這是一個相當新穎的數(shù)據(jù)庫

12、組織技術(shù)，將來有望得到廣泛應(yīng)用。</p><p>　　物理結(jié)構(gòu)。人們總是為了各自的目的，按邏輯方式設(shè)想或組織數(shù)據(jù)。因此，在一個具體應(yīng)用中，記錄R1和R2是邏輯相連且順序處理的，但是，在計算機系統(tǒng)中，這些在一個應(yīng)用中邏輯相鄰的記錄，物理位置完全可能不在一起。記錄在介質(zhì)和硬件中的物理結(jié)構(gòu)不僅取決于所采用的I/O設(shè)備、存儲設(shè)備及輸入輸出和存取技術(shù)，而且還取決于用戶定義的R1和R2中數(shù)據(jù)的邏輯關(guān)系。例如，R1和R2可能是

13、持有信用卡的顧客記錄，而顧客要求每兩周將貨物運送到同一個城市的同一個街區(qū)，而從運輸部門的管理者看，R1和R2是按地理位置組織的運輸記錄的順序項，但是在A/R應(yīng)用中，可找到R1長表示的顧客，并且可根據(jù)其完全不同的賬號處理他們的賬目。簡言之，在許多計算機化的信息記錄中，存儲記錄的物理位置用戶是看不見的。</p><p>　　Oracle的數(shù)據(jù)庫管理功能</p><p>　　Oracle 包括許

14、多使數(shù)據(jù)庫易于管理的功能，分三部分討論：Oracle 企業(yè)管理器、附加包、備份和恢復(fù)。</p><p>　　Oracle 企業(yè)管理器</p><p>　　和任何數(shù)據(jù)庫服務(wù)器一樣，Oracle 數(shù)據(jù)庫服務(wù)器包括以下部分：Oracle 企業(yè)管理器（IM）、一個帶有圖形接口的用于管理數(shù)據(jù)庫用戶、實例和提供Oracle 環(huán)境等附加信息功能（如：復(fù)制）的數(shù)據(jù)庫管理工具框架。</p>&

15、lt;p>　　在Oracle8i數(shù)據(jù)庫之前，EM 軟件必須安裝在Windows95/98或者基于NT 的系統(tǒng)中，而且每個庫每次只能由一個數(shù)據(jù)庫管理者訪問。如今你可以通過瀏覽器或者把EM 裝入Window95/98/2000 或基于NT 的系統(tǒng)中來使用EM。多個數(shù)據(jù)庫管理員可以同時訪問EM庫。在Oracle9i的EM版中，超級管理員可以定義在普通管理員的控制臺上顯示的服務(wù)，并能建立管理區(qū)域。</p><p>

16、<b>　　附加包</b></p><p>　　正如下面所描述的那樣，Oracle可使用一些可選的附加包，還有用于Oracle應(yīng)用程序和SAP R/3的管理包。</p><p><b>　　（1）標準管理包</b></p><p>　　Oracle的標準管理包提供了用于小型Oracle數(shù)據(jù)庫的管理工具（如：Oracle服務(wù)

17、器/標準版）。功能包括：對數(shù)據(jù)庫爭用、輸入/輸出、裝載、內(nèi)存使用和實例、對話分析、索引調(diào)整進行監(jiān)控，并改變調(diào)查和跟蹤。</p><p><b>　?。?）診斷包</b></p><p>　　利用診斷包，可以監(jiān)控、診斷及維護企業(yè)版數(shù)據(jù)庫、操作系統(tǒng)和應(yīng)用程序的安全。用有關(guān)歷史和實時的分析，可自動的在問題發(fā)生前將其消除。診斷包還提供空間管理功能，有助于對未來系統(tǒng)資源需要的計

18、劃和跟蹤。</p><p><b>　　（3）調(diào)整包</b></p><p>　　利用調(diào)整包，可確定并調(diào)整企業(yè)版數(shù)據(jù)庫和應(yīng)用系統(tǒng)的瓶頸，如效率低的SQL、很差的數(shù)據(jù)設(shè)計、系統(tǒng)資源的不當使用，從而優(yōu)化系統(tǒng)性能。調(diào)整包能提前發(fā)現(xiàn)調(diào)整時機，并自動生成分析和需求變化來調(diào)整系統(tǒng)。</p><p><b>　?。?）變化管理包</b>

19、</p><p>　　變化管理包在升級企業(yè)版數(shù)據(jù)庫時幫助排錯和避免丟失數(shù)據(jù)，以達到支持新的應(yīng)用程序的目的。該包能分析與應(yīng)用程序變動有關(guān)的影響和復(fù)雜依賴關(guān)系并自動升級數(shù)據(jù)庫。用戶可使用一種簡單的向?qū)О幢匾牟襟E來升級。</p><p><b>　?。?）可用性</b></p><p>　　Oracle 企業(yè)管理器可用管理Oracle標準版或企業(yè)版

20、。在標準版中，用于診斷、調(diào)整和改變實例的附加功能由標準管理包提供。對于企業(yè)版，這些附加的功能由單獨的診斷包、調(diào)整包和變化管理包提供。</p><p><b>　　3. 備份和恢復(fù)</b></p><p>　　正如每個數(shù)據(jù)庫管理者所熟知的，對數(shù)據(jù)庫做備份是一件很普通但又必要的工作。一次不當?shù)膫浞輹箶?shù)據(jù)庫難于恢復(fù)甚至不可恢復(fù)。不幸的是，人們往往在相關(guān)系統(tǒng)發(fā)生故障而丟失了

21、重要的業(yè)務(wù)數(shù)據(jù)后才認識到這項日常工作的重要。</p><p>　　下面介紹一些實現(xiàn)數(shù)據(jù)庫備份操作的產(chǎn)品技術(shù)。 </p><p><b>　　(1)恢復(fù)管理者</b></p><p>　　典型的備份包括完整的數(shù)據(jù)庫備份（最普通的類型）、桌

22、面空間備份、數(shù)據(jù)文件備份、控件備份和存檔注冊備份。Oracle8i為數(shù)據(jù)服務(wù)器管理備份和恢復(fù)管理器（RMAN）。以前，Oracle的企業(yè)備份工具（EBU）在一些平臺上提供了相似的解決方案。然而，RMAN及其存儲在Oracle數(shù)據(jù)庫中的恢復(fù)目錄提供了更完整的解決方案。RMAN可以自動定位、備份、存儲并恢復(fù)數(shù)據(jù)文件、控制文件和存檔記錄注冊。當備份到期時，Oracle9i的RMAN可以重新啟動備份和恢復(fù)來實現(xiàn)恢復(fù)窗口的任務(wù)。Oracle企業(yè)管

23、理器的備份管理器曾RMAN提供基于圖形用戶界面的接口。</p><p>　　(2)附加備份和恢復(fù)</p><p>　　RMAN能夠執(zhí)行企業(yè)版數(shù)據(jù)庫的附加備份。附加備份僅備份上一次備份后改變了的數(shù)據(jù)文件、桌面空間或數(shù)據(jù)庫塊，因此，它比完整的備份占用時間短而且速度快。RMAN也能執(zhí)行及時指向的恢復(fù)，這種恢復(fù)能在一個不期望的事件發(fā)片之前（如錯誤的刪除表格）恢復(fù)數(shù)據(jù)。</p><

24、;p>　　(3)連續(xù)存儲管理器</p><p>　　許多媒體軟件商支持RMAN。Oracle捆綁了連續(xù)存儲管理器來提供媒體管理服務(wù)，包括為至多四臺設(shè)備提供磁帶容量跟蹤的服務(wù)。RMAN界面自動地與媒體管理軟件一起來管理備份和恢復(fù)操作必須的磁帶設(shè)備。</p><p><b>　　(4)可用性</b></p><p>　　盡管標準版和企業(yè)版的O

25、racle都有基本的恢復(fù)機制，但附加備份僅限于企業(yè)版。</p><p>　　Oracle 和 SQL Server 的比較選擇</p><p>　　我不得不決定是使用Oracle數(shù)據(jù)庫及其數(shù)據(jù)庫開發(fā)系統(tǒng)，還是選擇配有Visual Studio的Microsoft SQL Server。這個決策將決定我們今后Web項目的方向。這兩種組合各有什么優(yōu)勢和劣勢呢？</p><p

26、>　　Lori: 決定選擇哪種方案將取決于你目前的工作平臺。例如，如果你想實現(xiàn)一種基于Web的數(shù)據(jù)庫應(yīng)用，而且你的工作平臺只是Windows,那么SQL Sever和Visual Studio 組件就是一個不錯的選擇。但是對于混合平臺，則最好選擇Oracle解決方案。</p><p>　　還要考慮一些其他的因素，例如你可以獲得哪些額外的功能以及需要哪些技術(shù)。WebDB是一種內(nèi)容管理和開發(fā)工具。WebDB是一

27、種基于瀏覽器的工具，有利于方便地創(chuàng)建內(nèi)容，以及提供導(dǎo)航和維護工具。這對于已經(jīng)使用Oracle的機構(gòu)則是一個很好的解決方案。Oracle比SQL Server更易于調(diào)整，但你需要身邊有一個稱職的Oracle管理員。</p><p>　　SQL Server/Visual Studio方法相對來說較難使用，需要一個有經(jīng)驗的面向?qū)ο蟮木幊倘藛T或一些全面的訓(xùn)練。但是，你只要花上1619美元就可以獲得許多Visual St

28、udio的開發(fā)工具：Visual Basic，Visual C++，以及Visual InterDev。另外，你需要再加上SQL Server的費用，1999美元就可以擁有10個客戶端，或用3999美元獲得25個客戶端-與Oracle的費用相比則便宜些。</p><p>　　Oracle也有一個組件解決方案，根據(jù)所選擇平臺的不同，費用也不同，最低為6767美元。Oracle.com套件不僅包括WebDB和Orac

29、le8，還包括其他的開發(fā)工具，如Oracle應(yīng)用服務(wù)器、JDeveloper和iWorkplace模板，該套件與Microsoft 方案相比能運行在更多的平臺上。如果你剛創(chuàng)業(yè)或是一個小型或中型企業(yè)，則Oracle套件是一個很好的選擇方案。以組件的形式購買這些工具要比單獨采購的花費要少些。</p><p>　　對這兩種方案的選擇主要取決于你的技術(shù)水平、硬件資源和資金預(yù)算。我希望以上所說的能對你的決策有一定幫助。&l

30、t;/p><p>　　Brooks: 我完全同意對這種方案的選擇在很大程度上取決于你目前所配有的基礎(chǔ)設(shè)施和所具有的專門技術(shù)。如果很難做出抉擇，你就需要考慮由誰來做這項工作，以及你的重點是什么。</p><p>　　這兩種產(chǎn)品采用不同的方法，并反映出這兩個開發(fā)商的不同特點。Oracle是為那些優(yōu)秀的程序員和項目負責(zé)人進行的專業(yè)化開發(fā)而設(shè)計的產(chǎn)品。學(xué)習(xí)時間校長，該方案的費用也較高；但是如果你堅持下

31、去，最終就會獲得更好的靈活性，以及更高的可靠性。</p><p>　　如果你的項目時間很緊，而且你沒有時間或金錢來雇傭一個花銷很大、經(jīng)驗非常豐富的開發(fā)隊伍，你也許會發(fā)現(xiàn)選擇Oracle方案會很容易使你陷入困境。沒有比開發(fā)一個質(zhì)量很差的Oracle應(yīng)用程序更糟糕的了。</p><p>　　Microsoft 所提供的解決方案則致力于快速開發(fā)和低本實現(xiàn)。開發(fā)工具、服務(wù)器、以及你所需要的開發(fā)人員

32、的花費都比較少。若要使項目快速啟動，選擇SQL Server和Visual Studio則是很好的方式。</p><p>　　當然，有得必有失。在使用Visual Studio 和SQL Server 的過程中，我所遇到的主要問題就是，只能使用Microsoft 操作系統(tǒng)和Intel硬件。如果有一天你需要支持成百上千個用戶，你除了購買上百個服務(wù)器而外別無他法，這會給管理帶來很大麻煩。</p><

33、;p>　　如果你采用Microsoft 方法，就表明你可能只需要Visual Interdev即可。如果你已經(jīng)知道你將開發(fā)Visual Basic或Visual C++里的ActiveX組件這就是一個預(yù)示，表明你需要更多的來考慮Oracle的解決方案。</p><p>　　我想強調(diào)的是，盡管這兩種平臺有它們各自的優(yōu)點和缺點，如果你使用正確，你用任何一個都可以設(shè)計出具有世界水平的應(yīng)用程序。如果你的組織傾向于某

34、種產(chǎn)品，一定要跟隨這種趨向。如果你是從零起點開始，就需要問問自己，你的組織是更傾向于完美主義還是實用主義，并要清楚這兩種主義都有缺點。</p><p>　　Database Management</p><p>　　Database (sometimes spelled database) is also called an electronic database, referring t

35、o any collections 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 conj

36、unction with various data-processing operations. Database can be stored on magnetic disk or tape, optical disk, or some other secondary storage device.</p><p>　　A database consists of a file or a set of file

37、s. The information in the these files may be broken down into records, each of which consists of one or more fields are the basic units of data storage, and each field typically contains information pertaining to one asp

38、ect 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 pa

39、rticular aggre</p><p>　　Database records and files must be organized to allow retrieval of the information. Early system were arranged sequentially (i.e., alphabetically, numerically, or chronologically); th

40、e development of direct-access storage devices made possible random access to data via indexes. Queries are the main way users retrieve database information. Typically the user provides a string of characters, and the co

41、mputer searches the database for a corresponding sequence and provides the source materials in wh</p><p>　　The many users of a large database must be able to manipulate the information within it quickly at a

42、ny given time. Moreover, large business and other organizations tend to build up many independent files containing related and even overlapping data, and their data, processing activities often require the linking of dat

43、a from several files. Several different types of database management systems have been developed to support these requirements: flat, hierarchical, network, relational, and object-</p><p>　　In flat databases

44、, records are organized according to a simple list of entities; many simple databases for personal computers are flat in structure. The records in hierarchical databases are organized in a treelike structure, with each l

45、evel of records branching off into a set of smaller categories. Unlike hierarchical databases, which provide single links between sets of records at different levels, network databases create multiple linkages between se

46、ts by placing links, or pointers, to one se</p><p>　　The information in many databases consists of natural-language texts of documents; number-oriented database primarily contain information such as statisti

47、cs, tables, financial data, and raw scientific and technical data. Small databases can be maintained on personal-computer systems and may be used by individuals at home. These and larger databases have become increasingl

48、y important in business life. Typical commercial applications include airline reservations, production management, medical rec</p><p>　　DBMS Structuring Techniques</p><p>　　Sequential, direct, a

49、nd other file processing approaches are 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 for information. That is, th

50、e DBMS is able to structure and tie together the logically related data from several large files. </p><p>　　Logical Structures. Identifying these logical relationships is a job of the data administrator. A d

51、ata definition language is used for this purpose. The DBMS may then employ one of the following logical structuring techniques during storage access, and retrieval operations.</p><p>　　List structures. In th

52、is 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 of another logically related record. Records in a customer master file,

53、 for example, will contain the name and address of each customer, and each record in this file is identified by an account number. During an accounting period, a customer may buy a number of items on different days. Thus

54、, the company may maintain an invoice </p><p>　　Hierarchical (tree) structures. In this logical approach, data units are structured in multiple levels that graphically resemble an “upside down” tree with the

55、 root at the top and the branches formed below. There’s a superior-subordinate relationship in a hierarchical (tree) structure. Below the single-root data component are subordinate elements or nodes, each of which, in tu

56、rn, “own” one or more other elements (or none). Each element or branch in this structure below the root has only a single</p><p>　　Network Structures. Unlike the tree approach, which does not permit the conn

57、ection of branches, the network structure permits the connection of the nodes in a multidirectional manner. Thus, each node may have several owners and may, in turn, own any number of other data units. Data management so

58、ftware permits the extraction of the needed information from such a structure by beginning with any record in a file.</p><p>　　Relational structures. A relational structure is made up of many tables. The dat

59、a are stored in the form of “relations” in these tables. For example, relation tables could be established to link a college course with the instructor of the course, and with the location of the class.</p><p&

60、gt;　　To find the name of the instructor and the location of the English class, the course/instructor relation is searched to get the name (“Fitt”), and the course/location relation is a relatively new database structurin

61、g approach that’s expected to be widely implemented in the future.</p><p>　　Physical Structures. People visualize or structure data in logical ways for their own purposes. Thus, records R1 and R2 may always

62、be logically linked and processed in sequence in one particular application. However, in a computer system it’s quite possible that these records that are logically contiguous in one application are not physically stored

63、 together. Rather, the physical structure of the records in media and hardware may depend not only on the I/O and storage devices and techniques used</p><p>　　Database Management Features of Oracle </p>

64、;<p>　　Oracle includes many features that make the database easier to manage. We’ve divided the discussion in this section into three categories: Oracle Enterprise Manager, add-on packs, backup and recovery.</p

65、><p>　　1.Oracle Enterprise Manager</p><p>　　As part of every Database Server, Oracle provides the Oracle Enterprise Manager (EM), a database management tool framework with a graphical interface use

66、d to manage database users, instances, and features (such as replication) that can provide additional information about the Oracle environment.</p><p>　　Prior to the Oracle8i database, the EM software had to

67、 be installed on Windows 95/98 or NT-based systems and each repository could be accessed by only a single database manager at a time. Now you can use EM from a browser or load it onto Windows 95/98/2000 or NT-based syste

68、ms. Multiple database administrators can access the EM repository at the same time. In the EM repository for Oracle9i, the super administrator can define services that should be displayed on other administrators’ console

69、s, and</p><p>　　2.Add-on packs</p><p>　　Several optional add-on packs are available for Oracle, as described in the following sections. In addition to these database-management packs, management

70、 packs are available for Oracle Applications and for SAP R/3.</p><p>　　(1)standard Management Pack </p><p>　　The Standard Management Pack for Oracle provides tools for the management of small Or

71、acle databases (e.g., Oracle Server/Standard Edition). Features include support for performance monitoring of database contention, I/O, load, memory use and instance metrics, session analysis, index tuning, and change in

72、vestigation and tracking.</p><p>　　(2)Diagnostics Pack </p><p>　　You can use the Diagnostic Pack to monitor, diagnose, and maintain the health of Enterprise Edition databases, operating systems,

73、 and applications. With both historical and real-time analysis, you can automatically avoid problems before they occur. The pack also provides capacity planning features that help you plan and track future system-resourc

74、e requirements. </p><p>　　(3)Tuning Pack</p><p>　　With the Tuning Pack, you can optimise system performance by identifying and tuning Enterprise Edition databases and application bottlenecks suc

75、h as inefficient SQL, poor data design, and the improper use of system resources. The pack can proactively discover tuning opportunities and automatically generate the analysis and required changes to tune the systems. &

76、lt;/p><p>　　(4)Change Management Pack</p><p>　　The Change Management Pack helps eliminate errors and loss of data when upgrading Enterprise Edition databases to support new applications. It impact

77、and complex dependencies associated with application changes and automatically perform database upgrades. Users can initiate changes with easy-to-use wizards that teach the systematic steps necessary to upgrade.</p>

78、;<p>　　(5)Availability</p><p>　　Oracle Enterprise Manager can be used for managing Oracle Standard Edition and/or Enterprise Edition. Additional functionality is provided by separate Diagnostics, Tuni

79、ng, and Change Management Packs.</p><p>　　3.Backup and Recovery</p><p>　　As every database administrator knows, backing up a database is a rather mundane but necessary task. An improper backup m

80、akes recovery difficult, if not impossible. Unfortunately, people often realize the extreme importance of this everyday task only when it is too late –usually after losing business-critical data due to a failure of a rel

81、ated system.</p><p>　　The following sections describe some products and techniques for performing database backup operations.</p><p>　　(1)Recovery Manager</p><p>　　Typical backups i

82、nclude complete database backups (the most common type), database backups, control file backups, and recovery of the database. Previously, Oracle’s Enterprise Backup Utility (EBU) provided a similar solution on some plat

83、forms. However, RMAN, with its Recovery Catalog stored in an Oracle database, provides a much more complete solution. RMAN can automatically locate, back up, restore, and recover databases, control files, and archived re

84、do logs. RMAN for Oracle9i can restart back</p><p>　　(2)Incremental backup and recovery</p><p>　　RMAN can perform incremental backups of Enterprise Edition databases. Incremental backups back up

85、 only the blocks modified since the last backup of a datafile, tablespace, or database; thus, they’re smaller and faster than complete backups. RMAN can also perform point-in-time recovery, which allows the recovery of d

86、ata until just prior to a undesirable event.</p><p>　　(3)Legato Storage Manager</p><p>　　Various media-management software vendors support RMAN. Oracle bundles Legato Storage Manager with Oracle

87、 to provide media-management services, including the tracking of tape volumes, for up to four devices. RMAN interfaces automatically with the media-management software to request the mounting of tapes as needed for backu

88、p and recovery operations.</p><p>　　(4)Availability</p><p>　　While basic recovery facilities are available for both Oracle Standard Edition and Enterprise Edition, incremental backups have typic

89、ally been limited to Enterprise Edition.</p><p>　　Data Independence </p><p>　　An important point about database systems is that the database should exist independently of any of the specific app

90、lications. Traditional data processing applications are data dependent. COBOL programs contain file descriptions and record descriptions that carefully describe the format and characteristics of the data.</p><

91、p>　　Users should be able to change the structure of the database without affecting the applications that use it. For example, suppose that the requirements of your applications change. A simple example would be expand

92、ing ZIP codes from five digits to nine digits. On a traditional approach using COBOL programs each individual COBOL application program that used that particular field would have to be changed, recompiled, and retested.

93、The programs would be unable to recognize or access a file that had</p><p>　　Most database programs provide the ability to change the database structure by simply changing the ZIP code field and the data-ent

94、ry form. In this case, data independence allows for minimal disruption of current and existing applications. Users can continue to work and can even ignore the nine-digit code if they choose. Eventually, the file will be

95、 converted to the new nine-digit ZIP code, but the ease with which the changeover takes place emphasizes the importance of data independence.</p><p>　　Data Integrity</p><p>　　Data integrity refe

96、rs to the accuracy, correctness, or validity of the data in the database. In a database system, data integrity means safeguarding the data against invalid alteration or destruction arise. The first has to do with many us

97、ers accessing the database concurrently. For example, if thousands of travel agents and airline reservation clerks are accessing the database concurrently. For example, if thousands of travel agents and airline reservati

98、on clerks are accessing the same database</p><p>　　The second complication relates to hardwires, software, or human error during the course of processing and involves database transactions treated as a singl

99、e . For example, an agent booking an airline reservation involves several database updates (i.e., adding the passenger’s name and address and updating the seats-available field), which comprise a single transaction. The