🛢DBMS: Metadata Repository (Definitions)

 "A database or storage medium where Metadata are stored and easily accessed by people in an organization." (Margaret Y Chu, "Blissful Data ", 2004)

"A centralized database containing metadata captured from around the enterprise." (Sharon Allen & Evan Terry, "Beginning Relational Data Modeling 2nd Ed.", 2005)

"A database where metadata are stored as structured data that can be easily accessed and queried by business and technology workers." (Danette McGilvray, "Executing Data Quality Projects", 2008)

"A container of consistent definitions of business data and rules for mapping data to their actual physical locations in the system." (Judith Hurwitz et al, "Service Oriented Architecture For Dummies" 2nd Ed., 2009)

"A database constructed for the purpose of storing, managing, and making available metadata." (David C Hay, "Data Model Patterns: A Metadata Map", 2010)

"A container of consistent definitions of business data and rules for mapping data to its actual physical locations in the system." (Marcia Kaufman et al, "Big Data For Dummies", 2013) 

"A metadata repository is a software tool or database used to store and manage metadata." (Piethein Strengholt, "Data Management at Scale", 2020)

🛢DBMS: Repository (Definitions)

"The storage container for the metadata managed by OLAP Services. Metadata is stored in tables in a relational database and is used to define the parameters and properties of OLAP server objects." (Microsoft Corporation, "SQL Server 7.0 System Administration Training Kit", 1999)

"A database containing information models that, in conjunction with the executable software, manage the database." (Anthony Sequeira & Brian Alderman, "The SQL Server 2000 Book", 2003)

"A repository is a collection of resources that can be accessed to retrieve information." (S. Sumathi & S. Esakkirajan, "Fundamentals of Relational Database Management Systems", 2007)

"A database for software and components, with an emphasis on revision control and configuration management. Where they keep the good stuff, in other words." (Judith Hurwitz et al, "Service Oriented Architecture For Dummies" 2nd Ed., 2009)

"A database containing information models that, in conjunction with the executable software, manage the database." (Microsoft, "SQL Server 2012 Glossary", 2012)

"A store of information about the data assets of an organization." (Craig S Mullins, "Database Administration", 2012)

"A database for software and components, with an emphasis on revision control and configuration management (where they keep the good stuff, in other words)." (Marcia Kaufman et al, "Big Data For Dummies", 2013)

"A place where important corporate metadata is stored" (Daniel Linstedt & W H Inmon, "Data Architecture: A Primer for the Data Scientist", 2014)

"a database for software and components, with an emphasis on revision control and configuration management (where they keep the good stuff, in other words)." (Judith S Hurwitz, "Cognitive Computing and Big Data Analytics", 2015)

"A storage location for physical data, preferably databases." (Hamid R Arabnia et al, "Application of Big Data for National Security", 2015)

"In a software context, a repository is a data store that contains the code and or data for a project." (Alex Thomas, "Natural Language Processing with Spark NLP", 2020)

"A database containing information models that, in conjunction with the executable software, manage the database." (Microsoft Technet)

🛢DBMS: Database Design (Definitions)

"1.The process of developing a physical data model, followed by definition of all physical database objects, including tables, indexes, and sequences. 2.The physical data model and the detailed DDL for a database. The database design addresses physical constraints such as storage and performance." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"The process that yields the description of the database structure. The database design process determines the database components. Database design is the second phase of the Database Life Cycle." (Carlos Coronel et al, "Database Systems: Design, Implementation, and Management 9th Ed", 2011)

🛢DBMS: Partitioning (Definitions)

"To divide a table into logical subsets based on characteristics of the data. Partitioning is used to improve application performance or reduce the potential for conflicts in multisite update replication." (Microsoft Corporation, "SQL Server 7.0 System Administration Training Kit", 1999)

"Physically separating data into areas that are more easily maintained or accessed. Data partitioning increases performance and aids in maintenance processes." (Microsoft Corporation, "Microsoft SQL Server 7.0 Data Warehouse Training Kit", 2000)

"The process of splitting a database object (usually a tablespace, table, or index) into two or more physical locations, or partitions, that is, a splitting of a logical group of pages (for example, the pages of a table) into chains or files which are physically removed from each other, perhaps on separate disks. Informix calls this fragmentation." (Peter Gulutzan & Trudy Pelzer, "SQL Performance Tuning", 2002)

"The process of replacing a table with multiple smaller tables. Each smaller table has the same format as the original table, but with a subset of the data. Each partitioned table has rows allocated to it based on some characteristic of the data, such as specific key ranges. The rules that define into which table the rows go must be unambiguous. For example, a table is partitioned into two tables. All rows with primary key values lower than a specified value are allocated to one table, and all keys equal to or greater than the value are allocated to the other. Partitioning can improve application processing speeds and reduce the potential for conflicts in multisite update replication. You can improve the usability of partitioned tables by creating a view. The view, created by a union of select operations on all the partitioned tables, presents the data as if it all resided in a single table." (Anthony Sequeira & Brian Alderman, "The SQL Server 2000 Book", 2003)

"Physical splitting of tables into separate sections (partitions), including parallel processing on multiple partitions and individual operations on individual partitions. One particularly efficient aspect is the capability when querying a table to read fewer than all the partitions making up a table, perhaps even a single partition. This is also known as partition pruning." (Gavin Powell, "Beginning Database Design", 2006)

