🧱IT: Batch Processing (Definitions)

"A computer application that runs in a sequential series of processing steps." (Sharon Allen & Evan Terry, "Beginning Relational Data Modeling" 2nd Ed., 2005)

"Computer environment in which programs (usually long-running, sequentially oriented) access data exclusively, and user interaction is not allowed while the activity is occurring." (William H Inmon, "Building the Data Warehouse", 2005)

"Processing system that processes inputs at fixed intervals as a file and operates on it all at once; contrasts with online (or interactive) processing." (Linda Volonino & Efraim Turban, "Information Technology for Management" 8th Ed,, 2011)

[batch job:] "A set of computer processes that can be run without user interaction." (Microsoft, "SQL Server 2012 Glossary", 2012)

"A type of processing whereby computer programs are coded into jobs that are submitted for execution and run to completion without online interaction or manual intervention." (Craig S Mullins, "Database Administration", 2012)

"A noninteractive process that runs in a queue, usually when the system load is lowest, and generally used for processing batches of information in a serial and usually efficient manner. Early computers were capable of only batch processing." (Marcia Kaufman et al, "Big Data For Dummies", 2013)

"The collection of transaction into 'batches' that are processed collectively." (Daniel Linstedt & W H Inmon, "Data Architecture: A Primer for the Data Scientist", 2014)

"A processing strategy in which transactions are not handled immediately; rather, receipts are collected and processed as a batch." (Mike Harwood, "Internet Security: How to Defend Against Attackers on the Web" 2nd Ed., 2015)

🛢DBMS: Batch (Definitions)

"One or more Transact-SQL statements terminated by an end-of-batch signal, which submits them to SQL Server for processing." (Karen Paulsell et al, "Sybase SQL Server: Performance and Tuning Guide", 1996)

"A set of SQL statements submitted together and executed as a group. A script is often a series of batches submitted one after the other." (Patrick Dalton, "Microsoft SQL Server Black Book", 1997)

"Denotes a set of statements executed together." (Owen Williams, "MCSE TestPrep: SQL Server 6.5 Design and Implementation", 1998)

"A set of SQL statements submitted together and executed as a group. A script is often a series of batches submitted one after the other. A batch, as a whole, is compiled only one time and is terminated by an end-of-batch signal (such as the GO command in SQL Server utilities)." (Microsoft Corporation, "SQL Server 7.0 System Administration Training Kit", 1999)

"A set of SQL statements submitted together and executed as a group. A script is often a series of batches submitted one after the other." (Anthony Sequeira & Brian Alderman, "The SQL Server 2000 Book", 2003)

"Multiple batches can be combined in a single script or procedure using the GO Keyword to separate the batches. A collection of zero, one, or more T-SQL statements sent to SQL Server to be run together." (Thomas Moore, "EXAM CRAM™ 2: Designing and Implementing Databases with SQL Server 2000 Enterprise Edition", 2005)

"A collection of zero, one, or more T-SQL statements sent to SQL Server to be run together. Multiple batches can be combined in a single script or procedure, using the GO keyword to separate the batches." (Thomas Moore, "MCTS 70-431: Implementing and Maintaining Microsoft SQL Server 2005", 2006)

"A set of requests or transactions that have been grouped together." (Microsoft, "SQL Server 2012 Glossary", 2012)

"A group of commands or statements.  A Client-Library command batch is one or more Client-Library commands terminated by an application’s call to ct_send. For example, an application can batch together commands to declare, set rows for, and open a cursor. A Transact-SQL statement batch is one or more Transact-SQL statements submitted to an Adaptive Server by means of a single Client-Library command or Embedded SQL statement." (Sybase, "Open Server Server-Library/C Reference Manual", 2019)