by Eric H
In this scholar journal it talked about physical and logical database. Most of those that deals with and manage databases usually focus on logical level of the database. that is a good thing, because these people wanted the logical data model to represent how the business truly views its data. Most data modeling tools have the functionality to instantiate a physical database in any of the common platforms(Chisholm, 2007). Often time when data modelers physically implemented the database, it thinks they have finished their part of the job, and its up to the business users to deal with the contents of the database. Reference data in a database is a data that has many synonyms(Chisholm, 2007). Reference data typically contain two attributes, a primary key and description and its referred to as code tables, lookup tables or domain values (Chisholm, 2007). There are usually just a few rows in these tables, and that the data it contains are usually unchanged or slow changing. And as more and more reference data tables gets added to a data model, its design will become more generalized, and in turn it will depends on the physical data even more, on specifying its implemented design.
This article that i have picked relates to the physical database design we have went over in class. and in this article i learned about the the connection between logical and physical data modeling, and the role reference data it plays in this. And the importance of reference data in the database. The reading for me is a bit difficult, i didn’t know understand a lot of the thing he author talked about, but from his writing reference seems to be a big part of a database, as he said it could take up about 20 percents of the whole database.
Chisholm, M. (2007). Data models are not database design. Information Management, 17(10), 45-45. Retrieved from http://search.proquest.com/docview/214681529?accountid=10357