[data partitioning:] "Process of moving data from a single server to one or more different data repositories. This can be vertical, in which data from a single table is split into multiple tables, or horizontal, in which the number of rows in a table are restricted and partitioned by one or more columns." (Sara Morganand & Tobias Thernstrom , "MCITP Self-Paced Training Kit : Designing and Optimizing Data Access by Using Microsoft SQL Server 2005 - Exam 70-442", 2007)

"The process of replacing a table with multiple smaller units. Tables can be partitioned horizontally or vertically." (Victor Isakov et al, "MCITP Administrator: Microsoft SQL Server 2005 Optimization and Maintenance (70-444) Study Guide", 2007)

"The method for dividing a database into manageable parts for the purpose of easier management and better performance." (Paulraj Ponniah, "Data Warehousing Fundamentals for IT Professionals", 2010)

"The process of splitting a table into subsets of rows or columns." (Carlos Coronel et al, "Database Systems: Design, Implementation, and Management" 9th Ed., 2011)

"The process of replacing a table with multiple smaller tables." (Microsoft, "SQL Server 2012 Glossary,", 2012)

"With respect to distributed databases, partitioning refers to splitting documents, tables, or graphs and distributing them to different servers." (Dan Sullivan, "NoSQL for Mere Mortals®", 2015)

[index-controlled partitioning:] "A type of partitioning in which partition boundaries for a partitioned table are controlled by values that are specified on the CREATE INDEX statement." (Sybase, "Open Server Server-Library/C Reference Manual", 2019)

"Partitioning is the spreading of data across multiple files across a cluster to balance large amounts of data across disks or nodes. Read-only partitions make a read-only table space that prevents updates on all tables in the table space. Other patterns can be applied on this table space to improve performance." (Piethein Strengholt, "Data Management at Scale", 2020)

[composite partitioning:] "In partitioning strategy in which a table is partitioned by one data distribution method and then each partition is further divided into subpartitions using a second data distribution method." (Oracle, "Oracle Database Concepts")

"The ability to decompose very large tables and indexes into smaller and more manageable pieces called partitions." (Oracle, "Oracle Database Concepts")

🛢DBMS: Linked Server (Definitions)

"A definition of an OLE DB data source used by SQL Server distributed queries. The linked server definition specifies the OLE DB provider required to access the data, and includes enough addressing information for the OLE DB provider to connect to the data. Any rowsets exposed by the OLE DB data source can then be referenced as tables, called linked tables, in SQL Server distributed queries." (Microsoft Technet, "Glossary", 0)

"An abstraction of an OLE DB data source that looks like another server to the local SQL Server. A linked server has an associated OLE DB provider that manages the data source. Linked servers allow heterogeneous data access as if the data were local SQL Server data." (Microsoft Corporation, "SQL Server 7.0 System Administration Training Kit", 1999)

"A database object that represents a particular data source and the attributes, including security and collation attributes, necessary to access the data source." (Thomas Moore, "EXAM CRAM™ 2: Designing and Implementing Databases with SQL Server 2000 Enterprise Edition", 2005)

"An OLE DB data source used by SQL Server distributed queries." (Marilyn Miller-White et al, "MCITP Administrator: Microsoft® SQL Server™ 2005 Optimization and Maintenance 70-444", 2007)

"A definition that specifies an external OLE DB database source, such as another SQL Server, or an Oracle server. Once defined, the linked server can be used for distributed queries using only the four-part name in the query." (Darril Gibson, "MCITP SQL Server 2005 Database Developer All-in-One Exam Guide", 2008)

"Database objects that provide the connection information for remote data sources housed on another server. The other server could be a SQL Server, an Oracle server, a Microsoft Access database, or one of many other data sources. Linked servers are created when the remote data source will be accessed more than once or twice." (Robert D. Schneider and Darril Gibson, "Microsoft SQL Server 2008 All-In-One Desk Reference For Dummies", 2008)

"Database objects that provide the connection information for remote data sources housed on another server. The other server could be a SQL Server, an Oracle server, a Microsoft Access database, or one of many other data sources. Linked servers are created when the remote data source will be accessed more than once or twice. See also ad hoc query." (Robert D Schneider & Darril Gibson, "Microsoft SQL Server 2008 All-in-One Desk Reference For Dummies", 2008)

"A definition of an OLE DB data source used by SQL Server distributed queries. The data exposed by a linked server is then referenced as tables, called linked tables." (Jim Joseph, "Microsoft SQL Server 2008 Reporting Services Unleashed", 2009)

"A definition of an OLE DB data source used by SQL Server distributed queries. The linked server definition specifies the OLE DB provider required to access the data, and includes enough addressing information for the OLE DB provider to connect to the data." (Microsoft, "SQL Server 2012 Glossary", 2012)

"This is the remote servers in a distributed query." (Joseph L Jorden & Dandy Weyn, "MCTS Microsoft SQL Server 2005: Implementation and Maintenance Study Guide - Exam 70-431", 2006)

🛢DBMS: Two-Phase Commit [2PC] (Definitions)

"An approach for maintaining consistency over multiple systems. In the first phase, all backends are asked to confirm a requested change so that in the second phase the commitment of the updates usually succeeds." (Nicolai M Josuttis, "SOA in Practice", 2007)

"A protocol that ensures that transactions that apply to more than one server are completed on all servers or on none." (Microsoft Corporation, "SQL Server 7.0 System Administration Training Kit", 1999)

