ALLBASE/SQL Database Administration Guide (36216-90214)

ManualsBrandsHP ManualsSoftwareMPE/iX 6.5 Operating System

Summary of content (571 pages)

PAGE 1
HP 3000 MPE/iX Computer Systems ALLBASE/SQL Database Administration Guide ABCDE HP Part No. 36216-90005 Printed in U.S.A.
PAGE 2
The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or tness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
PAGE 3
Printing History The following table lists the printings of this document, together with the respective release dates for each edition. The software version indicates the version of the software product at the time this document was issued. Many product releases do not require changes to the document. Therefore, do not expect a one-to-one correspondence between product releases and document editions.
PAGE 4
ALLBASE/SQL Documents Title ALLBASE/NET User's Guide ALLBASE/SQL Advanced Application Programming Guide ALLBASE/SQL C Application Programming Guide ALLBASE/SQL COBOL Application Programming Guide ALLBASE/SQL Database Administration Guide ALLBASE/SQL FORTRAN Application Programming Guide ALLBASE/SQL Message Manual ALLBASE Pascal Application Programming Guide ALLBASE/SQL Performance and Monitoring Guidelines ALLBASE/SQL Reference Manual ISQL Reference Manual for ALLBASE/SQL and IMAGE/SQL Up and Running with
PAGE 5
Preface This manual describes how to design, create, and maintain ALLBASE/SQL databases on HP 3000 computers running under the MPE/iX operating system. ALLBASE/SQL is Hewlett-Packard's proprietary relational database management product. MPE/iX, Multiprogramming Executive with Integrated POSIX, is the latest in a series of forward-compatible operating systems for the HP 3000 line of computers.
PAGE 6
What's New in this Release G.1 and G.2 New Features The following table highlights the new or changed functionality added in G.1 and G.2 releases, and shows you where each feature is documented. New Features in ALLBASE/SQL Releases G.1 and G.2 Feature (Category) Description New operand to Adds an operand to concatenate concatenate strings character or binary strings in an expression. New operand: jj (Standards) Documented in . . . ALLBASE/SQL Reference Manual , \Expressions.
PAGE 7
New Features in ALLBASE/SQL Releases G.1 and G.2 (continued) Feature (Category) Syntax added to DELETE (Usability, Performance) Description Documented in . . . Automates execution of COMMIT ALLBASE/SQL Reference Manual , DELETE in \SQL Statements." WORK at the beginning of the DELETE and after each batch of rows is deleted when WITH AUTOCOMMIT is used. Reduces log-space and shared-memory requirements. WITH AUTOCOMMIT cannot be used in some cases (see the DELETE statement).
PAGE 8
New Features in ALLBASE/SQL Releases G.1 and G.2 (continued) Feature (Category) Description Documented in . . . Allow or disallow authority to create modules. (Usability) Grants or revokes the ability to create modules for speci c users. New attributes for GRANT and REVOKE: INSTALL. ALLBASE/SQL Reference Manual , GRANT, REVOKE in \SQL Statements." Script for migration to a new release (Usability, Tools) Provides SQLINSTL script for migration to a new release of ALLBASE/SQL.
PAGE 9
G.0 Features The following table highlights the new or changed functionality in release G.0, and shows you where each feature is documented. New Features in ALLBASE/SQL Release G.0 Feature (Category) Description Documented in . . . Stored procedures (Usability) Provides additional stored procedure functionality for application programs. Allows declaration of a procedure cursor and fetching of multiple rows within a procedure to applications. New statement: ADVANCE.
PAGE 10
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) Description Documented in . . . New SQLGEN GENERATE parameters (Usability) Generates SQL statements necessary to recreate modi ed access plans for module sections. New syntax for GENERATE: DEFAULTSPACE, MODOPTINFO, PARTITION, PROCOPTINFO, SPACEAUTH. ALLBASE/SQL Database Administration Guide , \SQLGEN Commands" appendix.
PAGE 11
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) High Availability Description Provides a collection of features to keep systems available nonstop including: Partial STORE and RESTORE, Partial rollforward recovery, DBEFiles in di erent groups (MPE/iX), detaching and attaching database objects, CHECKPOINT host variable, changing log les, console messages logged to a le, generating fewer log records by using TRUNCATE TABLE to delete rows, and new system catalog information.
PAGE 12
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) New and changed SQLUtil commands for increased availability (High Availability) Description Documented in . . . Adds support for high availability ALLBASE/SQL Database Administration Guide , \SQLUtil" appendix. and System Management Intrinsics. Intended for non-stop, continuously available operations. New SQLUtil commands: ATTACHFILE, CHANGELOG, DETACHFILE, RESTORE PARTIAL, STORE PARTIAL, STOREINFO, STOREONLINE PARTIAL, WRAPDBE.
PAGE 13
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) Description Documented in . . . Optimizer enhancement (Performance) ALLBASE/SQL Performance and Uses a more e cient algorithm that signi cantly reduces the time Monitoring Guidelines , \Optimization" in \Basic Concepts in ALLBASE/SQL to generate the access plan. Performance." Access plan modi cation (Performance) Allows modi cation of access plans for stored section to optimize performance. View the plan with SYSTEM.SETOPTINFO.
PAGE 14
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) I/O performance improvement (Performance) Description Optimizes I/O for initial load, index build, serial scans, internal data restructuring, le activity, pseudo mapped les and temporary les. See the following features for new and changed syntax. Documented in . . . ALLBASE/SQL Reference Manual , \SQL Statements." Deletes all rows in a speci ed table ALLBASE/SQL Reference Manual , TRUNCATE TRUNCATE TABLE in \SQL Statements.
PAGE 15
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) Description Documented in . . . Modi ed SET options (Performance) Provides better performance for LOADs and UNLOADs. Specify bu er size, status reporting for LOAD/UNLOAD or exclusive lock for data table. AUTOSAVE row limit increased to 2147483647. New and changed SET options: LOAD BUFFER, LOAD ECHO, AUTOLOCK, AUTOSAVE.
PAGE 16
New Features in ALLBASE/SQL Release G.0 (continued) Feature (Category) Description Increased memory for MPE/iX (HP-UX shared memory allocation is unchanged) (Performance) Increases memory up to 50,000 data bu er pages and 2,000 run time control block pages. Increases the limits signi cantly allowing allocation of enough data bu er pages to keep the entire DBEnvironment in memory if desired for performance.
PAGE 17
Conventions UPPERCASE In a syntax statement, commands and keywords are shown in uppercase characters. The characters must be entered in the order shown; however, you can enter the characters in either uppercase or lowercase. For example: COMMAND can be entered as any of the following: command Command COMMAND It cannot, however, be entered as: comm italics comamnd In a syntax statement or an example, a word in italics represents a parameter or argument that you must replace with the actual value.
PAGE 18
Conventions (continued) [ ... ] In a syntax statement, horizontal ellipses enclosed in brackets indicate that you can repeatedly select the element(s) that appear within the immediately preceding pair of brackets or braces. In the example below, you can select parameter zero or more times. Each instance of parameter must be preceded by a comma: [,parameter][...
PAGE 19
Contents 1. DBA Tasks and Tools Tasks for the DBA . . . . . . . . . . . . . . . . . . . . . Creating Logical and Physical Objects . . . . . . . . . . . . Starting and Stopping DBE Sessions . . . . . . . . . . . . Establishing Multiple DBEnvironment Connections . . . . . . Managing ALLBASE/SQL Logs . . . . . . . . . . . . . . De ning Logs . . . . . . . . . . . . . . . . . . . . . Logs and Recovery . . . . . . . . . . . . . . . . . . . LOG FULL Condition . . . . . . . . . . . . . . . . . .
PAGE 20
Performing an Audit . . . . . . . . SQLAudit Result Files . . . . . . . . Checking the Exit Status . . . . . . . System Administration for ALLBASE/SQL Shared Memory Usage . . . . . . . . . Native Language Support . . . . . . . Network Administration . . . . . . . . Using NETUtil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 21
3. Physical Design Calculating Storage for Database Objects . . . . . . . . . . . . . . . . Understanding DBEFile Characteristics . . . . . . . . . . . . . . . . Calculating Storage for Tables . . . . . . . . . . . . . . . . . . . . Calculating Row Length . . . . . . . . . . . . . . . . . . . . . . Calculating Rows per Page . . . . . . . . . . . . . . . . . . . . . Calculating Number of Pages . . . . . . . . . . . . . . . . . . . . Calculating Directory Overhead . . . . . . . . . . . . . . . . . . .
PAGE 22
Estimating Log File Size . . . . . . . . . . Example . . . . . . . . . . . . . . . . Calculating Temporary Disk Space . . . . . . . Controlling the Use of Temporary Space . . . . Estimating Shared Memory Requirements . . . . Estimating Runtime Control Block Bu er Pages E ects of Page and Row Level Locking . . . Running out of Shared Memory . . . . . . . Estimating Data Bu er Pages . . . . . . . . Setting the Memory Resident Bu er Flag . . . Estimating Log Bu er Pages . . . . . . . . .
PAGE 23
Granting/Revoking EXECUTE Authority . . . . . . . . . . . Granting/Revoking SECTIONSPACE or TABLESPACE Authority Veri cation of Authority . . . . . . . . . . . . . . . . . . . Managing DBEnvironment Sessions . . . . . . . . . . . . . . . Using Autostart . . . . . . . . . . . . . . . . . . . . . . Using START DBE . . . . . . . . . . . . . . . . . . . . . Starting a DBE Session in Single-User Mode . . . . . . . . . Overriding DBECon Parameters . . . . . . . . . . . . . .
PAGE 24
Using the WITH GRANT OPTION Clause and Authorization Groups Creating a Database Schema . . . . . . . . . . . . . . . . . . . . Loading Tables . . . . . . . . . . . . . . . . . . . . . . . . . . Loading from an External File . . . . . . . . . . . . . . . . . . Loading from an Internal File . . . . . . . . . . . . . . . . . . Loading Tables with Constraints on Them . . . . . . . . . . . . . Loading Tables with Rules Built on Them . . . . . . . . . . . . . Using Command Files for Loading . . . . . . . . . . .
PAGE 25
Purging Log Files with PURGELOG . . . . . . . . . . Moving Log Files with MOVELOG . . . . . . . . . . . Starting a New Log . . . . . . . . . . . . . . . . . . . Monitoring the Log with SQLMON . . . . . . . . . . . . Setting up a Wrapper DBEnvironment . . . . . . . . . . . Selecting Valid Log Files with SHOWLOG . . . . . . . . Single Logs . . . . . . . . . . . . . . . . . . . . . Dual Logs . . . . . . . . . . . . . . . . . . . . .
PAGE 26
Maintaining Applications . . . . . . . . . . . . . . . . Invalidation and Revalidation of Sections . . . . . . . . . Information in the System Catalog on Validity of Sections Monitoring File Space for Modules and Sections . . . . . Causes for Invalidation of Sections . . . . . . . . . . Avoiding the Need for Re-Preprocessing . . . . . . . . Determining Available Space for Sections . . . . . . . Determining Number of Sections in the DBEnvironment . Module Related Authorities . . . . . . . . . . . . . .
PAGE 27
System.Paramdefault System.Parameter . . System.Partition . . System.Plan . . . . System.Procauth . . System.Procedure . . System.ProcedureDef System.ProcResult . System.Rule . . . . System.RuleColumn . System.RuleDef . . . System.Section . . . System.Setoptinfo . . System.Spaceauth . . System.Spacedefault . System.Specauth . . System.Tabauth . . System.Table . . . . System.TempSpace . System.TPIndex . . System.Transaction . System.User . . . . System.ViewDef . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 28
RESCUELOG . . . . . . . RESTORE . . . . . . . . . RESTORELOG . . . . . . RESTORE PARTIAL . . . . SET . . . . . . . . . . . . SETDBEMAINT . . . . . . SETUPRECOVERY . . . . SETUPRECOVERY PARTIAL SHOWACCESS . . . . . . . SHOWDBE . . . . . . . . SHOWDBE-ALL . . . . . . SHOWDBE-EXIT . . . . . SHOWDBE-HELP . . . . . SHOWDBE-LANG . . . . . SHOWDBE-MAINT . . . . SHOWDBE-QUIT . . . . . SHOWDBE-STARTPARMS . SHOWLOG . . . . . . . . SHOWSET . . . . . . . . STORE . . . . . . . . . . STOREINFO . . . . . . . . STORELOG .
PAGE 29
GENERATE TEMPSPACES . GENERATE VIEWAUTH . . GENERATE VIEWS . . . . HELP . . . . . . . . . . . RELEASE . . . . . . . . . SET ECHO ALL OFF . . . SET ECHO ALL ON . . . . SET EDITOR . . . . . . . SET EXIT ON DBERR OFF SET EXIT ON DBERR ON . SET SCHEMA . . . . . . . STARTDBE . . . . . . . . : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 30
Figures 1-1. 1-2. 1-3. 1-4. 2-1. 2-2. 2-3. 2-4. 2-5. 2-6. 2-7. 2-8. 2-9. 2-10. 3-1. 3-2. 3-3. 3-4. 3-5. 4-1. 4-2. 4-3. 5-1. 5-2. 6-1. 6-2. 6-3. Tables, DBEFiles, and DBEFileSets . . . . . . . . . . . . Databases and DBEFileSets . . . . . . . . . . . . . . . Elements of an ALLBASE/SQL DBEnvironment . . . . . . The Relationship between Files and Bu ers . . . . . . . . Identifying Data Categories . . . . . . . . . . . . . . . Entities, Attributes, and Keys . . . . . . . . . . . . . .
PAGE 31
Tables 1-1. 1-2. 1-3. 1-4. 1-5. 1-6. 1-7. 2-1. 2-2. 3-1. 3-2. 3-3. 3-4. 3-5. 4-1. 5-1. 6-1. 6-2. 7-1. 8-1. 8-2. 8-3. 8-4. 8-5. 8-6. 8-7. 8-8. 8-9. 8-10. 8-11. 8-12. 8-13. 8-14. 8-15. 8-16. 8-17. 8-18. 8-19. 8-20. 8-21. 8-22. 8-23. 8-24. JCWs Set by SQLUtil . . . . . . . . . . . . . . . . . . . SQLGEN General Conventions . . . . . . . . . . . . . . . SQLGEN Name Entry Conventions . . . . . . . . . . . . . JCWs Set by SQLGEN . . . . . . . . . . . . . . . . . . JCWs Set by SQLMigrate . . . . . . . . . . . .
PAGE 32
8-25. 8-26. 8-27. 8-28. 8-29. 8-30. 8-31. 8-32. 8-33. 8-34. 8-35. 8-36. 8-37. 8-38. 8-39. 8-40. 8-41. 8-42. A-1. A-2. A-3. B-1. E-1. E-2. System.Procedure . . . . . . . . . . . . . . . . . System.ProcedureDef . . . . . . . . . . . . . . . System.ProcResult . . . . . . . . . . . . . . . . System.Rule . . . . . . . . . . . . . . . . . . . System.RuleColumn . . . . . . . . . . . . . . . . System.RuleDef . . . . . . . . . . . . . . . . . . System.Section . . . . . . . . . . . . . . . . . . System.Setoptinfo .
PAGE 33
1 DBA Tasks and Tools This guide shows how to perform database administration tasks for your ALLBASE/SQL relational database management system. The present chapter introduces the following topics: Tasks for the DBA Tools for the DBA System administration for ALLBASE/SQL Chapters 1 through 3 describe the concepts behind ALLBASE/SQL database administration tasks. Subsequent chapters describe DBA concepts and tasks in detail.
PAGE 34
Tasks for the DBA The database administrator is responsible for the overall operation of DBEnvironments. This includes: Creating logical and physical objects. Starting and stopping DBE sessions. Establishing multiple DBEnvironment connections. Managing ALLBASE/SQL logs. Maintaining bu ers for data and log pages. Managing transactions and locks. Setting parameters in the DBECon le. Monitoring the system catalog. Managing nonstop production systems. Backing up and restoring DBEnvironments.
PAGE 35
Figure 1-1. Tables, DBEFiles, and DBEFileSets A DBEFileSet is a collection of DBEFiles containing data for one or more tables. The tables and indexes associated with a DBEFileSet do not have to be for the same database. Figure 1-2 illustrates that while a DBEFileSet can contain data for all the tables in a database, a DBEFileSet can also contain data for some of the tables in a database, or for tables in more than one database.
PAGE 36
Figure 1-2. Databases and DBEFileSets Thus, DBEFileSets o er a way to allocate data storage independently of how users think about the data. During physical design and database creation, the DBA determines space requirements for the tables and indexes and creates DBEFiles and DBEFileSets to accommodate them. A DBEnvironment, illustrated in Figure 1-3, houses the DBEFiles for one or more ALLBASE/SQL databases.
PAGE 37
Figure 1-3. Elements of an ALLBASE/SQL DBEnvironment The DBEnvironment also contains the following entities, which contain information for all databases in the DBEnvironment: A DBECon le. This le contains information about the DBEnvironment's con guration, such as the size of various bu ers and other startup parameters. The name of the DBECon le is the same as the name of the DBEnvironment. Log les. A log le contains a record of DBEnvironment changes.
PAGE 38
Starting and Stopping DBE Sessions The DBA controls access to each DBEnvironment by turning the AUTOSTART ag ON or OFF and by issuing START DBE and STOP DBE commands. Use the SQLUtil ALTDBE command (described later in this chapter) to turn AUTOSTART mode ON or OFF. When users have the proper authorization, they access a database by rst connecting to the DBEnvironment in which the database resides.
PAGE 39
Managing ALLBASE/SQL Logs For each DBEnvironment you create, ALLBASE/SQL automatically starts a log containing log records which re ect the DBEnvironment's activities. ALLBASE/SQL uses writeahead logging. This means that actual changes are not made to the DBEnvironment until the changes are rst written to the log les as log records. Log records enable an ALLBASE/SQL DBEnvironment to roll back transactions and to recover in the event of a soft crash or a media failure.
PAGE 40
Rollback recovery is an automatic feature of both nonarchive and archive log modes. Rollback recovery has two purposes: to let users roll back the e ects of a transaction with the ROLLBACK WORK statement to let ALLBASE/SQL automatically roll back the DBEnvironment to a consistent state after a soft crash, and whenever the START DBE statement is executed. A soft crash is a program abort or a system failure that does not damage the storage media.
PAGE 41
the log bu er is full, so changes to the DBEnvironment must be written to disk to free log bu er space. when a checkpoint is taken by means of a user's CHECKPOINT statement or by ALLBASE/SQL internally. The checkpoint writes a system checkpoint record to the log, and it ushes the log bu er as well as the data bu er. ALLBASE/SQL ushes pages from the data bu er to DBEFiles when one of the following occurs: the data bu er is full, so individual changed pages are written to disk to free data bu er space.
PAGE 42
Managing Transactions and Locks Within a DBEnvironment, ALLBASE/SQL manipulates data in units of recoverable work known as transactions. A transaction is one or more SQL statements that together perform a unit of work on one or more databases in a DBEnvironment. A transaction begins with an SQL statement and ends with either a COMMIT WORK statement or a ROLLBACK WORK statement. All work done within a transaction can be made permanent (committed) or undone (rolled back).
PAGE 43
The size of rows and columns in tables. The cluster count of indexes. Which transactions are waiting for locks to be released. The names of users on the system and their session ids. View and table de nitions. The \Maintenance" chapter shows how to perform many useful maintenance tasks using system catalog information. The \System Catalog" chapter describes each view and pseudotable in the system catalog with examples of its contents.
PAGE 44
Backing Up and Restoring DBEnvironments The DBA is also responsible for routine backup and, when necessary, the restoring of DBEnvironments following a system failure. This means: Choosing either archive or nonarchive logging. Implementing a backup strategy. Backing up DBEnvironments and log les regularly. Adding and dropping log les as needed. Restoring the system from backups as needed. The subject is discussed fully in the chapter \Backup and Recovery.
PAGE 45
Tools for the DBA In addition to the general set of SQL statements, the DBA uses several utility programs in creating and maintaining DBEnvironments. These are: ISQL SQLUtil SQLGEN SQLMigrate SQLMON SQLVer SQLAudit The use of each toolset is described in the following paragraphs. Complete command syntax for ISQL, SQLUtil, SQLGEN, SQLMigrate, and SQLAudit is in the appendices. In addition, there is a discussion of SQLINSTL. SQLINSTL is a script used when moving to a new version of ALLBASE/SQL.
PAGE 46
Add, purge, store, and restore log les. Perform rollforward recovery. Starting SQLUtil There are two ways to run the SQLUtil program: directly from MPE/iX, or within ISQL. For the rst method, type the following command: : RUN SQLUTIL.PUB.SYS To execute SQLUtil within ISQL, type: isql=> sqlutil; No matter which method you use, you will see the SQLUtil banner and prompt (>>). The SQLUtil commands are described in the appendix, \SQLUtil.
PAGE 47
Table 1-1. JCWs Set by SQLUtil JCW Name Contents Range UTILERR number of SQL errors encountered 0 - 32767 UTILWARN number of SQL warnings encountered 0 - 32767 JCW FATAL if SQL error encountered, 0 if SQL error not encountered. The system JCW is set only if the SET EXIT ON DBERR command is ON. FATAL or 0 Using SQLGEN SQLGEN is a utility that generates the commands used to recreate all or part of an existing ALLBASE/SQL DBEnvironment.
PAGE 48
system catalogs are not being altered during SQLGEN execution. When you nish entering commands, use the EXIT command to return either to MPE/iX or to ISQL. When you run SQLGEN directly from MPE/iX, you can specify the editor name as an INFO string. When you run SQLGEN from ISQL, the current editor name is passed to and displayed by SQLGEN. Refer to the SET EDITOR command for more information. SQLGEN Commands SQLGEN commands can be divided into two categories, generate commands and auxiliary commands.
PAGE 49
rst character of the command. Only commands allowed in break can be executed. Table 1-2 summarizes SQLGEN's general conventions. Table 1-2. SQLGEN General Conventions Convention Explanation No Semicolons Command terminating semicolons are not needed, but allowed. : to enter system commands Use any command allowed in break. Example EXIT or EXIT; >> :LISTF 4 Return 5 : to escape to MPE Use any command allowed in break Type resume to return to SQLGEN.
PAGE 50
Table 1-3. SQLGEN Name Entry Conventions Convention Explanation Example all objects starting with the character P all two-letter names starting with P Pattern Matching Using % and _ % replaces 0 or more characters. _ No Quotes Use in most cases. Name is upshifted. Pattern matching allowed. PurchDB P% Single Quotes Use around lower case names. Names are not upshifted. Pattern matching allowed. 'tab' tab 'T%s' all names starting with T and Use when the name itself contains a % or_.
PAGE 51
at run-time during production hours can also cause concurrency problems due to write locks placed on the system catalog. You must use SQLINSTL whenever a new version of ALLBASE/SQL is installed; however, SQLINSTL does not need to be executed separately if SQLMigrate is being executed to migrate between major releases. Refer to the section, \Using SQLINSTL," later in this chapter for more information. Note ALLBASE/SQL no longer supports pseudo-mapped les.
PAGE 52
For backward migration, since previous releases do not support partitions, the only supported option for a DBEnvironment with audit logging in use is to place all the tables in the default partition with the only audit logging element speci ed being DATA. Then the DBEnvironment can be migrated backward unchanged. If the audit elements include something other than DATA, one of the following may happen: The migration is not allowed to proceed. The elements are reset to be only DATA.
PAGE 53
6. For each DBEnvironment that will be migrated, issue the PREVIEW command to check for errors that might occur during migration. The syntax for PREVIEW of a forward migration is: 3 2 SQLMIGRATE=> PREVIEW 'DBEnvironmentName' FORWARD TO 'Version' ; Note that the version parameter is optional. If this parameter is omitted, the most recent version supported by SQLMigrate will be used as the default.
PAGE 54
b. If you do not have TurboSTORE, issue the following SQL statements in single user mode in ISQL: isql=> BEGIN ARCHIVE; isql=> COMMIT ARCHIVE; Exit from ISQL and run SQLUtil, then issue the STORE command. 9. Run SQLUtil (if you are not already in SQLUtil from the previous step) and issue the SHOWDBE command to check the parameters of the new version of the DBEnvironment. Use the ALTDBE command if changes are necessary. Use the SHOWLOG command to display current log information. 10.
PAGE 55
If you encounter errors during the PREVIEW step that you do not understand, contact your HP Service Representative or Response Center. d. Run SQLMigrate and issue the MIGRATE command to modify your DBEnvironment to make it compatible with the old release of ALLBASE/SQL. The MIGRATE BACKWARD syntax is: SQLMIGRATE=> MIGRATE 'DBEnvironmentName' BACKWARD TO 'Version'; If you encounter errors during the MIGRATE step that you do not understand, contact your HP Service Representative or Response Center. 3.
PAGE 56
Table 1-5. JCWs Set by SQLMigrate JCW Name Contents Range MIGERR number of SQL errors encountered 0 - 32767 MIGWARN number of SQL warnings encountered 0 - 32767 JCW FATAL if SQL error encountered, 0 if SQL error not encountered. The system JCW is set only if the SET EXIT ON DBERR command is ON. FATAL or 0 Using SQLINSTL SQLINSTL is a script that you use instead of SQLMigrate when migrating between releases of versions of ALLBASE/SQL (such as G1.14 to G1.15) or minor releases (such as G.0 to G.
PAGE 57
To run SQLMON, log on as system manager, as the database administrator, or a user that was granted MONITOR authority, and issue the following command: : SQLMON Using SQLVer SQLVer allows you to check the version strings of the ALLBASE/SQL les. The syntax of SQLVer is as follows: 2 3 le The le parameter speci es the fully quali ed name of the ALLBASE/SQL le whose version you want to check.
PAGE 58
psqlfor.pub.sys (created THU, OCT 17, 1996): HP36216-02A.G1.18 FORTRAN Preprocessor/3000 ALLBASE/SQL psqlpas.pub.sys (created THU, OCT 17, 1996): HP36216-02A.G1.18 PASCAL Preprocessor/3000 ALLBASE/SQL sqlct000.pub.sys (created THU, OCT 17, 1996): sqlgen.pub.sys (created THU, OCT 17, 1996): HP36216-02A.G1.18 SQL Command Generator/3000 ALLBASE/SQL sqlmonp.pub.sys (created THU, OCT 17, 1996): HP36216-02A.G1.18 SQLMonitor/3000 ALLBASE/SQL sqlmig.pub.sys (created THU, OCT 17, 1996): HP36216-02A.G1.
PAGE 59
-----------------------------------------------------------------------SUMMARY: ------Current ALLBASE/SQL version installed: A.G1.18 ALLBASE/SQL has 0 file(s) missing. ALLBASE/NET has 0 file(s) missing. Number of version incompatibilities found: 0 Using SQLAudit SQLAudit is an ALLBASE/SQL utility program that can be used in conjunction with audit DBEnvironments to view the changes that have been made to the DBEnvironment.
PAGE 60
SET EXIT ON DBERR SET RECOVERFILE SHOW AUDITPOINT UNLOCK AUDITPOINT : Sets SQLAudit to exit or continue when a database error is encountered. De nes the recovery le used by the AUDIT command. Displays audit point information contained in a le. Removes a locked audit point from the log. Escapes temporarily to the operating system for the execution of operating system commands. Refer to the appendix \SQLAudit" for the complete SQLAudit command reference.
PAGE 61
Table 1-7. SQLAudit General Conventions Convention Explanation Example No Semicolons Command terminating semicolons are not needed, but allowed. EXIT or EXIT; : to enter system commands Use any command allowed in MPE/iX. SQLAudit >> :listf 4RETURN5 : to escape to MPE/iX Use any command allowed in MPE/iX. SQLAudit >> : 4RETURN5 : RESUME 4RETURN5 SQLAudit >> // OR / to return to the SQLAudit prompt Single or double slashes end a command.
PAGE 62
Suppose, for example, that at the time the beginning audit point is de ned, the current list of partitions and their committed transactions exists as follows: Partition 1 2 6 Transaction Identification Information Transaction # 10 Transaction # 21 Transaction # 16 Transaction number 10 was the last transaction that changed data in partition number 1. Similarly, transaction numbers 21 and 16 were the last transactions to change data in partition numbers 2 and 6, respectively.
PAGE 63
Example of Getting Audit Points The following example illustrates how GET AUDITPOINT de nes and displays an audit point: SQLAudit >> GET AUDITPOINT Audit Point File >> STARTPT Lock Log for Current Audit Point (no/yes) >> NO Display Current Audit Point Information (no/yes) >> YES Creator Name: dbauser Lockpoint: Log Sequence No (5) Page No (327) No.
PAGE 64
Since the bank does not want to lose any information before they audit it, they also lock the beginning audit point to make sure the transactions are not overwritten.
PAGE 65
SQLAudit Result Files The results of an audit are put into a le in a user readable format. The following example shows what the contents of this le could look like for an audit of partition number 2: ***** SQLAUDIT: GENERATING RESULTS **** Creator: dbauser Creation Time: 1993-05-11 BEGIN INSERT (2) USER1.TABLE1 (123, 'test data', UPDATE (2) USER1.TABLE1 (123, 'test data', COMMIT User: USER1 Label: TRANS1 BEGIN DELETE (2) USER1.
PAGE 66
System Administration for ALLBASE/SQL The DBA must cooperate with the system administrator on several crucial matters. These include: Shared Memory Usage Native Language Support Network Administration Shared Memory Usage Since ALLBASE/SQL may have to coexist on a system with other applications, the amount of available shared memory for log bu ers, data bu ers, and runtime control blocks must be negotiated with the system administrator.
PAGE 67
0 1 2 3 4 5 6 7 8 NATIVE-3000 AMERICAN C-FRENCH DANISH DUTCH ENGLISH FINNISH FRENCH GERMAN 9 10 11 12 13 14 41 51 ITALIAN NORWEGIAN PORTUGUESE SPANISH SWEDISH ICELANDIC KATAKANA ARABIC 52 61 71 81 201 211 221 231 ARABICW GREEK HEBREW TURKISH CHINESE-S CHINESE-T JAPANESE KOREAN Resetting NLUSERLANG while you are connected to a DBEnvironment has no e ect on the current DBE session.
PAGE 68
2 Logical Design An ALLBASE/SQL database is de ned both logically and physically. Logically, an ALLBASE/SQL database is one or more tables or views with the same owner. This chapter will give guidelines on how to design the logical structure of a relational database and to use ALLBASE/SQL table, view, and index de nition features to meet the needs of users and applications.
PAGE 69
Figure 2-1. Identifying Data Categories You can use similar documents as a starting point for designing the tables in your own databases. Data from the purchase order can be arranged in categories. Once the data has been identi ed, it must be broken up into tables. This is done by identifying entities, attributes, and keys within the data.
PAGE 70
For example, on the purchase order for Integrated Peripherals, the database designer might identify the following general groups of information as entities: Vendor information Order information Order item information The Vendor Information entity has several attributes, including vendor number, vendor name, vendor address, sales contact, and phone number.
PAGE 71
Note that the key for order item information is composed of two items. This is because neither the Item Number nor the Order Number is signi cant by itself. Remember that a primary key must be unique. Item number alone cannot be the primary key because every order can have an item #1. The order number alone cannot be the primary key either because one order can have several items, forcing the order number to be repeated (not unique).
PAGE 72
Figure 2-3. First Normal Form: Removing Repeating Groups Second Normal Form In second normal form, shown in Figure 2-4, all attributes are functionally dependent on the primary key.
PAGE 73
Figure 2-4. Second Normal Form: Establishing Dependency Attributes are functionally dependent when their values depend directly upon the value of the primary key. The primary key in the Order Item information is the order and item number combination. Each such combination represents a unique row. Since the vendor part number and the order quantity relate to a particular order and item number, they are functionally dependent on the primary key.
PAGE 74
Figure 2-5. Third Normal Form: Removing Transitive Dependencies Third normal form relieves update problems. For example, in second normal form, when an item's price changes, all orders containing that item would have to be altered. In third normal form, only the rows for that item in the Supply Price table need to be changed. Normalized data provides a starting point for table de nition. Note that the data in Figure 2-3, Figure 2-4, and Figure 2-5 is in tabular form.
PAGE 75
Defining Tables To design tables you need to know how the applications use data in SELECT, DELETE, INSERT, and UPDATE operations. Data that is deleted, inserted, or updated at the same time should be put in the same table. Use these criteria to start grouping your data into tables. To determine the composition of your tables, keep the following guidelines in mind: The maximum number of tables you can de ne in a DBEnvironment is 231 -1. The maximum number of columns in a table is 1023.
PAGE 76
Tables can be joined as Cartesian products where each row of one table is joined with every row in another table. However, in order for tables to be meaningfully joined, they must share a common column. If two tables do not share a common column, then a third table containing common columns for both tables must be introduced into the join, as shown in Figure 2-6. Figure 2-6.
PAGE 77
Columns are added to some of the tables to t the user's needs. A VendorRemarks column is added to Vendors to keep comments for that vendor. A ReceivedQty column is added to the OrderItems table to denote when a shipment arrives. The resulting six tables are shown in Table 2-1. Table 2-1.
PAGE 78
Some guidelines for data types are: Match the data type to the data, for example: Columns used for quantity or count should be de ned as INTEGER or SMALLINT. Columns containing real numbers or engineering data should be de ned as REAL or FLOAT. Columns used for money should be de ned as DECIMAL so there is no loss of precision when rounding. Columns containing alphanumeric characters should be de ned as CHAR or VARCHAR.
PAGE 79
Defining Column Size You should always de ne your columns to be large enough to hold the largest piece of information you expect it will ever hold. This helps to avoid restructuring of tables at a later time. Column size a ects both physical design and logging. Rows are stored in 4096-byte DBEFile pages. After the space for a page header is used, 3996 bytes are left for data storage. During physical design row length is used in calculating the number of DBEFile pages needed to store data for a table.
PAGE 80
In addition, a two-byte tuple header is stored on disk for each tuple which has a NULL value if the inserted tuple's header does not match the rst shared header on the DBEFile page. The data types and sizes of the columns for the OrderItems and Vendors tables are shown in Table 2-2. Table 2-2.
PAGE 81
Data independence is usually a concern in programmatic environments. An application that accesses several tables would have to be modi ed each time the tables were altered. A view de ned to look like the old tables would keep applications independent of database changes. Refer to the appropriate ALLBASE/SQL Application Programming Guide for more information on how views a ect and are manipulated by application programs. View de nition is not restricted to base tables.
PAGE 82
Designing Indexes An index is de ned on one or more columns in a table to facilitate rapid retrieval of data. ALLBASE/SQL decides whether to use an index in the process of creating an optimal access path for the data during query optimization. By default, you cannot specify the use of an index in an SQL statement; the optimizer will decide to use an index if it will improve performance during query processing.
PAGE 83
This page in turn points to the second leaf page from the left, since Glen comes after Dave and before Larry . Finally, the leaf page points to a speci c data page where the desired row is found. Note that ALLBASE/SQL B-tree indexes are doubly linked, in that the leaf pages point to other leaf pages, so that the next higher or lower value in key order can be quickly located without \backing out" to a higher level in the tree.
PAGE 84
If you are considering a compound key, you should also keep the following in mind: A compound key can have up to 16 columns. The length of a compound key must be less than or equal to 1024 bytes. Use the following formula to determine whether or not a proposed compound key is acceptable: 2N C + K L + 18 <= 1024 Where NC is the number of columns, and KL is the sum of the column lengths in the key. A single column index may not exceed 1010 bytes.
PAGE 85
The unique index will not permit duplicate values for the key columns speci ed. The clustering index attempts to place rows with similar key values physically close to each other on disk. Defining Unique Indexes If you specify the unique option when creating an index, the columns named in the index key are kept unique. Unique indexes prevent duplicate data in the columns used as keys of the index.
PAGE 86
Clustering of data is maintained when there is a relatively large volume of DELETE operations followed by a similar volume of INSERT operations on the table. Clustering of data is not maintained when there is a larger volume of INSERT operations than DELETE operations. Designing Hash Structures Like an index, a hash structure speci es up to 16 key columns on a table to facilitate rapid access to data.
PAGE 87
Choosing Hash Keys In choosing a hash key, one important consideration is your query design. There must be an EQUAL factor for each key column in the predicates of queries that will use the hash structure. Another important issue is the distribution of key values. The best key results in a set of hash values that are evenly distributed among the primary pages available. The worst key results in hash values that cluster tightly in a narrow range of primary pages, leaving others empty.
PAGE 88
Designing Integrity Constraints You can enforce integrity in particular tables or in the relationships among tables in your design by creating integrity constraints on speci c columns. Unique, referential, and check integrity constraints can be included as part of the CREATE TABLE or ALTER TABLE statements. A check constraint can be included as part of a CREATE VIEW statement. A unique constraint lets you eliminate duplicate key values.
PAGE 89
Defining Security Levels In ALLBASE/SQL, you create security controls by granting authorities to speci c users or groups. An authority is a privilege that enables a user to access the DBEnvironment, create database objects, use SQL statements, preprocess and run application programs containing SQL statements, or maintain the DBEnvironment.
PAGE 90
NNNNNNNNNNN DBA | ----------------------------------------------------------------| | | | | | | | SECTION- DBA CONNECT TABLERESOURCE..... OWNER MONITOR INSTALL SPACE | SPACE | etc. -----------------| | | EXECUTE RUN ALTER DELETE INDEX INSERT SELECT UPDATE REFERENCES NNNNNNNNNNNNNNNNN .......implicit grant -------explicit grant NNNNNNNNNNNNNNNNN OWNER authority can be transferred Figure 2-8.
PAGE 91
Owner Authority The following objects can have owners: Tables Views Modules Procedures Authorization groups The owner of an object can drop that object. The owner of a table, view, module, or procedure can grant authorities for that table, view, module, or procedure to other users. The owner of a module has RUN authority for that module plus the capability to re-preprocess the module. The owner of an authorization group can add members to the group, remove members from the group, or drop the group.
PAGE 92
SELECT UPDATE REFERENCES Table and view authorities are described fully in Chapter 5. RUN Authority RUN authority determines who has access to speci c preprocessed application modules stored in the DBEnvironment. RUN authority is further described in the \Maintenance" chapter. EXECUTE Authority EXECUTE authority determines who has access to speci c procedures stored in the DBEnvironment. EXECUTE authority is further described in the \Maintenance" chapter.
PAGE 93
PUBLIC SEMIPERM STOREDSECT SYSTEM TEMP In addition, the DBECreator cannot be added to an authorization group. Each member of the authorization group has the authorities granted to the group. The owner of the group, if not explicitly a member of the group, does not have any of the authorities that have been granted to the group. After de ning groups, you can then control authorities on a group basis instead of an individual user basis.
PAGE 94
Figure 2-9. Authorization Group Chain Defining Classes A class is a special category of owner that is neither a conventional DBEUserID nor a group. You may wish to assign ownership of objects to a class when you do not want any individual or group to have automatic access to them. With class ownership, the DBA controls all authorities, since objects that belong to a class can be created and maintained only by the DBA. Strictly speaking, a class is an owner that does not have CONNECT authority.
PAGE 95
Guidelines for Creating Classes In designing a security scheme that includes classes, follow these guidelines: Make sure that a new class name is di erent from any DBEUserID. Make sure the class name is not the same as any group name de ned in the DBEnvironment. Choose a class name that re ects the concept behind the class, e.g., PurchDB for Purchasing Department Database. Do not assign CONNECT authority to a class.
PAGE 96
Figure 2-10. DBEnvironment used by Integrated Peripherals, Inc. The PurchDB database has been designed in the present chapter; the other databases are included to illustrate the use of multiple databases in a single DBEnvironment. All three databases are placed in a single DBEnvironment because the data, although used separately in most applications, is sometimes used together in reports and global applications.
PAGE 97
3 Physical Design Physically, an ALLBASE/SQL DBEnvironment is a collection of les for the storage of databases. The physical design process helps you compute the storage requirements for the tables, indexes, and other objects that emerge at the end of the logical design process.
PAGE 98
Understanding DBEFile Characteristics DBEFiles are used to store table and index data. They are composed of 4096-byte pages. DBEFiles can be from 2 to 524,287 pages. The number of pages in an ALLBASE/SQL le is determined when it is created. In the case of expandable DBEFiles, the maximum size and the size of an increment are determined when the DBEFile is created. All DBEFiles must be associated with a DBEFileSet before they can be used to store data.
PAGE 99
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 100
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 101
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 102
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 103
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 104
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 105
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 106
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 107
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 108
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 109
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 110
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 111
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 112
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 113
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 114
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 115
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 116
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 117
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 118
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 119
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 120
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 121
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 122
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 123
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 124
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 125
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 126
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 127
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 128
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 129
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 130
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 131
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 132
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 133
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 134
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 135
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 136
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 137
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 138
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 139
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 140
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 141
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 142
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 143
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 144
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 145
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 146
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 147
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 148
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 149
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 150
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 151
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 152
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 153
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 154
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 155
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 156
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 157
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 158
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 159
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 160
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 161
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 162
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 163
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 164
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 165
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 166
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 167
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 168
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 169
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 170
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 171
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 172
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 173
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 174
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 175
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 176
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 177
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 178
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 179
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 180
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 181
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 182
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 183
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 184
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 185
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 186
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 187
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 188
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 189
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 190
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 191
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 192
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 193
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 194
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 195
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 196
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 197
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 198
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 199
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 200
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 201
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 202
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 203
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 204
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 205
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 206
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 207
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 208
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 209
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 210
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 211
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 212
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 213
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 214
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 215
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 216
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 217
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 218
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 219
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 220
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 221
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 222
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 223
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 224
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 225
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 226
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 227
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 228
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 229
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 230
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 231
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 232
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 233
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 234
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 235
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 236
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 237
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 238
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 239
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 240
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 241
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 242
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 243
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 244
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 245
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 246
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 247
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 248
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 249
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 250
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 251
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 252
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 253
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 254
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 255
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 256
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 257
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 258
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 259
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 260
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 261
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 262
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 263
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 264
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 265
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 266
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 267
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 268
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 269
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 270
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 271
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 272
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 273
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 274
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 275
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 276
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 277
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 278
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 279
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 280
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 281
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 282
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 283
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 284
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 285
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 286
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 287
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 288
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 289
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 290
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 291
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 292
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 293
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 294
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 295
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 296
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 297
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 298
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 299
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 300
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 301
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 302
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 303
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 304
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 305
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 306
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 307
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 308
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 309
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 310
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 311
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 312
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 313
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 314
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 315
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 316
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 317
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 318
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 319
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 320
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 321
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 322
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 323
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 324
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 325
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 326
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 327
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 328
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 329
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 330
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 331
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 332
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 333
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 334
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 335
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 336
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 337
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 338
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 339
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 340
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 341
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 342
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 343
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 344
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 345
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 346
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 347
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 348
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 349
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 350
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 351
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 352
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 353
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 354
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 355
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 356
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 357
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 358
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 359
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 360
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 361
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 362
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 363
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 364
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 365
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 366
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 367
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 368
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 369
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 370
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 371
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 372
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 373
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 374
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 375
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 376
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 377
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 378
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 379
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 380
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 381
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 382
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 383
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 384
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 385
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 386
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 387
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 388
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 389
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 390
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 391
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 392
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 393
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 394
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 395
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 396
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 397
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 398
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 399
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 400
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 401
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 402
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 403
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 404
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 405
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 406
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 407
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 408
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 409
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 410
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 411
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 412
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 413
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 414
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 415
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 416
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 417
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 418
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 419
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 420
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 421
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 422
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 423
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 424
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 425
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 426
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 427
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 428
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 429
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 430
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 431
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 432
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 433
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 434
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 435
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 436
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 437
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 438
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 439
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 440
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 441
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 442
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 443
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 444
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 445
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 446
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 447
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 448
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 449
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 450
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 451
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 452
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 453
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 454
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 455
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 456
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 457
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 458
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 459
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 460
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 461
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 462
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 463
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 464
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 465
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 466
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 467
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 468
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 469
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 470
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 471
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 472
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 473
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 474
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 475
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 476
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 477
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 478
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 479
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 480
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 481
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 482
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 483
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 484
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 485
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 486
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 487
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 488
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 489
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 490
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 491
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 492
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 493
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 494
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 495
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 496
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 497
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 498
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 499
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 500
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 501
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 502
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 503
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 504
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 505
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 506
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 507
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 508
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 509
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 510
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 511
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 512
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 513
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 514
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 515
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 516
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 517
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 518
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 519
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 520
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 521
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 522
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 523
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 524
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 525
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 526
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 527
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 528
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 529
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 530
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 531
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 532
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 533
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 534
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 535
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 536
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 537
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 538
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 539
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 540
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 541
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 542
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 543
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 544
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 545
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 546
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 547
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 548
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 549
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 550
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 551
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 552
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 553
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 554
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 555
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 556
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 557
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 558
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 559
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 560
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 561
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 562
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 563
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 564
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 565
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 566
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 567
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 568
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 569
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 570
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.
PAGE 571
Figure 3-2. Data Stored in DBEFiles within a DBEFileSet All the DBEFiles for a given table and its indexes must be contained in one DBEFileSet. Table and index data can span more than one DBEFile within a DBEFileSet. Figure 3-2 shows the relationship between DBEFileSets, DBEFiles, and data. Note that in the gure the tables and indexes are stored in one or more DBEFiles, but they are all contained within a single DBEFileSet.