{"title":"Hierarchical storage management for relational databases","authors":"D. Isaac","doi":"10.1109/MASS.1993.289767","DOIUrl":null,"url":null,"abstract":"The author describes a prototype that integrates a database management system (DBMS) with a storage management system, allowing simple, cost-effective access to large volumes of data stored in a tape archive. The prototype study suggests that it is feasible from both technical and cost perspectives to store not just metadata, but large satellite images in a DBMS. The actual location of the data, whether in the DBMS, file system, or tape archive, is transparent to clients, allowing cost/performance optimization to be performed without affecting the interface to the client. Further, in common cases where database inserts can be bypassed, the performance of the prototype is equivalent to file system input/output (I/O).<<ETX>>","PeriodicalId":225568,"journal":{"name":"[1993] Proceedings Twelfth IEEE Symposium on Mass Storage systems","volume":"333 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1993-04-26","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"13","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"[1993] Proceedings Twelfth IEEE Symposium on Mass Storage systems","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/MASS.1993.289767","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 13
Abstract
The author describes a prototype that integrates a database management system (DBMS) with a storage management system, allowing simple, cost-effective access to large volumes of data stored in a tape archive. The prototype study suggests that it is feasible from both technical and cost perspectives to store not just metadata, but large satellite images in a DBMS. The actual location of the data, whether in the DBMS, file system, or tape archive, is transparent to clients, allowing cost/performance optimization to be performed without affecting the interface to the client. Further, in common cases where database inserts can be bypassed, the performance of the prototype is equivalent to file system input/output (I/O).<>