{"title":"Entity identity, performance, and storage","authors":"Aspen Olmsted","doi":"10.23919/ICITST.2017.8356368","DOIUrl":null,"url":null,"abstract":"When a database designer needs to model an entity that exists in a domain that does not have a global name authority, the designer must resort to using surrogate identifiers. Traditionally, these entities were referred to as Weak-Entities in Entity-Relationship models. There are many choices available to a database modeler, but each choice comes with sacrifices. This paper documents an experiment that evaluates several of these choices and hypothesizes the best solution from both a performance and a storage perspective. We then apply the suggested best algorithm to a production system and discover tremendous savings in disk space requirements and execution time on certain queries.","PeriodicalId":440665,"journal":{"name":"2017 12th International Conference for Internet Technology and Secured Transactions (ICITST)","volume":"1 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2017-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2017 12th International Conference for Internet Technology and Secured Transactions (ICITST)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.23919/ICITST.2017.8356368","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0
Abstract
When a database designer needs to model an entity that exists in a domain that does not have a global name authority, the designer must resort to using surrogate identifiers. Traditionally, these entities were referred to as Weak-Entities in Entity-Relationship models. There are many choices available to a database modeler, but each choice comes with sacrifices. This paper documents an experiment that evaluates several of these choices and hypothesizes the best solution from both a performance and a storage perspective. We then apply the suggested best algorithm to a production system and discover tremendous savings in disk space requirements and execution time on certain queries.