IBM Flex System x240 w

4. Clause 4: Scaling and Data Base Population Related Items4.1. Cardinality of TablesThe cardinality (e.g., the number of rows) of each table, as it existed at the start of the benchmark run, must bedisclosed.Table 4-2 portrays the TPC Benchmark TM C defined tables and the number of rows for each table as they were builtinitially.Table NameNumber of RowsWarehouse 128,160District 1,281,600Customer 3,844,800,000History 3,844,800,000Orders 3,844,800,000New Order 1,153,440,000Order Line 38,446,988,494Stock 12,816,000,000Item 100,000Table 4-2: Initial Cardinality of Tables4.2. Distribution of Tables and LogsThe distribution of tables and logs across all media must be explicitly depicted for the tested and priced systems.The log was configured using one Logical drive attached to one of the Fiber Channel disk controllers. The log wasconfigured as a RAID-10 disk array consisting of 12 450GB hot-swap SAS disks housed in one DS3512 drive enclosureand backed by a UPS.There are 112 Logical Disks (LD) for the utilized database tables. The LDs utilize 112 SSD drives attached via two 2portFiber Channel adapters. All of these drives are configured as JBOD and are partitioned identically and hold the staticdatabase tables. See Table 4-2,Table 4-3, and Table 4-44.3. Data Base Model ImplementedA statement must be provided that describes the data base model implemented by the DBMS used.The database manager used for this testing was DB2 9.7. DB2 is a relational DBMS. DB2 remote stored proceduresand embedded SQL statements were used. The DB2 stored procedures were invoked via SQL CALL statements. Boththe client application and stored procedures were written in embedded C code.