"A mechanism to synchronize updates on different machines or platforms, so that they all fall or all succeed together. The decision to commit is centralized, but each participant has the right to veto. This is a key process in real-time, transaction-based environments." (Atul Apte, "Java™ Connector Architecture: Building Custom Connectors and Adapters", 2002)

"A process that ensures transactions that apply to more than one server are completed on all servers or on none." (Anthony Sequeira & Brian Alderman, "The SQL Server 2000 Book", 2003)

"This is a special transaction involving two servers in which the transaction must be applied to both servers, or the entire transaction is rolled back from both servers." (Joseph L Jorden & Dandy Weyn, "MCTS Microsoft SQL Server 2005: Implementation and Maintenance Study Guide - Exam 70-431", 2006)

"A transaction processing protocol that first ensures the transaction holds locks on all records involved before committing any updates." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A protocol that ensures that transactions that apply to more than one server are completed on all servers or none at all. Two-phase commit is coordinated by the transaction manager and supported by resource managers." (Microsoft, "SQL Server 2012 Glossary", 2012)

"A two-step process by which recoverable resources and an external subsystem are committed. During the first step, the database manager subsystems are polled to ensure that they are ready to commit. If all subsystems respond positively, the database manager instructs them to commit." (IBM, "Informix Servers 12.1", 2014)

"A mechanism that is another control used in databases to ensure the integrity of the data held within the database." (Adam Gordon, "Official (ISC)2 Guide to the CISSP CBK" 4th Ed., 2015)

"A two-step process by which recoverable resources and an external subsystem are committed. During the first step, the database manager subsystems are polled to ensure that they are ready to commit. If all subsystems respond positively, the database manager instructs them to commit. See also distributed transaction." (Sybase, "Open Server Server-Library/C Reference Manual", 2019)

"A feature of transaction processing systems that enables a database to be returned to the pretransaction state if an error condition occurs." (Craig S Mullins, "Database Administration: The Complete Guide to DBA Practices and Procedures", 2012)

"A process that ensures transactions that apply to more than one server are completed on all servers or on none." (Microsoft Technet)

"An operation that is part of a distributed transaction, under the XA specification. (Sometimes abbreviated as 2PC.) When multiple databases participate in the transaction, either all databases commit the changes, or all databases roll back the changes." (MySQL, "MySQL 8.0 Reference Manual Glossary")

"The process of committing a distributed transaction in two phases. In the first phase, the transaction processor checks that all parts of the transaction can be committed. In the second phase, all parts of the transaction are committed. If any part of the transaction indicates in the first phase that it cannot be committed, the second phase does not occur. ODBC does not support two-phase commits." (Microsoft, "ODBC Glossary")

🛢DBMS: Extended Stored Procedure (Definitions)

"A SQL Server-provided procedure that dynamically loads and executes a function within a dynamic link library (DLL) in a manner similar to a stored procedure. Actions outside of SQL Server can be triggered and external information returned to SQL Server. Return status codes and output parameters (identical to their counterparts in regular stored procedures) are also supported." (Microsoft Corporation, "SQL Server 7.0 System Administration Training Kit", 1999)

"A function in a dynamic link library (DLL) that is coded using the SQL Server 2000 Extended Stored Procedure API. The function can then be invoked from Transact-SQL using the same statements that are used to execute Transact- SQL stored procedures." (Anthony Sequeira & Brian Alderman, "The SQL Server 2000 Book", 2003)

"A stored procedure in SQL Server that provides an interface to external COM components (typically DLL files)." (Marilyn Miller-White et al, "MCITP Administrator: Microsoft SQL Server 2005 Optimization and Maintenance 70-444", 2007)

"A function in a dynamic link library (DLL) that is coded using the SQL Server Extended Stored Procedure API. The function can then be invoked from Transact-SQL using the same statements that are used to execute Transact-SQL stored procedures." (Microsoft, "SQL Server 2012 Glossary", 2012)

"Provide a way for SQL Server to add functionality by calling stored procedures. This provides a way to affect external data and to return external data and information to SQL Server." (Owen Williams, "MCSE TestPrep: SQL Server 6.5 Design and Implementation", 1998)

"Extended stored procedures, or XPs, are functions exposed through unmanaged binary DLLs that are designed to run within the SQL Server process space. XPs were used in SQL Server 2000 and prior to programmatically extend the functionality of SQL Server using languages like C and C++ that compile to native code. XPs have been deprecated and SQL CLR functions and procedures are preferred over XPs." (Michael Coles & Rodney Landrum, , "Expert SQL Server 2008 Encryption", 2008)

🛢DBMS: Statistics (Definitions)

"Volatile data about the database, stored in the system catalog so that the optimizer has access to it." (Peter Gulutzan & Trudy Pelzer, "SQL Performance Tuning", 2002)

"Information about tables and indexes stored in the data dictionary used to assist the cost-based optimizer when deciding how to run a given query." (Bob Bryla, "Oracle Database Foundations", 2004)

"SQL Server keeps statistics about the distribution of the key values in each index and uses these statistics to determine what index(es) to use in query processing." (Thomas Moore, "EXAM CRAM™ 2: Designing and Implementing Databases with SQL Server 2000 Enterprise Edition", 2005)

"Information about the distribution of the key values in each index and uses these statistics to determine what index(es) to use in query processing." (Thomas Moore, "MCTS 70-431: Implementing and Maintaining Microsoft SQL Server 2005", 2006)

