• Journal of KIISE
• /
• v.43 no.2
• /
• pp.237-245
• /
• 2016

In this paper we introduce a novel database research area called science of databases (SoDB) and carry out a comprehensive analysis of its case studies. SoDB aims to better understand interesting phenomena observed across multiple database management systems (DBMSes). While mathematical and engineering work in the database field has been dominant, less attention has been given to scientific approaches through which DBMSes can be better understood. Scientific investigations can lead to better engineered designs through deeper understanding of query optimizers and transaction processing. The SoDB research has investigated several interesting phenomena observed across different DBMSes and provided several engineering implications based on our uncovered results. In this paper we introduce a novel scientific, empirical methodology and describe the research infrastructure to enable the methodology. We then review each of a selected group of phenomena studied and present an identified structural causal model associated with each phenomenon. We also conduct a comprehensive analysis on the case studies. Finally, we suggest future directions to expand the SoDB research.

• KIPS Transactions on Software and Data Engineering
• /
• v.9 no.4
• /
• pp.123-128
• /
• 2020

As the use of digital devices is becoming more commonplace, digital forensics techniques recover data to collect physical evidence during the investigation. Among them, the file forensics technique recovers deleted files, therefore, it can recover the database by recovering all files which compose the database itself. However, if the record is deleted from the database, the modified record contents will not be restored even if the file is recovered. For this reason, the database forensics technique is required to recover deleted records. Database forensics obtains metadata from database configuration files and recovers deleted records from data files. However, record recovery is difficult if database metadata such as block size cannot be obtained from the database. In this paper, we propose three methods for obtaining block size, which is database metadata. The first method uses the maximum size of free space in the block, and the second method uses the location where the block appears. The third method improves the second method to find the block size faster. The experimental results show that three methods can correctly find the block size of three DBMSes.