Performance and transaction cost variations of SQL/DS data base against selected parameters
Call Number: AIT Thesis no. CS-87-16 Material type:
TextSeries: Asian Institute of Technology. Thesis ; no. CS-87-16Publication details: Bangkok : Asian Institute of Technology, 1987Description: 122 pSubject(s): Online resources: Dissertation note: Thesis (M.Sc.) - Asian Institute of Technology, 1987 Summary: Buffer sizes, the storage and access methods used, cardinality of target tables, and some VM/SP system load indicators were shown to affect the performance of SQL/DS data base and their effects were quantified. Use of appropriate page buffer size and clustering index drastically reduced the CPU time and I/O requirements in retrieval transactions. Regular setting of appropriate page buffer size in order to conserve computer resources and the use the page hit ratio as the parameter to be monitored in order to determine proper page buffer size is recommended. In data base operations involving heavy retrieval transactions from DBSPACEs containing multiple tables, the use of clustering index is re commended to realize savings in computer resources even with the extra DASD space required for the indexes and the inconvenience in creating them. For certain storage/ access cases transaction cost models based on number of pages referenced and cardinality are shown to be in agreement with SQL/DS cost estimate. SQL/DS cost estimate is shown to be a linear function of cardinality in certain storage/access cases. Indexing has minimal effect in reducing transaction cost when the table accessed resides in single-table DBSPACE. Cost reduction is effected when tables have clustering index in multiple-table DBSPACE
| Cover image | Item type | Current library | Home library | Collection | Shelving location | Call number | Materials specified | Vol info | URL | Copy number | Status | Notes | Date due | Barcode | Item holds | Item hold queue priority | Course reserves | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
20-AIT Publication
|
Asian Institute of Technology Library AIT Publications | AIT Thesis no. CS-87-16 (Browse shelf(Opens below)) | 1 | Available | 30050003148243 | |||||||||||||
20-AIT Publication
|
Asian Institute of Technology Library AIT Publications | AIT Thesis no. CS-87-16 (Browse shelf(Opens below)) | 2 | Available | 30050002588035 | |||||||||||||
20-AIT Publication
|
Asian Institute of Technology Library Archives | AIT Thesis no. CS-87-16 (Browse shelf(Opens below)) | 3 | Available | 30050003148235 | |||||||||||||
40-Archives
|
Asian Institute of Technology Library Archives | AIT Thesis no. CS-87-16 (Browse shelf(Opens below)) | Available | 30050120373617 |
A thesis submitter in partial fulfillment of the requirements for the degree of Master of Science, School of Engineering and Technology
Thesis (M.Sc.) - Asian Institute of Technology, 1987
Buffer sizes, the storage and access methods used, cardinality of target tables, and some VM/SP system load indicators were shown to affect the performance of SQL/DS data base and their effects were quantified. Use of appropriate page buffer size and clustering index drastically reduced the CPU time and I/O requirements in retrieval transactions. Regular setting of appropriate page buffer size in order to conserve computer resources and the use the page hit ratio as the parameter to be monitored in order to determine proper page buffer size is recommended. In data base operations involving heavy retrieval transactions from DBSPACEs containing multiple tables, the use of clustering index is re commended to realize savings in computer resources even with the extra DASD space required for the indexes and the inconvenience in creating them. For certain storage/ access cases transaction cost models based on number of pages referenced and cardinality are shown to be in agreement with SQL/DS cost estimate. SQL/DS cost estimate is shown to be a linear function of cardinality in certain storage/access cases. Indexing has minimal effect in reducing transaction cost when the table accessed resides in single-table DBSPACE. Cost reduction is effected when tables have clustering index in multiple-table DBSPACE
There are no comments on this title.

AI Search