"Statistics are a small sample of a whole used to represent the whole. In SQL Server, statistics are maintained on indexes and used by the query optimizer to determine which indexes to use for a given query. Instead of scanning an entire index (the entire population), statistical data (a sampling) is maintained on the index." (Darril Gibson, "MCITP SQL Server 2005 Database Developer All-in-One Exam Guide", 2008)

[database statistics:] "In query optimization, refers to measurements about database objects, such as the number of rows in a table, number of disk blocks used, maximum and average row length, number of columns in each row, number of distinct values in each column, etc. Such statistics give a snapshot of database characteristics." (Carlos Coronel et al, "Database Systems: Design, Implementation, and Management" 9th Ed., 2011)

[optimizer statistics:] "Details about the database its object used by the optimizer to select the best execution plan for each SQL statement. Categories include table statistics such as numbers of rows, index statistics such as B-tree levels, system statistics such as CPU and I/O performance, and column statistics such as number of nulls." (Oracle, "Database SQL Tuning Guide Glossary", 2013)

[column statistics:] "Statistics about columns that the optimizer uses to determine optimal execution plans. Column statistics include the number of distinct column values, low value, high value, and number of nulls." (Oracle, "Database SQL Tuning Guide Glossary", 2013)

[index statistics:] "Statistics about indexes that the optimizer uses to determine whether to perform a full table scan or an index scan. Index statistics include B-tree levels, leaf block counts, the index clustering factor, distinct keys, and number of rows in the index." (Oracle, "Database SQL Tuning Guide Glossary", 2013)

"Statistics about tables that the optimizer uses to determine table access cost, join cardinality, join order, and so on. Table statistics include row counts, block counts, empty blocks, average free space per block, number of chained rows, average row length, and staleness of the statistics on the table." (Oracle, "Database SQL Tuning Guide Glossary", 2013)

🛢DBMS: Composite Index (Definitions)

"Indexes which involve more than one column. Use composite indexes when two or more columns are best searched as a unit because of their logical relationship." (Karen Paulsell et al, "Sybase SQL Server: Performance and Tuning Guide", 1996)

"Has two or more columns as index key columns in the same table." (Owen Williams, "MCSE TestPrep: SQL Server 6.5 Design and Implementation", 1998)

"An index that uses more than one column in a table to index data." (Microsoft Corporation, "SQL Server 7.0 System Administration Training Kit", 1999)

[compound index:] "An index whose keys contain values derived from more than one data column." (Peter Gulutzan & Trudy Pelzer, "SQL Performance Tuning", 2002)

"An index that is created on two or more columns in a table." (Bob Bryla, "Oracle Database Foundations", 2004)

"Indexes that can be built on more than a single field." (Gavin Powell, "Beginning Database Design", 2006)

"An index that includes two or more fields." (Rod Stephens, "Beginning Database Design Solutions", 2008)

"An index that is composed of more than one column. Both clustered and nonclustered indexes can be created as composite indexes." (Darril Gibson, "MCITP SQL Server 2005 Database Developer All-in-One Exam Guide", 2008)

"An index that is made of two or more columns." (Robert D. Schneider & Darril Gibson, "Microsoft SQL Server 2008 All-In-One Desk Reference For Dummies", 2008)

"An index that uses more than one column in a table to index data." (Microsoft, "SQL Server 2012 Glossary", 2012)

🛢DBMS: Relational Database (Definitions)

"A collection of data arranged in rows and columns and manipulated using relational algebraic operations." (Joseph P Bigus, "Data Mining with Neural Networks: Solving Business Problems from Application Development to Decision Support", 1996)

"A collection of information organized in tables, each of which models a class of objects of interest to the organization [..]" (Microsoft Corporation, "SQL Server 7.0 System Administration Training Kit", 1999)

"A collection of information organized in tables. Each table models a class of objects of interest to the organization." (Anthony Sequeira & Brian Alderman, "The SQL Server 2000 Book", 2003)

"A collection of tables that stores data without any assumptions as to how the data is related within the tables or between the tables." (Bob Bryla, "Oracle Database Foundations", 2004)

"A method for storing data in multiple tables, where relationships exist between tables." (Margaret Y Chu, "Blissful Data ", 2004)

"A database in which data is viewed as being stored in tables consisting of columns (data items) and rows (units of information). Data from different tables can be combined to form new data relationships." (Sybase, "Glossary", 2005)

"A collection of information organized in tables. Each table models a class of objects of interest to the organization. Each column in a table models an attribute of the object. Each row in a table represents one entity in the class of objects modeled by the table. Queries can use data from one table to find related data in other tables." (Thomas Moore, "MCTS 70-431: Implementing and Maintaining Microsoft SQL Server 2005", 2006)

"The set of requirements and fulfilling data that is developed and documented during critical parameter management. They link many-to-many relationships up and down throughout the hierarchy of the system being developed." (Clyde M Creveling, "Six Sigma for Technical Processes: An Overview for R Executives, Technical Leaders, and Engineering Managers", 2006)

"A database that organizes data in the form of tables." (S. Sumathi & S. Esakkirajan, "Fundamentals of Relational Database Management Systems", 2007)

"A database that stores data in tables containing rows and columns, and that allows queries representing relationships among records in different tables." (Rod Stephens, "Beginning Database Design Solutions", 2008)

