Database normalization

Database normalization is the process of structuring a relational database[clarification needed] in accordance with a series of so-called normal forms in order to reduce data redundancy and improve data integrity. It was first proposed by Edgar F. Codd as part of his relational model. Continue reading “Database normalization”

Database centric architecture

Database-centric Architecture or data-centric architecture has several distinct meanings, generally relating to software architectures in which databases play a crucial role. Often this description is meant to contrast the design to an alternative approach. For example, the characterization of an architecture as “database-centric” may mean any combination of the following: Continue reading “Database centric architecture”

Datafication

Datafication is a technological trend turning many aspects of our life into data[1] which is subsequently transferred into information realised as a new form of value.[2] Kenneth Cukier and Victor Mayer-Schöenberger introduced the term Datafication to the broader lexicon in 2013.[3] Up until this time, datafication had been associated with the analysis of representations of our lives captured through data, but not on the present scale. This change was primarily due to the impact of big data and the computational opportunities afforded to predictive analytics. Continue reading “Datafication”

Global serializability

In concurrency control of databasestransaction processing (transaction management), and other transactional distributed applications, global serializability (or modular serializability) is a property of a global schedule of transactions. Continue reading “Global serializability”

Database transaction

database transaction symbolizes a unit of work performed within a database management system (or similar system) against a database, and treated in a coherent and reliable way independent of other transactions. A transaction generally represents any change in a database. Transactions in a database environment have two main purposes: Continue reading “Database transaction”

Grid oriented storage

Grid-oriented Storage (GOS) was a term used for data storage by a university project during the era when the term grid computing was popular. Continue reading “Grid oriented storage”

Database server

database server is a server which uses a database application that provides database services to other computer programs or to computers, as defined by the client–server model.[citation needed][1][2] Database management systems (DBMSs) frequently provide database-server functionality, and some database management systems (such as MySQL) rely exclusively on the client–server model for database access (while others e.g. SQLite are meant for using as an embedded database). Continue reading “Database server”

H Store

H-Store is an experimental database management system (DBMS). It was designed for online transaction processing applications. H-Store was developed by a team at Brown University, Carnegie Mellon University, the Massachusetts Institute of Technology, and Yale University[1][2] in 2007 by researchers Michael Stonebraker, Sam Madden, Andy Pavlo and Daniel Abadi.[3][4][5] Continue reading “H Store”

Database schema

The database schema of a database is its structure described in a formal language supported by the database management system (DBMS). The term “schema” refers to the organization of data as a blueprint of how the database is constructed (divided into database tables in the case of relational databases). Continue reading “Database schema”

Government performance management

Government performance management (GPM) consists of a set of processes that help government organizations optimize their business performance. It provides a framework for organizing, automating, and analyzing business methodologies, metrics, processes and systems that drive business performance.[1] Continue reading “Government performance management”