Content deleted Content added
mNo edit summary |
m link mass surveillance |
||
(12 intermediate revisions by 9 users not shown) | |||
Line 2:
<!--... Attention: THIS IS AN OUTLINE
part of the set of
[[
Wikipedia outlines are
Line 10:
content navigation systems
[[Wikipedia:WikiProject
Further improvements
to this outline are on the way
Line 17:
The following is provided as an overview of and topical guide to databases:
'''[[Database]]''' – organized collection of data, today typically in digital form. The data are typically organized to model relevant aspects of reality (for example, the availability of rooms in hotels), in a way that supports processes requiring this information (for example, finding a hotel with vacancies).
== What type of things are databases? ==
Databases can be described as all of the following:
Line 47 ⟶ 46:
* [[Food composition database]] (FCDB) – provides detailed information on the nutritional composition of foods.
* [[Full-text database]] – database that contains the complete text of books, dissertations, journals, magazines, newspapers or other kinds of textual documents. Also called a "complete-text database".
* [[Government database]] – collects personal information for various reasons ([[mass surveillance]], Schengen Information System in the European Union, social security, statistics, etc.).
* [[Graph database]] – uses graph structures with nodes, edges, and properties to represent and store data.
* [[Knowledge base]] – special kind of database for knowledge management. A knowledge base provides a means for information to be collected, organised, shared, searched and utilised.
Line 81 ⟶ 80:
== History of databases ==
* [[Database#History|History of databases]] –
* [[Database management system#History|History of database management systems]] –:
Line 107 ⟶ 105:
* [[Log shipping]] – process of automating the backup of a database and transaction log files on a primary (production) database server, and then restoring them onto a standby server.
=== Database languages ===
[[Database#Database languages|Database languages]] –
* [[Data definition language]] –
Line 116 ⟶ 114:
** [[XQuery]] – a query and functional programming language that queries and transforms collections of structured and unstructured data.
=== Database security ===
[[Database security]] –
* [[Database activity monitoring]] (DAM) – database security technology for monitoring and analyzing database activity that operates independently of the database management system (DBMS) and does not rely on any form of native (DBMS-resident) auditing or native logs such as trace or transaction logs.
Line 123 ⟶ 121:
* [[Negative database]] – credit card terminology for a list of credit card owners who chargeback a lot.
=== Database design ===
[[Database design]] –
* [[Entity–relationship model]] (ER model) – abstract and conceptual representation of data.
Line 129 ⟶ 127:
* [[Database refactoring]] – simple change to a database schema that improves its design while retaining both its behavioral and informational semantics.
=== Database programming ===
* [[Database abstraction layer]] – application programming interface which unifies the communication between a computer application and databases such as SQL Server, DB2, MySQL, PostgreSQL, Oracle or SQLite.
* [[Object–relational mapping]] (ORM, O/RM, and O/R mapping) – in computer software is a programming technique for converting data between incompatible type systems in object-oriented programming languages.
=== Database management ===
* [[Database virtualization]] – it is the decoupling of the database layer, which lies between the storage and application layers within the application stack.
* [[Database tuning]] – describes a group of activities used to optimize and homogenize the performance of a database.
** [[Database caching]] – effective approach to achieve high scalability and performance.
*
* [[Database preservation]] – usually involves converting the information stored in a database, without losing the characteristics (Context, Content, Structure, Appearance and Behaviour) of the data, to a format which can be used in the long term, even if the technology and daily life knowledge changes.
* [[Database integrity]] – ensures that data entered into the database is accurate, valid, and consistent.
Line 143 ⟶ 141:
== Database management systems ==
[[Database management system]] –
* [[Database model]] –
* [[Database normalization]] – organizing tables based on their attributes so that the data presented can avoid having redundancy and dependency.
*
* [[Distributed database management system]] –
* [[Federated database system]] – type of meta-database management system (DBMS), which transparently maps multiple autonomous database systems into a single federated database.
Line 161 ⟶ 159:
* [[ACID]] – (''atomicity, consistency, isolation, durability'') is a set of properties that guarantee that database transactions are processed reliably.
* [[Create, read, update and delete]] (CRUD) – are the four basic functions of persistent storage.
* [[Null (SQL)|Null]] –
* [[Candidate key]] – minimal superkey for a relation.
* [[Foreign key]] – referential constraint between two tables.
* [[Primary key]] –
* [[Superkey]] – set of attributes of a relation variable for which it holds that in all relations assigned to that variable, there are no two distinct tuples (rows) that have the same values for the attributes in this set.
* [[Surrogate key]] – unique identifier in a database for either an ''entity'' in the modeled world or an ''object'' in the database.
Line 171 ⟶ 169:
=== Objects ===
* [[Relation (database)|Relation]] –
** [[Table (database)|Table]] –
** [[Column (database)|Column]] –
** [[Row (database)|Row]] –
* [[View (database)|View]] –
* [[Database transaction]] –
* [[Transaction log]] – history of actions executed by a database management system to guarantee ACID properties over crashes or hardware failures. Also called "transaction journal", "database log" or "binary log".
* [[Database trigger]] – procedural code that is automatically executed in response to certain events on a particular table or view in a database.
* [[Index (database)|Index]] –
* [[Stored procedure]] – subroutine available to applications that access a relational database system.
* [[Cursor (databases)|Cursor]] –
* [[Partition (database)|Partition]] –
=== Components ===
Line 188 ⟶ 186:
* [[Data dictionary]] – as defined in the ''IBM Dictionary of Computing'', is a "centralized repository of information about data such as meaning, relationships to other data, origin, usage, and format." Also called a "metadata repository".
* [[Java Database Connectivity]] – .
* [[Open Database Connectivity]] –
* [[Query language]] –
* [[Query optimizer]] – component of a database management system that attempts to determine the most efficient way to execute a query.
* [[Query plan]] – ordered set of steps used to access or modify information in a SQL relational database management system. Also called a "query execution plan".
Line 212 ⟶ 210:
* [[Flat file database]] – various means to encode a database model (most commonly a table) as a single file.
* [[Hierarchical database model]] – data model in which the data is organized into a tree-like structure.
*
* [[Network model]] – database model conceived as a flexible way of representing objects and their relationships.
* [[Relational model]] –
Line 221 ⟶ 219:
=== Other models ===
▲* [[Online analytical processing#Multidimensional databases]] –
* [[Semantic data model]] –
* [[Star schema]] – is the simplest style of data warehouse schema. Also called "star-join schema", "[[data cube]]", or "multi-dimensional schema".
Line 308 ⟶ 305:
== Database-related organizations ==
* ''[[Database (journal)|Database]]''
* ''[[Journal of Database Management]]''
== Database-related publications ==
* [[Ling Liu (computer scientist)|Ling Liu]] and Tamer M. Özsu (Eds.) (2009). "[https://www.springer.com/computer/database+management+&+information+retrieval/book/978-0-387-49616-0 Encyclopedia of Database Systems], 4100 p. 60 illus. {{ISBN|978-0-387-49616-0}}. Table of Content available at http://refworks.springer.com/mrw/index.php?id=1217
* Beynon-Davies, P. (2004). Database Systems. 3rd Edition. Palgrave, Houndmills, Basingstoke.
* Connolly, Thomas and Carolyn Begg. ''Database Systems.'' New York: Harlow, 2002.
* {{cite book|last=Date |first=C. J. |authorlink=Christopher J. Date |title=An Introduction to Database Systems, Fifth Edition |publisher=Addison Wesley |year= 2003 |isbn=0-201-51381-1
* Gray, J. and Reuter, A. ''Transaction Processing: Concepts and Techniques'', 1st edition, Morgan Kaufmann Publishers, 1992.
* Kroenke, David M. and David J. Auer. ''Database Concepts.'' 3rd ed. New York: Prentice, 2007.
* {{cite book|last1=Lightstone |first1=S. |first2=T. |last2=Teorey |first3=T. |last3=Nadeau |title=Physical Database Design: the database professional's guide to exploiting indexes, views, storage, and more |publisher=Morgan Kaufmann Press |year=2007 |isbn=978-0-12-369389-1
* Teorey, T.; Lightstone, S. and Nadeau, T. ''Database Modeling & Design: Logical Design'', 4th edition, Morgan Kaufmann Press, 2005. {{ISBN|0-12-685352-5}}
Line 333 ⟶ 329:
* [[Outline of computing]]
** [[Outline of software]]
* [[Databank]]
* [[Database model]]
* [[Database schema]]
Line 349 ⟶ 346:
== External links ==
{{
* [http://www.fileextension.org/DB DB File extension] – information about files with the DB extension
Line 358 ⟶ 354:
[[Category:Databases|*]]
[[Category:Outlines of computing and engineering|Databases]]
[[Category:
|