"A database where tables hold records containing fields. Fields holding the same values link related tables." (Rod Stephens, "Start Here!™ Fundamentals of Microsoft® .NET Programming", 2011)

"A database for storing structured data. This allows for a fixed format, usually a limited number of values in a defined order." (Kenneth A Shaw, "Integrated Management of Processes and Information", 2013)

"A database in which data is stored in multiple, interrelated tables." (Faithe Wempen, "Computing Fundamentals: Introduction to Computers", 2015)

"A database in which the information is organized into tables related to each other by specific rules." (Mike Harwood, "Internet Security: How to Defend Against Attackers on the Web" 2nd Ed., 2015)

"A database that stores related data in rows and columns in tables." (Rod Stephens, "Beginning Software Engineering", 2015)

"Essentially, a collection of tables or lists." (E C Nelson & Stephen L Nelson, "Excel Data Analysis For Dummies ", 2015)

"A database that can be perceived as a set of tables and manipulated in accordance with the relational model of data. Each database includes a set of system catalog tables that describe the logical and physical structure of the data, a configuration file containing the parameter values allocated for the database, and a recovery log with ongoing transactions and archivable transactions." (Sybase, "Open Server Server-Library/C Reference Manual", 2019)

"A database or database management system that stores information in tables as rows and columns of data, and conducts searches by using the data in specified columns of one table to find additional data in another table." (Microsoft Technet)

"A database in which data is viewed as being stored in tables consisting of columns (data items) and rows (units of information). Data from different tables can be combined to form new data relationships." (Sybase)

"A database that can be perceived as a set of tables and manipulated in accordance with the relational model of data." (IBM)

"A database that conforms to the relational model, storing data in a set of simple relations." (Oracle)

🛢DBMS: Database [DB] (Definitions)

"A collection of interrelated data stored together in one or more computerized files. (IEEE," IEEE Standard Glossary of Software Engineering Terminology", 1990)

"A set of related data tables and other database objects that are organized and presented to serve a specific purpose."  (Karen Paulsell et al, "Sybase SQL Server: Performance and Tuning Guide", 1996)

"A collection of information, data tables, and other objects that are organized and presented to serve a specific purpose, such as facilitation of searching and sorting data."  (Patrick Dalton, "Microsoft SQL Server Black Book", 1997)

"A preallocated portion of a device used  to store database objects and data. (Rob Scrimger et al, "MCSE TestPrep: SQL Server 6.5  Administration", 1998)

"A collection of information, tables, and other objects organized and presented to serve a specific purpose, such as searching, sorting, or recombining data."  (Anthony Sequeira & Brian Alderman, "The SQL Server 2000 Book", 2003)

"A collection of tables that stores data without any assumptions as to how the data is related within the tables or between the tables." (Bob Bryla, "Oracle Database Foundations", 2004)

"A shared collection of logically related data (and a description of this data), designed to meet the information needs of an organization." (Thomas M Connolly & Carolyn E Begg, "Database Solutions: A step-by-step guide to building databases", 2004)

"The collection of all physical files on disk that are associated with a single Oracle instance." (Bob Bryla, "Oracle Database Foundations", 2004)

"A collection of information organized in tables. Each table models a class of objects of interest to the organization. Each column in a table models an attribute of the object. Each row in a table represents one entity in the class of objects modeled by the table. Queries can use data from one table to find related data in other tables." (Thomas Moore, "MCTS 70-431: Implementing and Maintaining Microsoft SQL Server 2005", 2006)

"A collection of persistent data. In a database, data are modeled in accordance with a database model. This model defines the structure of the data, the constraints for integrity and security, and the behavior of the data." (Slawomir Zadrozny et al, "An Overview of Fuzzy Approaches to Flexible Database Querying", 2008)

"A database that stores data in tables containing rows and columns, and that allows queries representing relationships among records in different tables." (Rod Stephens, "Beginning Database Design Solutions", 2008)

"An entity that holds data in some useful way and provides CRUD methods. Modern databases also provide sophisticated methods for joining, sorting, grouping, and otherwise manipulating the data."  (Rod Stephens, "Beginning Database Design Solutions", 2008)

"A collection of information, tables, and other objects organized and presented to serve a specific purpose, such as searching, sorting, and recombining data. Databases are stored in files."  (Jim Joseph, "Microsoft SQL Server 2008 Reporting Services Unleashed", 2009)

"A collection of information organized in tables." (Jim Joseph et al, "Microsoft SQL Server 2008 Reporting Services Unleashed", 2009)

"A collection of records stored in a computer in a systematic way, so that a computer program can consult it to answer questions. For better retrieval and sorting, each record is usually organized as a set of data elements (facts). The items retrieved in answer to queries become information that can be used to make decisions." (Robert J Mockler & Dorothy G. Dologite, "Medical IT Systems and Their Effect on Human Resources", 2009)

"A collection of related information. The information held in the database is stored in an organised way so that specific items can be selected and retrieved quickly." (Yanqing Duan & Mark Xu, "Decision Support Systems in Small Businesses", 2009)

"A database is a tool that stores data, and lets you create, read, update, and delete the data in some manner." (Rod Stephens, "Beginning Database Design Solutions", 2009)

"An entity that holds data in some useful way and provides CRUD methods." (Rod Stephens, "Beginning Database Design Solutions", 2009)

