GLOSSARY - The Data Access - page 317

Service-Oriented Architecture (SOA)
A way of designing software applications for reusability and flexibility. It involves design-
ing loosely coupled software components called services. See also service.
soft page fault
A type of page fault that is generated when an application requests a page in memory at
its original address space but is eventually located elsewhere in RAM. See also hard page
fault.
statement
A request sent to the database (including the result of the request).
statement pool
A set of prepared statements that an application can reuse.
static SQL
SQL statements in an application that do not change at runtime and, therefore, can be
hard-coded into the application. See also dynamic SQL.
stored procedure
A set of SQL statements (subroutine) available to applications accessing a relational data-
base system. Stored procedures are physically stored in the database.
streaming protocol database system
A database system that processes a query and sends results until there are no more results
to send; the database is uninterruptable. Sybase, Microsoft SQL Server, and MySQL are
examples of streaming protocol databases.
T
throughput
The amount of data that is transferred from sender to receiver over time.
tightly coupled
A dependent relationship between two or more systems or organizations with some kind
of exchange relationship. In the context of Service-Oriented Architecture (SOA) services,
data access is often inadvisably designed to be tightly coupled, or built into the service.
See also loosely coupled.
transaction
One or more SQL statements that make up a unit of work performed against the data-
base. Either all the statements in a transaction are committed as a unit or all the state-
ments are rolled back as a unit.