Outline of databases: Difference between revisions

Browse history interactively

← Previous edit

Content deleted Content added

VisualWikitext

Revision as of 16:30, 7 September 2017 edit KolbertBot (talk \| contribs) Bots 1,166,042 edits m Bot: HTTP→HTTPS ← Previous edit		Latest revision as of 20:22, 29 August 2025 edit undo Kku (talk \| contribs) Extended confirmed users 122,081 edits m link mass surveillance
(48 intermediate revisions by 33 users not shown)
Line 1: {{Short description\|1=Overview of and topical guide to databases}} <!--... Attention: THIS IS AN OUTLINE part of the set of ~~700~~830+ outlines listed at [[~~Portal~~Wikipedia:Contents/Outlines]]. Wikipedia outlines are Line 9 ⟶ 10: content navigation systems See [[Wikipedia: Outlines]] and [[Wikipedia:WikiProject Outlines]] for more details. Further improvements to this outline are on the way ...--> The following ~~[[Wikipedia:OUTLINE\|outline]]~~ 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 29: * [[Active database]] – includes an event driven architecture (often in the form of ECA rules) which can respond to conditions both inside and outside the database. * [[Animation database]] – stores fragments of animations or human movements and which can be accessed, analyzed and queried to develop and assemble new animations. * [[Back-end database]] – accessed by users indirectly through an external application rather than by application programming stored within the database itself or by low level manipulation of the data (e.g. through [[SQL]] commands). * [[Bibliographic database]] – database of bibliographic records, an organized digital collection of references to published literature, including journal and newspaper articles, conference proceedings, reports, government and legal publications, patents, books, etc. * [[Centralized database]] – database located and maintained in one ___location, unlike a distributed database. Line 45: * [[Endgame tablebase]] – computerized database that contains precalculated exhaustive analysis of a chess endgame position. * [[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 80: == History of databases == * [[Database#History\|History of databases]] – * [[Database management system#History\|History of database management systems]] –: ==Database use== Line 106 ⟶ 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 113 ⟶ 112: [[Information retrieval query language]] – query language used to make queries into database, where the semantics of the query are defined not by a precise rendering of a formal syntax, but by an interpretation of the most suitable results of the query. [[SQL]] (Structured Query Language) – special-purpose programming language designed for managing data held in a relational database management system (RDBMS), or for stream processing in a relational data stream management system (RDSMS). ** [[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 121: * [[Negative database]] – credit card terminology for a list of credit card owners who chargeback a lot. === Database design === [[Database design]] – * [[~~Entity-relationship~~Entity–relationship model]] (ER model) – abstract and conceptual representation of data. * [[Database normalization]] – process of organizing the fields and tables of a relational database to minimize redundancy and dependency. * [[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~~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. * [[{{section link\|Data migration#\|Database migration]]}} – * [[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 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. * [[Database storage structures]] – * [[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 152: * [[Relational database management system]] (RDBMS) – database management system (DBMS) that is based on the relational model as introduced by E. * [[Relational model]] – for database management is a database model based on first-order predicate logic, first formulated and proposed in 1969 by Edgar F. * [[~~Object-relational~~Object–relational database]] (ORD) – database management system (DBMS) similar to a relational database, but with an object-oriented database model: objects, classes and inheritance are directly supported in database schemas and in the query language. Also called ~~object-relational~~object–relational database management system (ORDBMS). * [[Transaction processing]] – Line 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 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 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". === Functions === * [[Database administration ~~and automation~~]] – work done by a [[database administrator]], some of which may be automated. * [[Query optimization]] – function of many relational database management systems in which multiple query plans for satisfying a query are examined and a good query plan is identified. * [[Database replication]] – Line 198: === Database products === * [[List of object-oriented database management systems]] – ** [[Comparison of ~~object-relational~~object–relational database management systems]] – * [[List of relational database management systems]] – ** [[Comparison of relational database management systems]] – Line 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. [[ {{section link\|Database model#\|Dimensional model]]}} – [[Network model]] – database model conceived as a flexible way of representing objects and their relationships. * [[Relational model]] – * [[~~Entity-relationship~~Entity–relationship model]] – * [[Graph database]] – uses graph structures with nodes, edges, and properties to represent and store data. * [[Object database]] – database management system in which information is represented in the form of objects as used in object-oriented programming. Also called an "object-oriented database management system". * [[~~Entity-attribute-value~~Entity–attribute–value model]] – === Other models === [[ {{section link\|Online analytical processing#\|Multidimensional databases]]}} –▼ [[Associative model of data]] – alternative data model for database systems. ▲[[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". * [[XML database]] – === Implementations === * [[Flat file database]] – * [[Deductive database]] – database system that can make deductions. * [[Document-oriented database]] – * [[~~Object-relational~~Object–relational database]] – * [[Temporal database]] – database with built-in time aspects, for example a temporal data model and a temporal version of Structured Query Language (SQL). * [[XML database]] – * [[Triplestore]] – purpose-built database for the storage and retrieval of triples, a triple being a data entity composed of subject-predicate-object, like "Bob is 35" or "Bob knows Fred". Line 240 ⟶ 239: ==== Concepts ==== * [[Dimension (data warehouse)\|Dimension]] – * [[Dimensional modeling]] (DM) – is the name of a set of techniques and concepts used in data warehouse design. * [[Fact (data warehouse)\|Fact]] – * [[Online analytical processing]] (OLAP) – or is an approach to swiftly answer multi-dimensional analytical (multi-dimensional analytical\|MDA) queries. * [[Star schema]] – * [[Aggregate (Data Warehouse)\|Aggregate]] – ==== Variants ==== Line 257 ⟶ 256: ==== Elements ==== * [[Data dictionary]] – /[[Metadata]] – * [[Data mart]] – access layer of the data warehouse environment that is used to get data out to the users. * [[Sixth normal form]] (6NF) – term in relational database theory, used in two different ways. * [[Surrogate key]] – ==== Fact ==== * [[Fact table]] – consists of the measurements, metrics or facts of a business process. * [[Early-arriving fact]] – * [[Measure (data warehouse)\|Measure]] – ==== Dimension ==== Line 273 ⟶ 272: ==== Filling ==== * [[Extract, transform, load\|Extract-Transform-Load (ETL)]] – * [[Data extraction]] – act or process of retrieving data out of (usually unstructured or poorly structured) data sources for further data processing or data storage (data migration). * [[Data transformation]] – converts data from a source data format into destination data. * [[Data loading]] – === Using the data warehouse === Line 282 ⟶ 281: ==== Concepts ==== * [[Business intelligence]] (BI) – is defined as the ability for an organization to take all its capabilities and convert them into knowledge, ultimately, getting the right information to the right people, at the right time, via the right channel. * [[Dashboard (business)\|Dashboard]] – * [[Data mining]] – is the process that results in the discovery of new patterns in large data sets. It is the analysis step of the "Knowledge Discovery in Databases" process, or KDD. * [[Decision support system\|Decision support system (DSS)]] – * [[OLAP cube]] – set of data, organized in a way that facilitates non-predetermined queries for aggregated information, or in other words, online analytical processing. ==== Languages ==== * [[Data Mining Extensions]] (DMX) – * [[MultiDimensional eXpressions]] (MDX) – * [[XML for Analysis]] (XMLA) – ==== Tools ==== * [[Business intelligence tools]] – * [[List of reporting software]] – * [[Spreadsheets]] – === People === * [[Edgar F. Codd]] – English Computer scientist who introduced the relational database model * [[Bill Inmon]] – * [[Ralph Kimball]] (Born 1944) – author on the subject of data warehousing and business intelligence. === Products === * [[Comparison of OLAP ~~Servers~~servers]] – == Database-related organizations == * ''[[Database (journal)\|Database]]'' ~~{{Empty section\|date=June 2012}}~~ * ''[[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 ~~\|ref=harv~~}} * 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-61 ~~\|ref=harv~~}} * Teorey, T.; Lightstone, S. and Nadeau, T. ''Database Modeling & Design: Logical Design'', 4th edition, Morgan Kaufmann Press, 2005. {{ISBN\|0-12-685352-5}} Line 323 ⟶ 324: * [[Kamran Parsaye]] * [[C. J. Date]] * [[Peter Chen]] == See also == * [[Outline of computing]] ** [[Outline of software]] * [[Databank]] * [[Database model]] * [[Database schema]] Line 343 ⟶ 346: == External links == {{~~Sisterlinks~~Sister project links\|Databases}} * {{dmoz\|Computers/Data_Formats/Database\|Databases}} * [http://www.fileextension.org/DB DB File extension] – information about files with the DB extension {{Outline footer}} [[Category:Databases\| *]] [[Category:~~Wikipedia~~Outlines ~~outlines~~of computing and engineering\|Databases]] [[Category:Outlines\|Databases]]