"A collection of interrelated stored data that serves the needs of multiple users; a collection of tables in the relational model." (Toby J Teorey, ", Database Modeling and Design 4th Ed", 2010)

"An organized collection of data, usually in digital form."  (Craig S Mullins, "Database Administration: The Complete Guide to DBA Practices and Procedures" 2nd Ed, 2012)

"A computer system intended to store large amounts of information reliably and in an organized fashion. Most databases provide users with convenient access to the data, along with helpful search capabilities." (Marcia Kaufman et al, "Big Data For Dummies", 2013)

"A structured collection of units of data organized around some topic or theme" (Daniel Linstedt & W H Inmon, "Data Architecture: A Primer for the Data Scientist", 2014)

"Systematically organized or structured repository of indexed information that allows easy retrieval, updating, analysis, and output of data." (Siddhartha Duggirala, "Big Data Architecture: Storage and Computation", 2014)

"A collection of interrelated persistent information stored and organized as a unit in order to serve a specific purpose and satisfy the demands of a set of users. A database can be considered to be an electronic filling system stored on mass-storage systems such as magnetic tape or disk. A database is one component of a database management system." (Ioannis Kouris et al, "Indexing and Compressing Text", 2015)

"a computer system intended to store large amounts of information reliably and in an organized fashion. Most databases provide users convenient access to the data, along with helpful search capabilities." (Judith S Hurwitz, "Cognitive Computing and Big Data Analytics", 2015)

"A structured set of data held in a computer, especially one that is accessible in various ways." (Ronald R Yager & Rachel L Yager, "Fuzzy Social Network Modeling for Influencing Consumer Behavior", 2015)

"Collection of information or data organized together, with individual element having the same set of fields. It is a component of the database management system." (Hamid R Arabnia et al, "Application of Big Data for National Security", 2015)

"Essentially, a collection of tables or lists." (E C Nelson & Stephen L Nelson, "Excel Data Analysis For Dummies ", 2015)

"A set of data contained in a location on a network, computer, or server. Typically, different data sets are stored in different databases. Examples of these databases include inventory, selling price point, and sales, divided into total dollar sales and unit sales."  (Brittany Bullard, "Style and Statistics", 2016)

"A physical set of data records." (Andrew Pham et al, "From Business Strategy to Information Technology Roadmap", 2016)

"A collection of information that is organized so that it can be easily accessed, managed, and updated." (Jonathan Ferrar et al, "The Power of People: Learn How Successful Organizations Use Workforce Analytics To Improve Business Performance", 2017)

"A database is a collection of information (data) that is organized so that it can easily be accessed, managed, and updated. It is the collection of schemes, tables, queries, reports, views and other objects. The data is typically organized to model aspects of reality in a way that supports processes requiring information. In one view, databases can be classified according to types of content: bibliographic, full-text, numeric, and images." (Alessandra Meschini et al, "Expanded Cultural Heritage Representation: Digital Applications for Mixed-Reality Experiences", 2017)

"A collection of data related to a common subject organized in a known structure (the currently used database is a relational database)." (Dan Ophir, "Visualization and Storage of Big Data for Linguistic Applications", 2018)

"A collection of interrelated or independent data items that are stored together to serve one or more applications." (Sybase, "Open Server Server-Library/C Reference Manual", 2019)

"A set of related data tables and other database objects that are organized to serve a specific purpose." (Sybase, "Open Server Server-Library/C Reference Manual", 2019)

"A database is a piece of software used to organize data, generally stored and accessed electronically from a computer system."  (Piethein Strengholt, "Data Management at Scale", 2020)

"A complex combination of structured data in tables that relate to one another, allowing the interactive management of information with automatic implementations, quick updates and specific interrogations." (Cristina Boido et al, "Digital Tools Aimed to Represent Urban Survey", 2021)

"A structured set of data held in a computer, especially one that is accessible in various ways." (Ingrid N Pinto-López, "Fuzzy Reliability Theory: A Bibliometric-Based Review", 2021)

"A digital collection of data stored via a certain technique." (Analytics Insight)

🛢DBMS: Static SQL (Definitions)

[static query:] "A previously saved query that is optimized for a particular execution plan. The opposite of an ad hoc query." (Microsoft Corporation, "Microsoft SQL Server 7.0 Data Warehouse Training Kit", 2000)

"SQL that has been compiled prior to execution." (Ajay Gupta et al, "Informix Dynamic Server 11", 2007)

"SQL statements in an application that do not change at runtime and, therefore, can be hard-coded into the application." (John Goodson & Robert A Steward, "The Data Access Handbook", 2009)

[Static embedded SQL:] "Embedded SQL in which the entire SQL statement can be specified when the program is written, allowing the statement to be precompiled before the program is executed." (Jan L Harrington, "SQL Clearly Explained” 3rd Ed. , 2010)

[static query:] "A stored, precompiled SQL query, optimized for access against a particular database design." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A style of embedded SQL in which the SQL statements do not change while the application is running." (Carlos Coronel et al, "Database Systems: Design, Implementation, and Management" 9th Ed., 2011)

"SQL statements, embedded within a program, that are prepared during the program preparation process (before the program is executed). After being prepared, the SQL statement does not change (although values of host variables specified by the statement might change." (Kirsten A Larsen et al, "Extremely pureXML in DB2 10 for z/OS", 2011)

"SQL queries that are preprocessed and whose access paths are determined during the bind procedure, prior to execution." (Craig S Mullins, "Database Administration", 2012)

"SQL statements that are embedded within a program and are bound before the program is executed. After being bound, a static SQL statement does not change, although values of host variables specified by the statement can change. " (Sybase, "Open Server Server-Library/C Reference Manual", 2019)

"A program where access to the database has been predetermined by the programmer and any input from the user will not change this access pattern. Put another way, all SQL statements are already part of the program when it is executed." (Microfocus)

"A type of embedded SQL in which SQL statements are hard-coded and compiled when the rest of the program is compiled." (Microsoft) 

"It is called static SQL because the SQL statements in the program are static; that is, they do not change each time the program is run."  (Microsoft) [source]

🛢DBMS: Dynamic SQL (Definitions)

"Dynamic SQL is a method of binding between an application program, in one of a number of standard programming languages, and an SQL-implementation." (ISO/IEC 9075-1, 1999)

"In Embedded SQL for C, a SQL statement built and executed at run time." (Microsoft Corporation, "SQL Server 7.0 System Administration Training Kit", 1999)

"SQL that is interpreted during execution of the statement." (Ajay Gupta et al, "Informix Dynamic Server 11", 2007)

"A SQL statement built and executed at runtime by concatenating different parts of the statement based on provided variables." (Darril Gibson, "MCITP SQL Server 2005 Database Developer All-in-One Exam Guide", 2008)

"[...] dynamic SQL is a means of constructing SQL statements as strings in your server-side (or even client-side) applications and executing them dynamically, on the fly. When used properly, dynamic SQL can be used to generate complex queries at runtime, in some cases improve performance, and do tasks that just aren't possible (or are extremely difficult) in standard, nondynamic T-SQL." (Michael Coles, "Pro T-SQL 2008 Programmer's Guide", 2008)

"SQL statements that are constructed at runtime; for example, the application may allow users to enter their own queries. These types of SQL statements are not hard-coded into the application. See also static SQL." (John Goodson & Robert A Steward, "The Data Access Handbook", 2009)

[Dynamic embedded SQL:] "Embedded SQL in which the entire SQL statement cannot be assembled prior to running the program. The SQL statement is therefore completed and processed during the program run." (Jan L Harrington, "SQL Clearly Explained” 3rd Ed., 2010)

"A term used to describe an environment in which the SQL statement is not known in advance, but instead is generated at run time. In a dynamic SQL environment, a program can generate the SQL statements at run time that are required to respond to ad hoc queries." (Carlos Coronel et al, "Database Systems: Design, Implementation, and Management” 9th Ed., 2011)

"Dynamically constructed SQL queries that are not pre-processed, and whose access paths are determined at run time prior to execution." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"SQL statements that are prepared and executed within an application program while the program is executing. In dynamic SQL, the SQL source is contained in host language variables rather than being coded into the application program. The SQL statement can change several times during the application program's execution." (Kirsten A Larsen et al, "Extremely pureXML in DB2 10 for z/OS", 2011)

"SQL queries that are not preprocessed and whose access paths are determined at run time right before execution." (Craig S Mullins, "Database Administration", 2012)

"Allows an Embedded SQL or Client-Library application to execute SQL statements containing variables whose values are determined at runtime." (Sybase, "Open Server Server-Library/C Reference Manual", 2019)

[dynamic SQL statements:] "An SQL statement that is prepared and executed at run time. In dynamic SQL, the SQL statement is contained as a character string in a host variable and is not precompiled." (Sybase, "Open Server Server-Library/C Reference Manual", 2019)

"A feature that lets you create and execute prepared statements using more robust, secure, and efficient methods to substitute parameter values than the naive technique of concatenating the parts of the statement into a string variable." (MySQL)

"A program in which user input determines how the program interacts with the database. Put another way, the SQL statements are not part of the program when it is launched; instead they are built as the program runs." (Microfocus)

"A type of embedded SQL in which SQL statements are created and compiled at run time." (Microsoft) 

"Dynamic SQL is a programming technique that enables you to build SQL statements dynamically at runtime. You can create more general purpose, flexible applications by using dynamic SQL because the full text of a SQL statement may be unknown at compilation." (Oracle) [source]

"Dynamic SQL is an application that uses dynamic code to increase flexibility in querying a database. Dynamic code is generated at execution of a SQL application by inserting statements into variables." (Idera) [source]

🛢DBMS: Database Administrator [DBA] (Definitions)

"The person responsible for creating, installing, configuring, and maintaining databases. Often the system administrator serves as the database administrator." (Microsoft Corporation, "Microsoft SQL Server 7.0 Data Warehouse Training Kit", 2000)

"An individual responsible for management of an RDBMS. Responsibilities may include user management, indexing, tuning, and backup and recovery." (Christopher Adamson, "Mastering Data Warehouse Aggregates", 2006)

"A person or group of people responsible for the design and supervision of a data base." (S. Sumathi & S. Esakkirajan, "Fundamentals of Relational Database Management Systems", 2007)

"An individual responsible for the installation, configuration, administration, monitoring, and maintenance of the DBMS and its physical databases." (Craig S Mullins, "Database Administration", 2012)

"The person who manages a database. The administrator determines the content, internal structure, and access strategy for a database, defines security and integrity, and monitors performance." (Microsoft, "SQL Server 2012 Glossary", 2012)

"One who is responsible for databases used in the business environment; duties might include performing database updates, tuning database performance, coordinating on server hardware and OS issues, defining backup and restore strategies, and of course, security." (Mike Harwood, "Internet Security: How to Defend Against Attackers on the Web" 2nd Ed., 2015)

"The person (or persons) who has (have) the highest possible privileges inside the Oracle database, responsible for its care and feeding, and accountable if there is a loss or corruption of data. In charge of tasks such as space allocation, overall performance tuning, database security and privilege allocation, and physical database design. Some DBAs also perform dual duty as application developers." (Bill Pribyl & Steven Feuerstein, "Learning Oracle PL/SQL", 2001)

"The organizational function charged with the day-to-day monitoring and care of the databases. The DBA function is more closely associated with physical database design than the DA [Data Administrator] is." (William H Inmon, "Building the Data Warehouse", 2005)

"The person in a software organization who is in charge of designing, creating, and maintaining the databases of an enterprise. The DBA makes use of a variety of software tools provided by a DBMS." (Toby J Teorey, ", Database Modeling and Design" 4th Ed., 2010)

"The IT professional role responsible for database administration, usually in the context of a particular DBMS, hence often prefixed with the name of the DBMS, e.g., Oracle DBA. Functional responsibilities vary based on further definitions." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"The person responsible for planning, organizing, controlling, and monitoring the centralized and shared corporate database. The DBA is the general manager of the database administration department." (Carlos Coronel et al, "Database Systems: Design, Implementation, and Management" 9th Ed", 2011)

"A person who is responsible for the design, development, operation, maintenance, and use of a database." (Sybase, "Open Server Server-Library/C Reference Manual", 2019)

"A person who has the responsibility for maintaining a database." (Jan L Harrington, "Relational Database Design and Implementation" 3rd Ed., 2009)

🛢DBMS: Cursors (Definitions)

"A symbolic name associated with a Transact-SQL select statement through a declaration statement. Cursors consist of two parts: the cursor result set and the cursor position." (Karen Paulsell et al, "Sybase SQL Server: Performance and Tuning Guide", 1996)

"Database objects with which applications manipulate data by rows instead of by sets. Using cursors, multiple operations can be performed row-by-row against a result set with or without returning to the original table. For example, a cursor can generate a list of all user-defined table names within a database. Cursors are extremely powerful when combined with stored procedures and the EXECUTE statement." (Patrick Dalton, "Microsoft SQL Server Black Book", 1997)

"An object used to navigate through  records." (Rob Scrimger et al, "MCSE TestPrep: SQL Server 6.5  Administration", 1998)

"A database object used by applications to manipulate data by rows instead of by sets. Using cursors, multiple operations can be performed row by row against a result set with or without returning to the original table. In other words, cursors conceptually return a result set based on tables within the database(s)." (Microsoft Corporation, "Microsoft SQL Server 7.0 System Administration Training Kit", 1999)

"An entity that maps over a result set and establishes a position on a single row within the result set. After the cursor is positioned on a row, operations can be performed on that row, or on a block of rows starting at that position. The most common operation is to fetch (retrieve) the current row or block of rows." (Microsoft Corporation, "Microsoft SQL Server 2000 System Administration", 2001)

"A marker that indicates the current position within a result set." (Peter Gulutzan & Trudy Pelzer, "SQL Performance Tuning", 2002)

"An entity that maps over a result set and establishes a position on a single row within the result set." (Anthony Sequeira & Brian Alderman, "The SQL Server 2000 Book", 2003)

"A construct that holds a rowset from a SELECT statement, which can then be stepped through row by row for various operations." (Thomas Moore, "EXAM CRAM™ 2: Designing and Implementing Databases with SQL Server 2000 Enterprise Edition", 2005)

"Queries in SQL Server return a block of rows called a recordset . A cursor is a subset of a recordset with the added ability to move back and forth through the records." (Joseph L Jorden & Dandy Weyn, "MCTS Microsoft SQL Server 2005: Implementation and Maintenance Study Guide - Exam 70-431", 2006)

"A pointer to the result set of a query. Clients can iterate through a cursor to retrieve results." (MongoDb, 2008)

"An object that allows a program to work through the records returned by a query one at a time. Some databases allow cursors to move forward and backward through the set of returned records whereas others allow only forward movement." (Rod Stephens, "Beginning Database Design Solutions", 2008)

"A moving placement or pointer that indicates a position, used in programs to overcome the impedance mismatch between SQL (set-at-a-time processing) and application programs (record-at-a-time processing)." (Craig S Mullins, "Database Administration", 2012)

"A database element that controls record navigation, updateability of data, and the visibility of changes made to the database by other users." (Microsoft) 

"A handle or name for a private SQL area in the PGA. Because cursors are closely associated with private SQL areas, the terms are sometimes used interchangeably." (Oracle)

"A named control structure used by an application program to point to and select a row of data from a set." (IBM)

"A piece of software that returns rows of data to the application." (Microsoft) 

"A symbolic name that is associated with a SQL statement. In Embedded SQL, a cursor is a data selector that passes multiple rows of data to the host program, one row at a time." (Sybase)

"An embedded SQL query that returns multiple rows." (Microfocus) 

"An internal MySQL data structure that represents the result set of an SQL statement. Often used with prepared statements and dynamic SQL. It works like an iterator in other high-level languages, producing each value from the result set as requested." (MySQL)