Sql 2008 R2 Definitions

Front 1

.bak

Back 1

The file name extension of an auxiliary file, created either automatically or upon command, that contains the second-most-recent version of a file and that bears the same file name.

Front 2

.dat

Back 2

The generic file name extension of a data file.

Front 3

.NET Framework

Back 3

An integral Windows component that supports building, deploying, and running the next generation of applications and XML Web services. It provides a highly productive, standards-based, multilanguage environment for integrating existing investments with next generation applications and services, as well as the agility to solve the challenges of deployment and operation of Internet-scale applications. The .NET Framework consists of three main parts: the common language runtime, a hierarchical set of unified class libraries, and a componentized version of ASP called ASP.NET.

Front 4

2PC

Back 4

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.

Front 5

access control list

Back 5

In Windows-based systems, a list of access control entries (ACE) that apply to an entire object, a set of the object's properties, or an individual property of an object, and that define the access granted to one or more security principals.

Front 6

accessibility

Back 6

The quality of a system incorporating hardware or software to engage a flexible, customizable user interface, alternative input and output methods, and greater exposure of screen elements to make the computer usable by people with cognitive, hearing, physical, or visual disabilities.

Front 7

accessor

Back 7

A data structure or group of structures created by the consumer that describes how row or parameter data from the data store is to be laid out in the consumer's data buffer, enabling providers to optimize access. An accessor is a collection of bindings.

Front 8

action

Back 8

An end-user-initiated operation on a selected cube or portion of a cube.

Front 9

activation

Back 9

The process of starting a service program in response to a Service Broker message.

Front 10

active statement

Back 10

A SQL statement that has been run but whose result set has not yet been canceled or fully processed.

Front 11

ActiveX Data Objects

Back 11

A data access interface that communicates with OLE DB-compliant data sources to connect to, retrieve, manipulate, and update data.

Front 12

ActiveX Data Objects (Multidimensional)

Back 12

A high-level, language-independent set of object-based data access interfaces optimized for multidimensional data applications.

Front 13

ActiveX Data Objects MultiDimensional.NET

Back 13

A .NET managed data provider that provides access to multidimensional data sources, such as Microsoft SQL Server Analysis Services.

Front 14

activity data

Back 14

Data generated as part of a business transaction by executing an activity within an application. It is characterized by an exclusive write access pattern.

Front 15

ad hoc reporting

Back 15

A reporting system that enables end users to run queries and create custom reports without having to know the technicalities of the underlying database schema and query syntax.

Front 16

adapter host

Back 16

The root abstract class Adapter, which defines the handshake between the adapter and the StreamInsight server in the ENQUEUE interaction point. It provides all the required adapter services such as memory management, and exception handling.

Front 17

add-in

Back 17

A supplemental program that can extend the capabilities of an application program.

Front 18

ADF

Back 18

An XML file that fully describes a single Notification Services application. The ADF file contains the schemas for the events, subscriptions, and notifications; the rules for matching events with subscriptions; and may provide the name of the XSLT file used to format generated notifications.

Front 19

adjective phrasing

Back 19

A way of expressing a relationship in English in which an entity is described by an adjective.

Front 20

ADO

Back 20

A data access interface that communicates with OLE DB-compliant data sources to connect to, retrieve, manipulate, and update data.

Front 21

ADO MD

Back 21

A high-level, language-independent set of object-based data access interfaces optimized for multidimensional data applications.

Front 22

ADOMD.NET

Back 22

A .NET managed data provider that provides access to multidimensional data sources, such as Microsoft SQL Server Analysis Services.

Front 23

adornment

Back 23

A control or status area that is attached to the edge of a pane or window, such as a toolbar or ruler.

Front 24

Agent XP

Back 24

An option to enable extended stored procedures.

Front 25

aggregate

Back 25

A single value that is composed of multiple values.

Front 26

aggregate

Back 26

To combine multiple values.

Front 27

aggregate

Back 27

Pertaining to a combination of multiple values.

Front 28

aggregate function

Back 28

A function that performs a calculation on multiple values and returns a single value.

Front 29

aggregate query

Back 29

A query (SQL statement) that summarizes information from multiple rows by including an aggregate function such as Sum or Avg.

Front 30

aggregate type

Back 30

A data type composed of multiple elements. An aggregate can be homogeneous (all elements have the same type) e.g. an array, a list in a functional language, a string of characters, a file; or it can be heterogeneous (elements can have different types) e.g. a structure.

Front 31

aggregation

Back 31

A table or structure containing pre-calculated data for an online analytical processing (OLAP) cube. Aggregations support the rapid and efficient querying of a multidimensional database.

Front 32

aggregation prefix

Back 32

A string that is combined with a system-defined ID to create a unique name for a partition's aggregation table.

Front 33

aggregation wrapper

Back 33

A wrapper that encapsulates a COM object within another COM object.

Front 34

alert

Back 34

An audible or visual warning signal, generated by a computer, indicating that a threshold has been or is about to be breached.

Front 35

alias

Back 35

An alternative label for some object, such as a file or data collection.

Front 36

alias type

Back 36

A user-defined data type based on one of the SQL Server system data types that can specify a certain data type, length, and nullability.

Front 37

alignment

Back 37

A condition whereby an index is built on the same partition scheme as that of its corresponding table.

Front 38

allocation unit

Back 38

A set of pages that can be operated on as a whole. Pages belonging to an allocation unit are tracked by Index Allocation Map (IAM) pages. An allocation unit consists of the IAM page chain and all pages marked allocated in that IAM page chain. An allocation unit can contain at most a single IAM chain, and an IAM chain must belong to one, and only one, allocation unit.

Front 39

AMO

Back 39

A collection of .NET namespaces included with Analysis Services, used to provide administrative functionality for client applications.

Front 40

Analysis Management Objects

Back 40

A collection of .NET namespaces included with Analysis Services, used to provide administrative functionality for client applications.

Front 41

Analysis Services

Back 41

A feature of Microsoft SQL Server that supports online analytical processing (OLAP) and data mining for business intelligence applications. Analysis Services organizes data from a data warehouse into cubes with precalculated aggregation data to provide rapid answers to complex analytical queries.

Front 42

analytical data

Back 42

Data that provides the values that are associated with spatial data. For example, spatial data defines the locations of cities in an area whereas analytical data provides the population for each city.

Front 43

ancestor

Back 43

In a tree structure, the element of which a given element is a child. Equivalent to a parent element.

Front 44

ancestor element

Back 44

In a tree structure, the element of which a given element is a child. Equivalent to a parent element.

Front 45

anchor cap

Back 45

A line cap where the width of the cap is bigger than the width of the line.

Front 46

anchor member

Back 46

The first invocation of a recursive CTE consists of one or more CTE_query_definition joined by UNION ALL, UNION, EXCEPT or INTERSECT operators. Because these query definitions form the base result set of the CTE structure, they are referred to as anchor members.

Front 47

animation manager

Back 47

A core component of an animation application and the central programmatic interface for managing (creating, scheduling, and controlling) animations.

Front 48

annotational property

Back 48

A property that is maintained by Metadata Services as string data that can be attached to any repository object that exposes the IAnnotationalProps interface.

Front 49

anonymous subscription

Back 49

A type of pull subscription for which detailed information about the subscription and the Subscriber is not stored.

Front 50

ANSI to OEM conversion

Back 50

The conversion of characters that must occur when data is transferred from a database that stores character data using a specific code page to a client application on a computer that uses a different code page. Typically, Windows-based client computers use ANSI/ISO code pages, and some databases (for compatibility reasons) might use OEM code pages.

Front 51

antialiasing

Back 51

A software technique for smoothing the jagged appearance of curved or diagonal lines caused by poor resolution on a display screen. Methods of anti-aliasing include surrounding pixels with intermediate shades and manipulating the size and horizontal alignment of the pixels.

Front 52

anti-aliasing

Back 52

A software technique for smoothing the jagged appearance of curved or diagonal lines caused by poor resolution on a display screen. Methods of anti-aliasing include surrounding pixels with intermediate shades and manipulating the size and horizontal alignment of the pixels.

Front 53

API

Back 53

A set of routines that an application uses to request and carry out lower-level services performed by a computer's operating system. These routines usually carry out maintenance tasks such as managing files and displaying information.

Front 54

API server cursor

Back 54

A server cursor that is built to support the cursor functions of an API, such as ODBC, OLE DB, ADO, and DB-Library.

Front 55

API support

Back 55

A set of routines that an application uses to request and carry out lower-level services performed by a computer's operating system. These routines usually carry out maintenance tasks such as managing files and displaying information.

Front 56

application database

Back 56

The database that stores user and system data for one application. The application database contains the events, subscriptions, and notifications for the application. It also contains system metadata, including the schemas for the events, subscriptions, and notifications for the application; and the match rules for the application.

Front 57

application definition file

Back 57

An XML file that fully describes a single Notification Services application. The ADF file contains the schemas for the events, subscriptions, and notifications; the rules for matching events with subscriptions; and may provide the name of the XSLT file used to format generated notifications.

Front 58

application program interface

Back 58

A set of routines that an application uses to request and carry out lower-level services performed by a computer's operating system. These routines usually carry out maintenance tasks such as managing files and displaying information.

Front 59

application programming interface

Back 59

A set of routines that an application uses to request and carry out lower-level services performed by a computer's operating system. These routines usually carry out maintenance tasks such as managing files and displaying information.

Front 60

application role

Back 60

A SQL Server role created to support the security needs of an application.

Front 61

application time

Back 61

The clock time supplied by applications which must communicate their application time to the StreamInsight server so that all temporal operators refer to the timestamp of the events and never to the system clock of the host machine.

Front 62

apply branch

Back 62

The set of operations applied to an event group is called the apply branch.

Front 63

arbitration port

Back 63

A TCP/IP port used by the cache hosts to determine whether a cache host in the cluster has become unavailable. The port number that is used for arbitration can be different on each cache host.

Front 64

ARIMA

Back 64

A method for determining dependencies in observations taken sequentially in time, that also supports multiplicative seasonality.

Front 65

arithmetic overflow

Back 65

A condition that results from calculating a column value that exceeds the column's specified size.

Front 66

article

Back 66

A component in a publication. For example, a table, a column, or a row.

Front 67

assembly

Back 67

A managed application module containing class metadata and managed code as an object in SQL Server, against which CLR functions, stored procedures, triggers, user-defined aggregates, and user-defined types can be created in SQL Server.

Front 68

associative array

Back 68

An array composed of a collection of keys and a collection of values, where each key is associated with one value. The keys and values can be of any type.

Front 69

atom feed

Back 69

An XML structure that contains metadata about content, such as the language version and the date when the content was last modified, and is sent to subscribers by using the Atom Publishing Protocol (AtomPub).

Front 70

atomic

Back 70

Pertaining to an operation where all the transaction data modifications must be performed; either all of the transaction data modifications are performed or none are performed.

Front 71

attribute

Back 71

A single characteristic or additional piece of information (financial or non-financial) that exists in a database.

Front 72

attribute hierarchy

Back 72

A flat hierarchy (typically having an All level and a member level) containing a single attribute. It is created from one column in a dimension table, if supported by the cube.

Front 73

attribute relationship

Back 73

The hierarchy associated with an attribute containing a single level based on the corresponding column in a dimension table.

Front 74

attribute type

Back 74

The type of information contained by an attribute, such as quarters or months in a time dimension, which may enable specific treatment by the server and client applications.

Front 75

auditing

Back 75

The process an operating system uses to detect and record security-related events, such as an attempt to create, to access, or to delete objects such as files and directories. The records of such events are stored in a file known as a security log, whose contents are available only to those with the proper clearance.

Front 76

authentication

Back 76

The process of verifying the identity of a user, computer, process, or other entity by validating the credentials provided by the entity. Common forms of credentials are digital signatures, smart cards, biometric data, and a combination of user names and passwords.

Front 77

authenticator

Back 77

A data structure used by one party to prove that another party knows a secret key. In the Kerberos authentication protocol, authenticators include timestamps, to prevent replay attacks, and are encrypted with the session key issued by the Key Distribution Center (KDC).

Front 78

authorization

Back 78

The process of granting a person, computer process, or device access to certain information, services or functionality. Authorization is derived from the identity of the person, computer process, or device requesting access, which is verified through authentication.

Front 79

autocommit mode

Back 79

The default transaction management mode for the Database Engine. The Database Engine automatically starts a transaction for each individual Transact-SQL statement. When the statement completes, the transaction is committed or rolled back based on the success or failure of the statement.

Front 80

auto-consistency check

Back 80

A feature that automatically runs a consistency check on protected data sources when it detects an inconsistent replica.

Front 81

automatic failover

Back 81

In a database mirroring session, a failover initiated by the witness and mirror upon the failure of the principal server (if the database is in a synchronized state).

Front 82

automatic recovery

Back 82

Recovery that occurs every time SQL Server is restarted.

Front 83

auto-protection

Back 83

In DPM, a feature that automatically identifies and adds new data sources for protection.

Front 84

autoregressive integrated moving average

Back 84

A method for determining dependencies in observations taken sequentially in time, that also supports multiplicative seasonality.

Front 85

axis

Back 85

A set of tuples. Each tuple is a vector of members. A set of axes defines the coordinates of a multidimensional data set.

Front 86

back up

Back 86

To make a duplicate copy of a program, a disk, or data.

Front 87

backing stream

Back 87

The existing stream, that the new stream will be based on.

Front 88

backup

Back 88

A duplicate of a program, a disk, or data, made either for archiving purposes or for safeguarding files.

Front 89

backup copy

Back 89

A duplicate of a program, a disk, or data, made either for archiving purposes or for safeguarding files.

Front 90

backup device

Back 90

A tape or disk drive containing a backup medium.

Front 91

backup file

Back 91

A duplicate of a program, a disk, or data, made either for archiving purposes or for safeguarding files.

Front 92

backup medium

Back 92

Disk file or tape used to hold one or more backups.

Front 93

backup set

Back 93

A collection of files, folders, and other data that have been backed up and stored in a file or on one or more tapes.

Front 94

balanced hierarchy

Back 94

A dimension hierarchy in which all leaf nodes are the same distance from the root node.

Front 95

base backup

Back 95

A data backup of a database or files upon which a differential backup is fully or partially based. The base backup is the most recent full or file backup of the database or files.

Front 96

base data type

Back 96

Any system-supplied data type, for example, char , varchar , binary , and varbinary . User-defined data types are derived from base data types.

Front 97

base object

Back 97

The object that a synonym references.

Front 98

base table

Back 98

A table stored permanently in a database. Base tables are referenced by views, cursors, SQL statements, and stored procedures.

Front 99

basic marker map

Back 99

A map that displays a marker at each location (for example, cities) and varies marker color, size, and type.

Front 100

batch

Back 100

A set of requests or transactions that have been grouped together.

Front 101

batch job

Back 101

A set of computer processes that can be run without user interaction.

Front 102

batch processing

Back 102

The execution of a batch file.

Front 103

batching

Back 103

The process of sending changes in small groups instead of in a one-shot transfer of the data in its entirety.

Front 104

BI Development Studio

Back 104

A project development and management tool for business intelligence solution developers. It can be used to design end-to-end business intelligence solutions that integrate projects from Microsoft SQL Server Analysis Services (SSAS), Microsoft SQL Server Integration Services (SSIS), and Microsoft SQL Server Reporting Services (SSRS).

Front 105

billion

Back 105

In American usage (as is usual with microcomputers), a thousand million, or 109. Computer terminology uses the prefixes giga-for 1 billion and nano-for 1 billionth.

Front 106

binary large object

Back 106

A discrete packet of binary data that has an exceptionally large size, such as pictures or audio tracks stored as digital data, or any variable or table column large enough to hold such values. The designation "binary large object" typically refers to a packet of data that is stored in a database and is treated as a sequence of uninterpreted bytes.

Front 107

binder

Back 107

A tool/module that creates a binding/bindery.

Front 108

binding

Back 108

In Analysis Services, a defined relationship between an attribute or a measure and one or more underlying columns in a dimension or fact table.

Front 109

bit pattern

Back 109

A combination of bits, often used to indicate the possible unique combinations of a specific number of bits. For example, a 3-bit pattern allows 8 possible combinations and an 8-bit pattern allows 256 combinations.

Front 110

bitwise operation

Back 110

An operation that manipulates a single bit, or tests whether a bit is on or off.

Front 111

blittable type

Back 111

A data type that has a unique characteristic and an identical presentation in memory for both managed and unmanaged environments. It can be directly shared.

Front 112

blob

Back 112

A discrete packet of binary data that has an exceptionally large size, such as pictures or audio tracks stored as digital data, or any variable or table column large enough to hold such values. The designation "binary large object" typically refers to a packet of data that is stored in a database and is treated as a sequence of uninterpreted bytes.

Front 113

BLOb

Back 113

A discrete packet of binary data that has an exceptionally large size, such as pictures or audio tracks stored as digital data, or any variable or table column large enough to hold such values. The designation "binary large object" typically refers to a packet of data that is stored in a database and is treated as a sequence of uninterpreted bytes.

Front 114

BLOB

Back 114

A discrete packet of binary data that has an exceptionally large size, such as pictures or audio tracks stored as digital data, or any variable or table column large enough to hold such values. The designation "binary large object" typically refers to a packet of data that is stored in a database and is treated as a sequence of uninterpreted bytes.

Front 115

block

Back 115

A Transact-SQL statement enclosed by BEGIN and END.

Front 116

block cursor

Back 116

A cursor with a rowset size greater than 1.

Front 117

blocking transaction

Back 117

A transaction that causes another transaction to fail.

Front 118

Boolean

Back 118

Of, pertaining to, or characteristic of logical (true, false) values.

Front 119

Boolean expression

Back 119

An expression that yields a Boolean value (true or false). Such expressions can involve comparisons (testing values for equality or, for non-­Boolean values, the < [less than] or > [greater than] relation) and logical combination (using Boolean operators such as AND, OR, and XOR) of Boolean expressions.

Front 120

Boolean operator

Back 120

An operator designed to work with Boolean values. The four most common Boolean operators in programming use are AND (logical conjunction), OR (logical inclusion), XOR (exclusive OR), and NOT (logical negation).

Front 121

bound stream

Back 121

An event stream that contains all the information needed to produce events. Either the information is an already instantiated data source, or the information is sufficient for the StreamInsight server to start the data source.

Front 122

bounding box

Back 122

The smallest rectangular area that will surround a path, shape, or group of objects.

Front 123

box plot chart

Back 123

A statistical type of chart that uses boxes to indicate statistical distribution and easily identify outlier points. There are five values: upper quartile, lower quartile, High Box, Low Box, and Median.

Front 124

breakpoint

Back 124

A location in a program at which execution is halted so that a programmer can examine the program's status, the contents of variables, and so on.

Front 125

browse button

Back 125

A button that displays a dialog box to help users select a valid value.

Front 126

browse mode

Back 126

A function that lets you scan database rows and update their values one row at a time.

Front 127

B-tree

Back 127

A tree structure for storing database indexes.

Front 128

bubble map

Back 128

A geographical map that displays a circle over specific locations, where the radius of the circle is proportional to a numeric value.

Front 129

buffer pool

Back 129

A block of memory reserved for index and table data pages.

Front 130

buffer size

Back 130

The size of the area of memory reserved for temporary storage of data.

Front 131

built-in functions

Back 131

A group of predefined functions provided as part of the Transact-SQL and Multidimensional Expressions languages.

Front 132

BUILTIN\Administrators

Back 132

User account (local administrators)

Front 133

bulk copy

Back 133

An action of copying a large set of data.

Front 134

bulk export

Back 134

To copy a large set of data rows out of a SQL Server table into a data file.

Front 135

bulk import

Back 135

To load a large amount of data, usually in batches, from a data file or repository to another data repository.

Front 136

bulk load

Back 136

An action of inserting a large set of rows into a table.

Front 137

bulk log backup

Back 137

A backup that includes log and data pages changed by bulk operations. Point-in-time recovery is not allowed.

Front 138

bulk rowset provider

Back 138

A provider used for the OPENROWSET instruction to read data from a file. In SQL Server 2005, OPENROWSET can read from a data file without loading the data into a target table. This enables you to use OPENROWSET with a simple SELECT statement.

Front 139

Bulk Smart Card Issuance Tool

Back 139

A software program running on a client computer that a certificate manager can use to simultaneously issue multiple certificates.

Front 140

bulk-logged recovery model

Back 140

A database recovery mode that minimally logs bulk operations, such as index creation and bulk imports, while fully logging other transactions. Bulk-logged recovery increases performance for bulk operations, and is intended to be used an adjunct to the full recovery model.

Front 141

Business Intelligence Development Studio

Back 141

A project development and management tool for business intelligence solution developers. It can be used to design end-to-end business intelligence solutions that integrate projects from Microsoft SQL Server Analysis Services (SSAS), Microsoft SQL Server Integration Services (SSIS), and Microsoft SQL Server Reporting Services (SSRS).

Front 142

business logic

Back 142

The part of an application program that performs the required data processing of the business. It refers to the routines that perform the data entry, update, query and report processing, and more specifically to the processing that takes place behind the scenes rather than the presentation logic required to display the data on the screen.

Front 143

business logic handler

Back 143

A merge replication feature that allows you to run custom code during the synchronization process.

Front 144

business logic handler framework

Back 144

The business logic handler framework allows you to write a managed code assembly that is called during the merge synchronization process.

Front 145

business rules

Back 145

The logical rules that are used to run a business

Front 146

cache aging

Back 146

The mechanism of caching that determines when a cache row is outdated and must be refreshed.

Front 147

cache client

Back 147

A .NET application that uses the Windows Server AppFabric client APIs to communicate with and store data to a Windows Server AppFabric distributed cache system.

Front 148

cache cluster

Back 148

The instantiation of the distributed cache service, made up of one or more instances of the cache host service working together to store and distribute data. Data is stored in memory to minimize response times for data requests. This clustering technology differs from Windows Clustering.

Front 149

cache invalidation

Back 149

The process of flagging an object in the cache so that it will no longer be used by any cache clients. This occurs when an object remains in cache longer than the cache time-out value (when it expires).

Front 150

cache item

Back 150

An object that is stored in the cache and additional information associated with that object, such as tags and version. It can be extracted from the cache cluster using the GetCacheItem client API.

Front 151

cache notification

Back 151

An asynchronous notification that can be triggered by a variety of cache operations on the cache cluster. Cache notifications can be used to invoke application methods or automatically invalidate locally cached objects.

Front 152

cache operation

Back 152

An event that occurs on regions or cached items that can trigger a cache notification.

Front 153

cache port

Back 153

A TCP/IP port used by cache hosts to transmit data to and from the cache clients. The port number used for the cache port can be different on each cache host. These settings are maintained in the cluster configuration settings.

Front 154

cache region

Back 154

A container of data, within a cache, that co-locates all cached objects on a single cache host. Cache Regions enable the ability to search all cached objects in the region by using descriptive strings, called tags.

Front 155

cache service

Back 155

A process running the “Velocity” service, participating as a member of the cache cluster.

Front 156

cache tag

Back 156

One or more optional string-based identifiers that can be associated with each cached object stored in a region. Regions allow you to retrieve cached objects based on one or more tags.

Front 157

cache-aside programming pattern

Back 157

A programming pattern in which if the data is not present in the cache, the application, not the distributed cache system, must reload data into the cache from the original data source.

Front 158

cache-enabled application

Back 158

An application that uses the Windows Server AppFabric cache client to store data in cache on the cache cluster.

Front 159

calculated column

Back 159

A type of column that displays the results of mathematical or logical operations or expressions instead of stored data.

Front 160

calculated column

Back 160

A type of column that displays the results of mathematical or logical operations or expressions instead of stored data.

Front 161

calculated field

Back 161

A field defined in a query that displays the result of an expression rather than displaying stored data. The value is recalculated each time a value in the expression changes.

Front 162

calculated member

Back 162

A member of a dimension whose value is calculated at run time by using an expression. Calculated member values can be derived from the values of other members.

Front 163

calculation condition

Back 163

A Multidimensional Expressions (MDX) logical expression that is used to determine whether a calculation formula will be applied against a cell in a calculation subcube.

Front 164

calculation formula

Back 164

A Multidimensional Expressions (MDX) expression used to supply a value for cells in a calculation subcube, subject to the application of a calculation condition.

Front 165

calculation pass

Back 165

A stage of calculation in a multidimensional cube in which applicable calculations are evaluated.

Front 166

calculation pass number

Back 166

An ordinal position used to refer to a calculation pass.

Front 167

calculation subcube

Back 167

The set of multidimensional cube cells that is used to create a calculated cells definition. The set of cells is defined by a combination of MDX set expressions.

Front 168

callback

Back 168

The process used to authenticate users calling in to a network. During callback, the network validates the caller's username and password, hangs up, and then returns the call, usually to a preauthorized number. This process prevents unauthorized access to an account even if an individual's logon ID and password have been stolen.

Front 169

call-level interface

Back 169

The interface supported by ODBC for use by an application.

Front 170

candidate key

Back 170

A column or set of columns that have a unique value for each row in a table.

Front 171

cap

Back 171

For paths that contain unconnected ends, such as lines, the end of a stroke. You can change the way the stroke looks at each end by applying one of four end cap styles: flat cap, round cap, square cap, and triangle cap.

Front 172

cardinality

Back 172

The number of entities that can exist on each side of a relationship.

Front 173

carousel view

Back 173

In PowerPivot Gallery, a specialized view where the preview area is centered and the thumbnails that immediately precede and follow the current thumbnail are adjacent to the preview area.

Front 174

cascading delete

Back 174

For relationships that enforce referential integrity between tables, the deletion of all related records in the related table or tables when a record in the primary table is deleted.

Front 175

cascading update

Back 175

For relationships that enforce referential integrity between tables, the updating of all related records in the related table or tables when a record in the primary table is changed.

Front 176

case

Back 176

An abstract view of data characterized by attributes and relations to other cases.

Front 177

case key

Back 177

The element of a case by which the case is referenced within a case set.

Front 178

catalog views

Back 178

Built-in views that form the system catalog for SQL Server.

Front 179

catastrophic error

Back 179

An error that causes the system or a program to fail abruptly with no hope of recovery. An example of a fatal error is an uncaught exception that cannot be handled.

Front 180

CD sleeve

Back 180

A case for holding CDs.

Front 181

CD-ROM

Back 181

A form of storage characterized by high capacity (roughly 650 MB) and the use of laser optics instead of magnetic means for reading data.

Front 182

cell

Back 182

In a cube, the set of properties, including a value, specified by the intersection when one member is selected from each dimension.

Front 183

cellset

Back 183

In ADO MD, an object that contains a collection of cells selected from cubes or other cellsets by a multidimensional query.

Front 184

centralized registration model

Back 184

A registration model that removes all certificate subscriber participation from the management policy. For the workflow, a user designated as the originator will initiate the request and an enrollment agent will execute the request.

Front 185

CEP

Back 185

The continuous and incremental processing of event streams from multiple sources based on declarative query and pattern specifications with near-zero latency.

Front 186

CEP engine

Back 186

The core engine and adapter framework components of Microsoft StreamInsight. The StreamInsight server can be used to process and analyze the event streams associated with a complex event processing application.

Front 187

CERN

Back 187

A physics research center located in Geneva, Switzerland, where the original development of the World Wide Web took place under the leadership of Tim Berners-Lee in 1989 as a method to facilitate communication among members of the scientific community.

Front 188

certificate

Back 188

A digital document that is commonly used for authentication and to help secure information on a network. A certificate binds a public key to an entity that holds the corresponding private key. Certificates are digitally signed by the certification authority that issues them, and they can be issued for a user, a computer, or a service.

Front 189

certificate enrollment

Back 189

The process of requesting, receiving, and installing a certificate.

Front 190

certificate issuer

Back 190

The certification authority which issued the certificate to the subject.

Front 191

Certificate Lifecycle Manager Client

Back 191

A suite of Certificate Lifecycle Manager (CLM) client tools that assist end users with managing their smart cards. The tools include the Smart Card Self Service Control, the Smart Card Personalization Control, and the Certificate Profile Update Control. See Smart Card Self-Service Control, Smart Card Personalization Control, Certificate Profile Update Control.

Front 192

certificate manager

Back 192

A Certificate Lifecycle Manager (CLM) user that has the appropriate CLM permissions to either administer other CLM users or to administer the CLM application itself.

Front 193

certificate manager Web portal

Back 193

A Web application running on the Certificate Lifecycle Manager (CLM) server. This portal allows certificate administrators to administer other users’ certificates and smart cards. The certificate subscriber and certificate manager Web portals are both accessed through the same universal resource locator (URL); however, the content displayed is based on a user's roles and permissions.

Front 194

Certificate Profile Update Control

Back 194

An ActiveX control that automates the update of Certificate Lifecycle Manager (CLM) profiles on client computers.

Front 195

certificate revocation

Back 195

The process of revoking a digital certificate.

Front 196

certificate subscriber

Back 196

A user that needs certificates with our without smart cards. Certificate subscribers can access a small number of functions that can only be performed for the user’s own certificates.

Front 197

certificate subscriber Web portal

Back 197

A Web application running on the Certificate Lifecycle Manager (CLM) server. This component of the CLM server interacts directly with users in a self-service mode. The specific functionality is based upon Active Directory group memberships and permissions. The certificate subscriber and certificate manager Web portals are both accessed through the same universal resource locator (URL); however, the content displayed is based on a user's roles and permissions.

Front 198

certificate template

Back 198

A Windows construct that specifies the format and content of certificates based on their intended usage. When requesting a certificate from a Windows enterprise certification authority (CA), certificate requestors can select from a variety of certificate types that are based on certificate templates.

Front 199

change applier

Back 199

An object that performs conflict detection, conflict handling, and change application for a batch of changes.

Front 200

change propagation

Back 200

The process of applying changes from one replica to another.

Front 201

change script

Back 201

A text file that contains SQL statements for all changes made to a database, in the order in which they were made, during an editing session.

Front 202

change unit

Back 202

The minimal unit of change tracking in a store. In change propagation, only the units that are changed must be sent; whereas, in conflict detection, independent changes to the same unit are considered a conflict.

Front 203

changing dimension

Back 203

A dimension that has a flexible member structure, and is designed to support frequent changes to structure and data.

Front 204

character encoding

Back 204

A one-to-one mapping between a set of characters and a set of numbers.

Front 205

character set

Back 205

A grouping of alphabetic, numeric, and other characters that have some relationship in common. For example, the standard ASCII character set includes letters, numbers, symbols, and control codes that make up the ASCII coding scheme.

Front 206

chart data region

Back 206

A report item on a report layout that displays data in a graphical format.

Front 207

checkpoint

Back 207

An event in which the Database Engine writes dirty buffer pages to disk. Each checkpoint writes to disk all the pages that were dirty at the last checkpoint and still have not been written to disk.

Front 208

checksum

Back 208

A calculated value that is used to test data for the presence of errors that can occur when data is transmitted or when it is written to disk. The checksum is calculated for a given chunk of data by sequentially combining all the bytes of data with a series of arithmetic or logical operations. After the data is transmitted or stored, a new checksum is calculated in the same way using the (possibly faulty) transmitted or stored data. If the two checksums do not match, an error has occurred, and the data should be transmitted or stored again. Checksums cannot detect all errors, and they cannot be used to correct erroneous data.

Front 209

child

Back 209

In a tree structure, the relationship of a node to its immediate predecessor.

Front 210

chronicle

Back 210

A table that stores state information for a single application. An example is an event chronicle, which can store event data for use with scheduled subscriptions.

Front 211

chunk

Back 211

A specified  amount of data.

Front 212

claims identity

Back 212

A unique identifier that represents a specific user, application, computer, or other entity, enabling it to gain access to multiple resources, such as applications and network resources, without entering credentials multiple times. It also enables resources to validate requests from an entity.

Front 213

clause

Back 213

In Transact-SQL, a subunit of an SQL statement. A clause begins with a keyword.

Front 214

clean shutdown

Back 214

A system shutdown that occurs without errors.

Front 215

clear text

Back 215

Data in its unencrypted or decrypted form.

Front 216

cleartext

Back 216

Data in its unencrypted or decrypted form.

Front 217

CLI

Back 217

The interface supported by ODBC for use by an application.

Front 218

clickstream analysis

Back 218

Clickstream data are information that users generate as they move from page to page and click on items within a Web site, usually stored in log files. Web site designers can use clickstream data to improve users' experiences with a site.

Front 219

clickthrough report

Back 219

A report that displays related report model data when you click data within a rendered Report Builder report.

Front 220

client

Back 220

A service, application, or device that wants to integrate into the Microsoft Sync Framework architecture.

Front 221

client

Back 221

A computer or program that connects to or requests the services of another computer or program.

Front 222

client code generation

Back 222

The action of generating code for the client project based on operations and entities exposed in the middle tier. A RIA Services link must exist between the client and server projects.

Front 223

client cursor

Back 223

A cursor that is implemented on the client. The entire result set is first transferred to the client, and the client API software implements the cursor functionality from this cached result set.

Front 224

client subscription

Back 224

A subscription to a merge publication that uses the priority value of the Publisher for conflict detection and resolution.

Front 225

client type

Back 225

Information that determines how a cache client functions and impacts the performance of your application. There are two client types: a simple client type and a routing client type.

Front 226

CLM Audit

Back 226

A Certificate Lifecycle Manager (CLM) extended permission in Active Directory that allows the generation and display of CLM policy templates, defining management policies within a profile template, and generating CLM reports.

Front 227

CLM credentials

Back 227

User account information that can be used to authenticate a user to Certificate Lifecycle Manager (CLM). These credentials can be in the form of domain credentials or one-time passwords.

Front 228

CLM Enroll

Back 228

A Certificate Lifecycle Manager (CLM) extended permission in Active Directory that allows the initiation, running, or completion of an enrollment request.

Front 229

CLM Enroll

Back 229

A Certificate Lifecycle Manager (CLM) extended permission in Active Directory that allows the user to specify the workflow and the data to be collected while issuing certificates using a template. This extended permission only applies to profile templates.

Front 230

CLM Enrollment Agent

Back 230

A Certificate Lifecycle Manager (CLM) extended permission in Active Directory that allows a user or group to perform certificate requests on behalf of another user. The issued certificate’s subject will contain the target user’s name, rather than the requestor’s name.

Front 231

CLM Recover

Back 231

A Certificate Lifecycle Manager (CLM) extended permission in Active Directory that allows the initiation of encryption key recovery from the certification authority database.

Front 232

CLM Renew

Back 232

A Certificate Lifecycle Manager (CLM) extended permission in Active Directory that allows the initiation, running, or completion of an enrollment request. The renew request replaces a user’s certificate that is near its expiration date with a new certificate that has a new validity period.

Front 233

CLM reports

Back 233

Audit information pertaining to credential management activities within Certificate Lifecycle Manager (CLM).

Front 234

CLM Request Enroll

Back 234

A Certificate Lifecycle Manager (CLM) extended permission in Active Directory that allows the initiation, running, or completion of an enrollment request.

Front 235

CLM Request Recover

Back 235

A Certificate Lifecycle Manager (CLM) extended permission in Active Directory that allows the initiation of encryption key recovery from the certification authority database.

Front 236

CLM Request Renew

Back 236

A Certificate Lifecycle Manager (CLM) extended permission in Active Directory that allows the initiation, running, or completion of an enrollment request. The renew request replaces a user’s certificate that is near its expiration date with a new certificate that has a new validity period.

Front 237

CLM Request Revoke

Back 237

A Certificate Lifecycle Manager (CLM) extended permission in Active Directory that allows the revocation of a certificate before the expiration of the certificate’s validity period. An example of when this is necessary is if a user’s computer or smart card is compromised (stolen).

Front 238

CLM Request Unblock Smart Card

Back 238

A Certificate Lifecycle Manager (CLM) extended permission in Active Directory that enables a smart card’s User Personal Identification Number (PIN) to be reset, allowing access to the key material on a smart card and for that material to be re-established.

Front 239

CLM Revoke

Back 239

A Certificate Lifecycle Manager (CLM) extended permission in Active Directory that allows the revocation of a certificate before the expiration of the certificate’s validity period. An example of when this is necessary is if a user’s computer or smart card is compromised (stolen).

Front 240

clock vector

Back 240

A collection of clock vector elements that represents updates to a replica. Any change that occurs between 0 and the tick count is contained in the vector.

Front 241

clock vector element

Back 241

A pair of values, consisting of a replica key and a tick count, that represents a change to a replica.

Front 242

CLR function

Back 242

A function created against a SQL Server assembly whose implementation is defined in an assembly created in the .NET Framework common language runtime (CLR).

Front 243

CLR stored procedure

Back 243

A stored procedure created against a SQL Server assembly whose implementation is defined in an assembly created in the .NET Framework common language runtime (CLR).

Front 244

CLR trigger

Back 244

A trigger created against a SQL Server assembly whose implementation is defined in an assembly created in the .NET Framework common language runtime (CLR).

Front 245

CLR user-defined type

Back 245

A user-defined data type created against a SQL Server assembly whose implementation is defined in an assembly created in the .NET Framework common language runtime (CLR).

Front 246

cluster configuration storage location

Back 246

The shared location (or shared storage location) where cluster configuration information is persisted. It can be a shared file or a database.

Front 247

cluster disk resource

Back 247

A disk on a cluster storage device.

Front 248

cluster node

Back 248

An individual computer in a server cluster.

Front 249

cluster port

Back 249

A TCP/IP port used by the cache hosts to manage the cache cluster. The port number used for the cluster ports can be different on each cache host. These settings are maintained in the cluster configuration settings.

Front 250

cluster repair

Back 250

A repair operation in which all missing or corrupt files are replaced, all missing or corrupt registry keys are replaced and all missing or invalid configuration values are set to default values.

Front 251

clustered index

Back 251

An index in which the logical order of the key values determines the physical order of the corresponding rows in a table.

Front 252

clustered server

Back 252

A server that belongs to a server cluster.

Front 253

clustering

Back 253

A data mining technique that analyzes data to group records together according to their location within the multidimensional attribute space.

Front 254

coarse-grained lock

Back 254

A lock that applies to a large amount of code or data.

Front 255

code access security

Back 255

A mechanism provided by the common language runtime whereby managed code is granted permissions by security policy and these permissions are enforced, helping to limit the operations that the code will be allowed to perform.

Front 256

code element

Back 256

The minimum bit combination that can represent a unit of encoded text for processing or exchange.

Front 257

code page

Back 257

A table that relates the character codes (code point values) used by a program to keys on the keyboard or to characters on the display. This provides support for character sets and keyboard layouts for different countries or regions.

Front 258

code point

Back 258

The minimum bit combination that can represent a unit of encoded text for processing or exchange.

Front 259

cold standby

Back 259

A second data center that can provide availability within hours or days.

Front 260

collation

Back 260

A set of rules that determines how data is compared, ordered, and presented.

Front 261

collection

Back 261

An object that contains a set of related objects. An object's position in the collection can change whenever a change occurs in the collection; therefore, the position of any specific object in a collection may vary.

Front 262

collection item

Back 262

An instance of a collector type that is created with a specific set of input properties and collection frequency, and that is used to gather specific types of data.

Front 263

collection mode

Back 263

The frequency at which data is collected and uploaded to the management data warehouse.

Front 264

collection set

Back 264

A group of collection items with which a user can interact through the user interface.

Front 265

collector type

Back 265

A logical wrapper around the SQL Server Integration Services packages that provide the actual mechanism for collecting data and uploading it to the management data warehouse.

Front 266

collocate

Back 266

To select a partitioned table that contains related data and join with this table on the partitioning column.

Front 267

collocation

Back 267

A condition whereby partitioned tables and indexes are partitioned according to equivalent partition functions.

Front 268

color range

Back 268

The range of colors available to a display device.

Front 269

color rule

Back 269

A rule that applies to fill colors for polygons, lines, and markers that represent points or polygon center points.

Front 270

color scale

Back 270

A scale that displays the results of color rules only.

Front 271

column

Back 271

The area in each row of a database table that stores the data value for some attribute of the object modeled by the table.

Front 272

column binding

Back 272

The binding of an Analysis Services object to a column in a data source view.

Front 273

column delimiter

Back 273

A character which separates columns from each other in the CSV file being imported/exported.

Front 274

column filter

Back 274

A filter that restricts columns that are to be included as part of a snapshot, transactional, or merge publication.

Front 275

Column Pattern Profile

Back 275

A report containing a set of regular expressions that cover the specified percentage of values in a string column.

Front 276

column set

Back 276

An untyped XML representation that combines all the sparse columns of a table into a structured output.

Front 277

column-level collation

Back 277

Supporting multiple collations in a single instance.

Front 278

column-level constraint

Back 278

A constraint definition that is specified within a column definition when a table is created or altered.

Front 279

columnstore index

Back 279

Stores each column in a separate set of disk pages rather than storing multiple rows per page.

Front 280

COM

Back 280

An object-based programming model designed to promote software interoperability; it allows two or more applications or components to easily cooperate with one another, even if they were written by different vendors, at different times, in different programming languages, or if they are running on different computers running different operating systems.

Front 281

command buffer

Back 281

An area in memory in which commands entered by the user are kept. A command buffer can enable the user to repeat commands without retyping them completely, edit past commands to change some argument or correct a mistake, undo commands, or obtain a list of past commands.

Front 282

command prompt

Back 282

An interface between the operating system and the user in which the user types command language strings of text that are passed to the command interpreter for execution.

Front 283

command relationship

Back 283

Provides instructions to hardware based on natural-language questions or commands.

Front 284

commit

Back 284

An operation that saves all changes to databases, cubes, or dimensions made since the start of a transaction.

Front 285

committed

Back 285

Characteristic of a transaction that is logged and cannot be rolled back.

Front 286

commodity channel index formula

Back 286

A formula that calculates the mean deviation of the daily average price of a commodity from the moving average. A value above 100 indicates that the commodity is overbought, and a value below -100 indicates that the commodity is oversold.

Front 287

comparator

Back 287

A device for comparing two items to determine whether they are equal. In electronics, for example, a comparator is a circuit that compares two input voltages and indicates which is higher.

Front 288

compilation error

Back 288

An error which occurs while compiling an application. These compilation errors typically occur because syntax was entered incorrectly.

Front 289

compile time

Back 289

The amount of time required to perform a compilation of a program. Compile time can range from a fraction of a second to many hours, depending on the size and complexity of the program, the speed of the compiler, and the performance of the hardware.

Front 290

complete database restore

Back 290

A restore of a full database backup, the most recent differential database backup (if any), and the log backups (if any) taken since the full database backup.

Front 291

complex event processing

Back 291

The continuous and incremental processing of event streams from multiple sources based on declarative query and pattern specifications with near-zero latency.

Front 292

Component Object Model

Back 292

An object-based programming model designed to promote software interoperability; it allows two or more applications or components to easily cooperate with one another, even if they were written by different vendors, at different times, in different programming languages, or if they are running on different computers running different operating systems.

Front 293

composable

Back 293

Pertaining to the ability to form complex queries by using query components (objects or operators) as reusable building blocks. This is done by linking query components together or encapsulating query components within each other.

Front 294

composed environment

Back 294

A virtual environment that was created from virtual machines. Those virtual machines were created outside of Microsoft Test Manager and are already deployed on a host group.

Front 295

composite index

Back 295

An index that uses more than one column in a table to index data.

Front 296

composite key

Back 296

A key whose definition consists of two or more fields in a file, columns in a table, or attributes in a relation.

Front 297

compositional hierarchy

Back 297

A set of entities that are conceptually part of a hierarchy, such as a parent entity and a child entity. Data operations require that the entities be treated as a single unit.

Front 298

computed column

Back 298

A virtual column in a table whose value is computed at run time.

Front 299

computed field

Back 299

A value in a formatted notification that has been computed by using a Transact-SQL expression.

Front 300

COM-structured storage file

Back 300

A component object model (COM) compound file used by Data Transformation Services (DTS) to store the version history of a saved DTS package.

Front 301

concatenation

Back 301

The process of combining two or more character strings or expressions into a single character string or expression, or combining two or more binary strings or expressions into a single binary string or expression.

Front 302

concurrency

Back 302

A process that allows multiple users to access and change shared data at the same time. The Entity Framework implements an optimistic concurrency model.

Front 303

concurrency conflict

Back 303

A conflict that occurs when the same item or change unit is changed on two different replicas that are later synchronized.

Front 304

concurrency model

Back 304

A way in which an application can be designed to account for concurrent operations that use the same cached data. Windows Server AppFabric supports optimistic and pessimistic concurrency models.

Front 305

concurrent operation

Back 305

A computer operation in which two or more processes (programs) have access to the microprocessor's time and are therefore carried out nearly simultaneously. Because a microprocessor can work with much smaller units of time than people can perceive, concurrent processes appear to be occurring simultaneously but in reality are not.

Front 306

conditional expression

Back 306

An expression that yields a Boolean value (true or false). Such expressions can involve comparisons (testing values for equality or, for non-­Boolean values, the < [less than] or > [greater than] relation) and logical combination (using Boolean operators such as AND, OR, and XOR) of Boolean expressions.

Front 307

conditional split

Back 307

A restore of a full database backup, the most recent differential database backup (if any), and the log backups (if any) taken since the full database backup.

Front 308

config file

Back 308

A file that contains machine-readable operating specifications for a piece of hardware or software or that contains information on another file or on a specific user, such as the user's logon ID.

Front 309

configuration

Back 309

In reference to a single microcomputer, the sum of a system's internal and external components, including memory, disk drives, keyboard, video, and generally less critical add-on hardware, such as a mouse, modem, or printer. Software (the operating system and various device drivers), the user's choices established through configuration files such as the AUTOEXEC.BAT and CONFIG.SYS files on IBM PCs and compatibles, and sometimes hardware (switches and jumpers) are needed to "configure the configuration" to work correctly. Although system configuration can be changed, as by adding more memory or disk capacity, the basic structure of the system--its architecture--remains the same.

Front 310

configuration file

Back 310

A file that contains machine-readable operating specifications for a piece of hardware or software or that contains information on another file or on a specific user, such as the user's logon ID.

Front 311

Configuration Tools

Back 311

In SQL Server, a menu item which allows the user to enable, disable, start, or stop the features, services, and remote connectivity of the SQL Server installations.

Front 312

conflict detection

Back 312

The process of determining which operations were made by one replica without knowledge of the other, such as when two replicas make local updates to the same item.

Front 313

conflict resolution method

Back 313

The method that is used to determine which change is written to the store in the event of a conflict. Typical conflict resolution methods are as follows: last writer wins, source wins, destination wins, custom, or deferred. For custom resolution, the resolving application reads the conflict from the conflict log and selects a resolution. For deferred resolution, the conflict is logged together with the conflicting change data and the made-with knowledge of the change.

Front 314

conflict resolver

Back 314

A special mechanism which handles resolving of conflict situations.

Front 315

Connection Director

Back 315

A connectivity technology where applications based on different data access technologies (.NET or native Win32) can share the same connection information. Connection information can be centrally managed for such client applications.

Front 316

connection manager

Back 316

A logical representation of a run-time connection to a data source.

Front 317

connection string

Back 317

A series of semicolon-delimited arguments that define the location of a database and how to connect to it.

Front 318

consistency unit

Back 318

The minimal unit of data synchronization. Because all changes that have the same consistency unit are sent together, synchronization can never be interrupted with part of a consistency unit applied.

Front 319

constant

Back 319

A numeric or string value that is not calculated and, therefore, does not change.

Front 320

constraint conflict

Back 320

A conflict that violates constraints that are put on items or change units, such as the relationship of folders or the location of identically-named data within a file system.

Front 321

constraint violation

Back 321

A violation that occurs when the restriction criteria are not satisfied.

Front 322

contained database

Back 322

A SQL Server database that includes all of the user authentication, database settings, and metadata required to define and access the database, and has no configuration dependencies on the instance of the SQL Server Database Engine where the database is installed.

Front 323

container

Back 323

A control flow element that provides package structure.

Front 324

content formatter

Back 324

The part of the distributor that turns raw notification data into readable messages.

Front 325

content key

Back 325

The key used to both encrypt and decrypt protected content during publishing and consumption.

Front 326

contention

Back 326

On a network, competition among stations for the opportunity to use a communications line or network resource.

Front 327

context switch

Back 327

The changing of the identity against which permissions to execute statements or perform actions are checked.

Front 328

continuation media

Back 328

The series of removable backup media used after the initial medium becomes full, allowing continuation of the backup operation.

Front 329

continuation tape

Back 329

A tape that is used after the initial tape in a media family fills, allowing continuation of a media family.

Front 330

contract

Back 330

A Service Broker object that defines the message types that can be exchanged within a given conversation.

Front 331

control flow

Back 331

A group of connected control flow elements that perform tasks.

Front 332

control-break report

Back 332

A report that summarizes data in user-defined groups or breaks. A new group is triggered when different data is encountered.

Front 333

control-of-flow language

Back 333

Transact-SQL keywords that control the flow of execution of SQL statements and statement blocks in triggers, stored procedures, and batches.

Front 334

conversation endpoint

Back 334

The object which represents a party participating in the conversation.

Front 335

conversation group

Back 335

A group of related Service Broker conversations. Messages in the same conversation group can only be processed by one service program at a time.

Front 336

conversation handle

Back 336

An handle which uniquely defines a conversation.

Front 337

coordinate system

Back 337

In n-dimensional space, a set of n linearly independent vectors anchored to a point (called the origin). A group of coordinates specifies a point in space (or a vector from the origin) by indicating how far to travel along each vector to reach the point (or tip of the vector).

Front 338

correlated subquery

Back 338

A subquery that references a column in the outer statement. The inner query is run for each candidate row in the outer statement.

Front 339

cost of goods sold

Back 339

An accounting category used to sum the financial consequences of manufacturing products and carrying inventory.

Front 340

count window

Back 340

A window with a variable window size that moves along a timeline with each distinct event start time.

Front 341

countersign

Back 341

To sign a document already signed by the other party.

Front 342

CPU busy

Back 342

A SQL Server statistic that reports the time, in milliseconds, that the central processing unit (CPU) spent on SQL Server work.

Front 343

crawl

Back 343

The process of scanning content to compile and maintain an index.

Front 344

credentials

Back 344

Information that includes identification and proof of identification that is used to gain access to local and network resources. Examples of credentials are user names and passwords, smart cards, and certificates.

Front 345

cross-database ownership chaining

Back 345

An ownership chain that spans more than one database.

Front 346

cross-validation

Back 346

A method for evaluating the accuracy of a data mining model.

Front 347

CTI event

Back 347

A special punctuation event that indicates the completeness of the existing events.

Front 348

cube

Back 348

A set of data that is organized and summarized into a multidimensional structure that is defined by a set of dimensions and measures.

Front 349

cube role

Back 349

A collection of users and groups with the same access to a cube. A cube role is created when you assign a database role to a cube, and it applies only to that cube.

Front 350

current time increment event

Back 350

A special punctuation event that indicates the completeness of the existing events.

Front 351

cursor

Back 351

An entity that maps over a result set and establishes a position on a single row within the result set.

Front 352

cursor degradation

Back 352

The return of a different type of cursor than the user had declared.

Front 353

cursor library

Back 353

A part of the ODBC and DB-Library application programming interfaces (APIs) that implements client cursors

Front 354

custom rollup

Back 354

An aggregation calculation that is customized for a dimension level or member, and that overrides the aggregate functions of a cube's measures.

Front 355

custom rule

Back 355

In a role, a specification that limits the dimension members or cube cells that users in the role are permitted to access.

Front 356

custom variable

Back 356

A variable provided by package developers.

Front 357

custom volume

Back 357

A volume that is not in the DPM storage pool and is specified to store the replica and recovery points for a protection group member.

Front 358

cyclic protection

Back 358

A type of protection between two DPM servers where each server protects the data on the other.

Front 359

DAC

Back 359

A single unit of management that captures the SQL Server database and instance objects used by a client-server or 3-tier application.

Front 360

DAC instance

Back 360

A copy of a DAC deployed on an instance of the Database Engine. There can be multiple DAC instances on the same instance of the Database Engine.

Front 361

DAC package

Back 361

An XML manifest that contains all of the objects defined for the DAC; the package gets created when a developer builds a DAC project.

Front 362

DAC package file

Back 362

The XML file that is the container of a DAC package.

Front 363

DAC placement policy

Back 363

A PBM policy that comprises a set of conditions, which serve as prerequisites on the target instance of SQL Server where the DAC can be deployed.

Front 364

DAC project

Back 364

A Visual Studio project used by database developers to create and develop a DAC. DAC projects get full support from Visual Studio and VSTS source code control, versioning, and development project management.

Front 365

data adapter

Back 365

An object used to submit data to and retrieve data from databases, Web services, and Extensible Markup Language (XML) files.

Front 366

data backup

Back 366

Any backup that includes the full image of one or more data files.

Front 367

data binning

Back 367

The process of grouping data into specific bins or groups according to defined criteria.

Front 368

data block

Back 368

In text, ntext, and image data, a data block is the unit of data transferred at one time between an application and an instance of SQL Server. The term is also applied to the units of storage for these data types.

Front 369

data co-location

Back 369

In DPM, a feature that enables protection of multiple data sources on a single volume or on the same tape. This allows you to store more data on each volume or tape.

Front 370

data connection

Back 370

A connection that specifies the name, type, location, and, optionally, other information about a database file or server.

Front 371

Data Control Language

Back 371

The subset of SQL statements used to control permissions on database objects.

Front 372

data convergence

Back 372

Data at the Publisher and the Subscriber that matches.

Front 373

data corruption

Back 373

A process wherein data in memory or on disk is unintentionally changed, with its meaning thereby altered or obliterated.

Front 374

data definition

Back 374

The attributes, properties, and objects in a database.

Front 375

data definition language

Back 375

A language that defines all attributes and properties of a database, especially record layouts, field definitions, key fields, file locations, and storage strategy.

Front 376

data description language

Back 376

A language that defines all attributes and properties of a database, especially record layouts, field definitions, key fields, file locations, and storage strategy.

Front 377

data dictionary

Back 377

A database containing data about all the databases in a database system. Data dictionaries store all the various schema and file specifications and their locations. They also contain information about which programs use which data and which users are interested in which reports.

Front 378

data element

Back 378

A single unit of data.

Front 379

data explosion

Back 379

The exponential growth in size of a multidimensional structure, such as a cube, due to the storage of aggregated data.

Front 380

data extension

Back 380

A plug-in that processes data for a specific kind of data source. For example, Microsoft OLE DB Provider for DB2.

Front 381

data feed

Back 381

An XML data stream in Atom 1.0 format.

Front 382

data flow

Back 382

The movement of data through a group of connected elements that extract, transform, and load data.

Front 383

data flow component

Back 383

A component of SQL Server 2005 Integration Services that manipulates data.

Front 384

data flow engine

Back 384

An engine that executes the data flow in a package.

Front 385

data flow task

Back 385

The task that encapsulates the data flow engine that moves data between sources and destinations, providing the facility to transform, clean, and modify data as it is moved.

Front 386

data flow task

Back 386

The task that encapsulates the data flow engine that moves data between sources and destinations, providing the facility to transform, clean, and modify data as it is moved.

Front 387

data integrity

Back 387

The accuracy of data and its conformity to its expected value, especially after being transmitted or processed.

Front 388

data manipulation language

Back 388

The subset of SQL statements that is used to retrieve and manipulate data. DML statements typically start with SELECT INSERT UPDATE or DELETE.

Front 389

data mart

Back 389

A subset of the contents of a data warehouse that tends to contain data focused at the department level, or on a specific business area.

Front 390

data member

Back 390

A child member associated with a parent member in a parent-child hierarchy. A data member contains the data value for its parent member, rather than the aggregated value for the parent's children.

Front 391

data mining

Back 391

The process of identifying commercially useful patterns or relationships in databases or other computer repositories through the use of advanced statistical tools.

Front 392

data mining extension

Back 392

In Analysis Services, a statement that performs mining tasks programmatically.

Front 393

data mining model training

Back 393

The process a data mining model uses to estimate model parameters by evaluating a set of known and predictable data.

Front 394

data processing extension

Back 394

A plug-in that processes data for a specific kind of data source (similar to a database driver).

Front 395

Data Processor component

Back 395

A component of the report server engine that processes data.

Front 396

Data Profile Viewer

Back 396

A stand-alone utility that displays the profile output in both summary and detail format with optional drilldown capability.

Front 397

data provider

Back 397

A known data source specific to a target type that provides data to a collector type.

Front 398

data pump

Back 398

A component used in SQL Server 2000 Transformation Services (DTS) to import, export, and transform data between heterogeneous data stores.

Front 399

data region

Back 399

A report item that provides data manipulation and display functionality for iterative data from an underlying dataset.

Front 400

data scrubbing

Back 400

The process of building a data warehouse out of data coming from multiple online transaction processing (OLTP) systems.

Front 401

data segment

Back 401

The portion of memory or auxiliary storage that contains the data used by a program.

Front 402

data set

Back 402

A collection of related information made up of separate elements that can be treated as a unit in data handling.

Front 403

data source view

Back 403

A named selection of database objects--such as tables, views, relationships, and stored procedures, based on one or more data sources--that defines the schema referenced by OLAP and data mining objects in an Analysis Services databases. It can also be used to define sources, destinations, and lookup tables for DTS tasks, transformations, and data adapters.

Front 404

data steward

Back 404

The person responsible for maintaining a data element in a metadata registry.

Front 405

data viewer

Back 405

A graphical tool that displays data as it moves between two data flow components at run time.

Front 406

data warehouse

Back 406

A database specifically structured for query and analysis. A data warehouse typically contains data representing the business history of an organization.

Front 407

Data Warehouse

Back 407

A database specifically structured for query and analysis. A data warehouse typically contains data representing the business history of an organization.

Front 408

database administrator

Back 408

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.

Front 409

database catalog

Back 409

The part of a database that contains the definition of all the objects in the database, as well as the definition of the database.

Front 410

database diagram

Back 410

A graphical representation of any portion of a database schema. It can be either a whole or partial picture of the structure of the database. It includes tables, the columns they contain, and the relationships between the tables.

Front 411

database engine

Back 411

The program module or modules that provide access to a database management system (DBMS).

Front 412

Database Engine Tuning Advisor

Back 412

A tool for tuning the physical database design that helps users to select and create an optimal set of indexes, indexed views, and partitioning.

Front 413

Database Explorer

Back 413

A simple database administration tool that lets the user perform database operations such as creating new tables, querying and modifying existing data, and other database development functions.

Front 414

database file

Back 414

One of the physical files that make up a database.

Front 415

database language

Back 415

The language used for accessing, querying, updating, and managing data in relational database systems.

Front 416

database management system

Back 416

A layer of software between the physical database and the user. The DBMS manages all access to the database.

Front 417

database manager

Back 417

A layer of software between the physical database and the user. The DBMS manages all access to the database.

Front 418

database mirroring

Back 418

Immediately reproducing every update to a read-write database (the principal database) onto a read-only mirror of that database (the mirror database) residing on a separate instance of the database engine (the mirror server). In production environments, the mirror server is on another machine. The mirror database is created by restoring a full backup of the principal database (without recovery).

Front 419

Database Mirroring Monitor

Back 419

A tool used to monitor any subset of the mirrored databases on a server instance.

Front 420

database mirroring partner

Back 420

One in a pair of server instances that act as role-switching partners for a mirrored database.

Front 421

database mirroring partners

Back 421

A pair of server instances that act as role-switching partners for a mirrored database.

Front 422

database project

Back 422

A collection of one or more data connections (a database and the information needed to access that database).

Front 423

database reference

Back 423

A path, expression or filename that resolves to a database.

Front 424

database role

Back 424

A collection of users and groups with the same access to an Analysis Services database.

Front 425

database schema

Back 425

The names of tables, fields, data types, and primary and foreign keys of a database.

Front 426

database script

Back 426

A collection of statements used to create database objects.

Front 427

database snapshot

Back 427

A read-only, static view of a database at the moment of snapshot creation.

Front 428

database structure

Back 428

The names of tables, fields, data types, and primary and foreign keys of a database.

Front 429

Database view

Back 429

A read-only, static snapshot of a source database at the moment of the view's creation.

Front 430

data-definition query

Back 430

An SQL-specific query that contains data definition language (DDL) statements. These statements allow you to create or alter objects in the database.

Front 431

data-driven subscription

Back 431

A subscription that takes generated output for subscription values (for example, a list of employee e-mail addresses).

Front 432

datareader

Back 432

A stream of data that is returned by an ADO.NET query.

Front 433

data-tier application

Back 433

A single unit of management that captures the SQL Server database and instance objects used by a client-server or 3-tier application.

Front 434

data-tier application instance

Back 434

A copy of a DAC deployed on an instance of the Database Engine. There can be multiple DAC instances on the same instance of the Database Engine.

Front 435

data-tier application package

Back 435

An XML manifest that contains all of the objects defined for the DAC; the package gets created when a developer builds a DAC project.

Front 436

date

Back 436

A SQL Server system data type that stores a date value from January 1, 1 A.D., through December 31, 9999

Front 437

DB

Back 437

A collection of data formatted/arranged to allow for easy search and retrieval.

Front 438

DBCS

Back 438

A character set that can use more than one byte to represent a single character. A DBCS includes some characters that consist of 1 byte and some characters that consist of 2 bytes. Languages such as Chinese, Japanese, and Korean use DBCS.

Front 439

DBMS

Back 439

A layer of software between the physical database and the user. The DBMS manages all access to the database.

Front 440

DDL

Back 440

A language that defines all attributes and properties of a database, especially record layouts, field definitions, key fields, file locations, and storage strategy.

Front 441

DDL trigger

Back 441

A special kind of trigger that executes in response to Data Definition Language (DDL) statements.

Front 442

deadlock

Back 442

A situation when two users, each having a lock on one piece of data, attempt to acquire a lock on the other's piece.

Front 443

decision support

Back 443

Systems designed to support the complex analytic analysis required to discover business trends.

Front 444

decision tree

Back 444

A treelike model of data produced by certain data mining methods. Decision trees can be used for prediction.

Front 445

declaration

Back 445

A binding of an identifier to the information that relates to it. For example, to make a declaration of a constant means to bind the name of the constant with its value. Declaration usually occurs in a program's source code; the actual binding can take place at compile time or run time.

Front 446

Declarative Management Framework

Back 446

A policy based system of SQL Server management.

Front 447

Declarative Management Framework Facet

Back 447

A set of logical pre-defined properties that model the behavior or characteristics for certain types of managed targets (such as a database, table, login, view,etc) in policy-based management.

Front 448

declarative referential integrity

Back 448

FOREIGN KEY constraints defined as part of a table definition that enforce proper relationships between tables.

Front 449

dedicated administrator connection

Back 449

A dedicated connection that allows an administrator to connect to a server when the Database Engine will not respond to regular connections.

Front 450

default

Back 450

A value that is automatically used by a program when the user does not specify an alternative. Defaults are built into a program when a value or option must be assumed for the program to function.

Front 451

default database

Back 451

The database the user is connected to immediately after logging in to SQL Server.

Front 452

default instance

Back 452

The instance of SQL Server that uses the same name as the computer name on which it is installed.

Front 453

default language

Back 453

The human language that SQL Server uses for errors and messages if a user does not specify a language.

Front 454

default member

Back 454

The dimension member used in a query when no member is specified for the dimension.

Front 455

default result set

Back 455

The default mode that SQL Server uses to return a result set back to a client.

Front 456

defection

Back 456

The removal of a server from multiserver operations.

Front 457

deferred transaction

Back 457

A transaction that is not committed when the roll forward phase of recovery completes and that cannot be rolled back during database startup because data needed by roll back is offline. This data can reside in either a page or a file.

Front 458

degenerate dimension

Back 458

A relationship between a dimension and a measure group in which the dimension main table is the same as the measure group table.

Front 459

DEK

Back 459

A bit string that is used in conjunction with an encryption algorithm to encrypt and decrypt data.

Front 460

delegated registration model

Back 460

A registration model in which a person other than the certificate subscriber initiates the certificate transaction. The certificate subscriber then completes the transaction by providing a supplied one-time password.

Front 461

DELETE clause

Back 461

A part of a DML Statement that contains the DELETE keyword and associated parameters.

Front 462

delete level

Back 462

In Data Transformation Services, the amount and kind of data to remove from a data warehouse.

Front 463

delimited identifier

Back 463

An object in a database that requires the use of special characters (delimiters) because the object name does not comply with the formatting rules of regular identifiers.

Front 464

delivery channel

Back 464

A pipeline between a distributor and a delivery service.

Front 465

delivery channel type

Back 465

The protocol for a delivery channel, such as Simple Mail Transfer Protocol (SMTP) or File.

Front 466

delivery extension

Back 466

A plug-in that delivers reports to a specific target (for example, e-mail delivery).

Front 467

delivery protocol

Back 467

The set of communication rules used to route notification messages to external delivery systems.

Front 468

denormalize

Back 468

To introduce redundancy into a table to incorporate data from a related table.

Front 469

deploy

Back 469

To build a DAC instance, either directly from a DAC package or from a DAC previously imported to the SQL Server Utility.

Front 470

deployed environment

Back 470

A group of virtual machines located on a team project host group and controlled by Microsoft Test Manager. A deployed environment can be running or stopped.

Front 471

dequeue

Back 471

To remove from a queue.

Front 472

derived column

Back 472

A transformation that creates new column values by applying expressions to transformation input columns.

Front 473

deserialization

Back 473

The process of converting an object from a serial storage format to binary format in the form of an object that applications can use. This happens when the object is retrieved from the cache cluster with the Get client APIs.

Front 474

destination

Back 474

The SSIS data flow component that loads data into data stores or creates in-memory datasets.

Front 475

destination

Back 475

A synchronization provider that provide its current knowledge, accept a list of changes from the source provider, detect any conflicts between that list and its own items, and apply changes to its data store.

Front 476

destination adapter

Back 476

A data flow component that loads data into a data store.

Front 477

destination provider

Back 477

A synchronization provider that provide its current knowledge, accept a list of changes from the source provider, detect any conflicts between that list and its own items, and apply changes to its data store.

Front 478

detect

Back 478

To find something.

Front 479

device type

Back 479

A value from a developer-defined list that specifies the types of devices that a given application will support.

Front 480

diacritic

Back 480

A mark placed over, under, or through a character, usually to indicate a change in phonetic value from the unmarked state.

Front 481

diacritical mark

Back 481

A mark placed over, under, or through a character, usually to indicate a change in phonetic value from the unmarked state.

Front 482

dialect

Back 482

The syntax and general rules used to parse a string or a query statement.

Front 483

diamond-shape relationship

Back 483

A chain of attribute relationships that splits and rejoins but that contains no redundant relationships. For example, Day->Month->Year and Day->Quarter->Year have the same start and end points, but do not have any common relationships.

Front 484

differencer

Back 484

Creates a differencer of the DifferencingService object.

Front 485

differential backup

Back 485

A backup containing only changes made to the database since the preceding data backup on which the differential backup is based.

Front 486

differential base

Back 486

The most recent full backup of all the data in a database or in a subset of the files or filegroups of a database.

Front 487

digest delivery

Back 487

A method of sending notifications that combines multiple notifications within a batch and sends the resulting message to a subscriber.

Front 488

digital certificate

Back 488

A digital document that is commonly used for authentication and to help secure information on a network. A certificate binds a public key to an entity that holds the corresponding private key. Certificates are digitally signed by the certification authority that issues them, and they can be issued for a user, a computer, or a service.

Front 489

dimension

Back 489

A structural attribute of a cube that organizes data into levels. For example, a Geography dimension might include the members Country, Region, State or Province, and City.

Front 490

dimension expression

Back 490

A valid Multidimensional Expressions (MDX) expression that returns a dimension.

Front 491

dimension granularity

Back 491

The lowest level available to a particular dimension in relation to a particular measure group. The "natural" or physical grain is always that of the key that joins the main dimension table to the primary fact table.

Front 492

dimension hierarchy

Back 492

A logical tree structure that organizes the members of a dimension such that each member has one parent member and zero or more child members.

Front 493

dimension level

Back 493

The name of a set of members in a dimension hierarchy such that all members of the set are at the same distance from the root of the hierarchy. For example, a time hierarchy may contain the levels Year, Month, and Day.

Front 494

dimension member

Back 494

A single position or item in a dimension. Dimension members can be user-defined or predefined and can have properties associated with them.

Front 495

dimension member property

Back 495

A characteristic of a dimension member. Dimension member properties can be alphanumeric, Boolean, or Date/Time data types, and can be user-defined or predefined.

Front 496

dimension table

Back 496

A table in a data warehouse whose entries describe data in a fact table.

Front 497

direct connect

Back 497

The state of being connected to a back-end database, so that any changes you make to a database diagram automatically update your database when you save the diagram or selected items in it.

Front 498

direct response mode

Back 498

The default mode in which SQL Server statistics are gathered separately from the SQL Server Statistics display.

Front 499

dirty page

Back 499

A buffer page that contains modifications that have not been written to disk.

Front 500

dirty read

Back 500

A read that contains uncommitted data.

Front 501

disabled index

Back 501

Any index that has been marked as disabled. A disabled index is unavailable for use by the database engine. The index definition of a disabled index remains in the system catalog with no underlying index data.

Front 502

discrete signal

Back 502

A time series consisting of a sequence of quantities, that is a time series that is a function over a domain of discrete integers.

Front 503

discretize

Back 503

To put values of a continuous set of data into groups so that there are a discrete number of possible states.

Front 504

discretized column

Back 504

A column that represents finite, counted data

Front 505

distinct count measure

Back 505

A measure commonly used to determine for each member of a dimension how many distinct, lowest-level members of another dimension share rows in the fact table.

Front 506

distributed partitioned view

Back 506

A view that joins horizontally partitioned data from a set of member tables across more than one server, making the data appear as if from one table.

Front 507

distributed query

Back 507

A single query that accesses data from multiple data sources.

Front 508

distributed transaction

Back 508

A transaction that spans multiple data sources.

Front 509

distribution cleanup agent

Back 509

A scheduled job that runs under SQL Server Agent. After all Subscribers have received a transaction, the agent removes the transaction from the distribution database. It also cleans up snapshot files from the file system after entries corresponding to those files have been removed from the distribution database.

Front 510

distribution database

Back 510

A database on the Distributor that stores data for replication including transactions, snapshot jobs, synchronization status, and replication history information.

Front 511

distribution retention period

Back 511

In transactional replication, the amount of time transactions are stored in the distribution database.

Front 512

distributor

Back 512

A database instance that acts as a store for replication-specific data associated with one or more Publishers.

Front 513

DMF

Back 513

One of a set of built-in functions that returns server state information about values, objects, and settings in SQL Server.

Front 514

DML

Back 514

The subset of SQL statements that is used to retrieve and manipulate data. DML statements typically start with SELECT INSERT UPDATE or DELETE.

Front 515

DML trigger

Back 515

A stored procedure that executes when data in a specified table is modified.

Front 516

DMV

Back 516

A set of built-in views that return server state information about values, objects, and settings in SQL Server.

Front 517

DMX

Back 517

In Analysis Services, a statement that performs mining tasks programmatically.

Front 518

domain

Back 518

The set of possible values that you can specify for an independent variable in a function, or for a database attribute.

Front 519

domain

Back 519

A collection of computers in a networked environment that share a common database, directory database, or tree. A domain is administered as a unit with common rules and procedures, which can include security policies, and each domain has a unique name.

Front 520

domain context

Back 520

A client-side representation of a domain service.

Front 521

domain integrity

Back 521

The validity of entries for a specific column of data.

Front 522

domain operation

Back 522

A method on a domain service that is exposed to a client application. It enables client applications to perform an action on the entity such as, query, update, insert, or delete records.

Front 523

domain service

Back 523

A service that encapsulates the business logic of an application. It exposes a set of related domain operations in a service layer.

Front 524

dormant session

Back 524

Session in pre-login state. Sessions can be initiated or ended to modify their state, but they generally remain in either a "sleep/idle" state, such as when the session has been initiated and is open at the server for client use; or a "dormant" state, such as when the session has been ended and the session is not currently available at the server for client use.

Front 525

double byte character set

Back 525

A character set that can use more than one byte to represent a single character. A DBCS includes some characters that consist of 1 byte and some characters that consist of 2 bytes. Languages such as Chinese, Japanese, and Korean use DBCS.

Front 526

double-byte character set

Back 526

A character set that can use more than one byte to represent a single character. A DBCS includes some characters that consist of 1 byte and some characters that consist of 2 bytes. Languages such as Chinese, Japanese, and Korean use DBCS.

Front 527

down

Back 527

Not functioning, in reference to computers, printers, communications lines on networks, and other such hardware.

Front 528

download-only article

Back 528

An article in a merge publication that can be updated only at the Publisher or at a Subscriber that uses a server subscription.

Front 529

DPM Client

Back 529

The Data Protection Manager (DPM) Client enables the user to protect and recover their data as per the company protection policy configured by their backup administrator.

Front 530

DPM engine

Back 530

A policy-driven engine that DPM uses to protect and recover data.

Front 531

DPM Management Shell

Back 531

The command shell, based on Windows PowerShell (Powershell.exe), that makes available the cmdlets that perform functions in Data Protection Manager.

Front 532

DPM Online

Back 532

A feature that provides an online remote backup, both for securely storing data offsite for long durations and for disaster recovery (DR).

Front 533

DPM Online account

Back 533

A user account that DPM uses to start the DPM Online service.

Front 534

DPM Online cache

Back 534

A cache volume required by DPM Online on which the DPM server stores information for faster backup and recovery from DPM Online.

Front 535

DPM Online protection

Back 535

The process of using DPM online to protect data from loss or corruption by creating and maintaining replicas and recovery points of the data online.

Front 536

DPM Online protection group

Back 536

A collection of data sources that share the same DPM Online protection configuration.

Front 537

DPM Online recovery

Back 537

The process by which an administrator recovers previous versions of protected data from online recovery points on an internet-connected DPM server.

Front 538

DPM Online recovery point

Back 538

The date and time of a previous version of a data source that is available from DPM Online.

Front 539

DPM Online replica

Back 539

A complete copy of an online-protected data source on DPM Online. Each member of an online protection group on the DPM server is associated with a DPM Online replica.

Front 540

DPM role

Back 540

The grouping of users, objects, and permissions that is used by DPM administrators to manage DPM features that are used by end users.

Front 541

DPM Self-Service Recovery Configuration Tool

Back 541

A tool that enables DPM administrators to authorize end users to perform self-service recovery of data by creating and managing DPM roles (grouping of users, objects, and permissions).

Front 542

DPM Self-Service Recovery Tool

Back 542

A tool that is used by end users to recover backups from DPM, without any action required from the DPM administrator.

Front 543

DPM Self-Service Tool for SQL Server

Back 543

A tool for SQL Server that enables backup administrators to authorize end users to recover backups of SQL Server databases from DPM, without further action from the backup administrator.

Front 544

DPM SRT

Back 544

Software provided with DPM to facilitate a Windows Server 2003 bare metal recovery for the DPM server and the computers that DPM protects.

Front 545

DPM SST for SQL Server

Back 545

A tool for SQL Server that enables backup administrators to authorize end users to recover backups of SQL Server databases from DPM, without further action from the backup administrator.

Front 546

DPM System Recovery Tool

Back 546

Software provided with DPM to facilitate a Windows Server 2003 bare metal recovery for the DPM server and the computers that DPM protects.

Front 547

DQS knowledge base

Back 547

A repository of metadata that is used by Data Quality Services to improve the quality of data. This metadata is created either by the user interactively or by the Data Quality Services platform in an automated knowledge discovery process.

Front 548

drillthrough

Back 548

In Analysis Services, a technique to retrieve the detailed data from which the data in a cube cell was summarized.

Front 549

drill-through report

Back 549

A secondary report that is displayed when a user clicks an item in a report. Detailed data is displayed in the same report.

Front 550

drop-down list

Back 550

A list that can be opened to reveal all choices for a given field.

Front 551

DSN

Back 551

The collection of information used to connect an application to a particular ODBC database.

Front 552

DSN-less connection

Back 552

A type of data connection that is created based on information in a data source name (DSN), but is stored as part of a project or application.

Front 553

dump

Back 553

A duplicate of a program, a disk, or data, made either for archiving purposes or for safeguarding files.

Front 554

dump device

Back 554

A tape or disk drive containing a backup medium.

Front 555

dynamic cursor

Back 555

A cursor that can reflect data modifications made to the underlying data while the cursor is open.

Front 556

dynamic filter

Back 556

A row filter available with merge replication that allows you to restrict the data replicated to a Subscriber based on a system function or user-defined function (for example: SUSER_SNAME()).

Front 557

dynamic locking

Back 557

The process used by SQL Server to determine the most cost-effective locks to use at any one time.

Front 558

dynamic management function

Back 558

One of a set of built-in functions that returns server state information about values, objects, and settings in SQL Server.

Front 559

dynamic management view

Back 559

A set of built-in views that return server state information about values, objects, and settings in SQL Server.

Front 560

dynamic recovery

Back 560

The process that detects and/or attempts to correct software failure or loss of data integrity within a relational database management system (RDBMS).

Front 561

dynamic routing

Back 561

Routing that adjusts automatically to the current conditions of a network. Dynamic routing typically uses one of several dynamic-routing protocols such as Routing Information Protocol (RIP) and Border Gateway Protocol (BGP). Compare static routing.

Front 562

dynamic snapshot

Back 562

In merge replication, a snapshot that includes only the data from a single partition.

Front 563

eager loading

Back 563

A pattern of loading where a specific set of related objects are loaded along with the objects that were explicitly requested in the query.

Front 564

edge event

Back 564

An event whose event payload is valid for a given interval; however, only the start time is known upon arrival to the CEP server. The valid end time of the event is provided later in a separate edge event.

Front 565

effective policy

Back 565

The set of enabled policies for a target.

Front 566

e-mail

Back 566

The exchange of text messages and computer files over a communications network, such as a local area network or the Internet.

Front 567

encryption

Back 567

The process of converting readable data (plaintext) into a coded form (ciphertext) to prevent it from being read by an unauthorized party.

Front 568

encryption key

Back 568

A bit string that is used in conjunction with an encryption algorithm to encrypt and decrypt data.

Front 569

end cap

Back 569

For paths that contain unconnected ends, such as lines, the end of a stroke. You can change the way the stroke looks at each end by applying one of four end cap styles: flat cap, round cap, square cap, and triangle cap.

Front 570

endpoint

Back 570

A synchronization provider and its associated replica.

Front 571

endpoint mapper

Back 571

A service on a remote procedure call (RPC) server that maintains a database of dynamic endpoints and allows clients to map an interface/object UUID pair to a local dynamic endpoint.

Front 572

enqueue

Back 572

To place (an item) in a queue.

Front 573

enroll

Back 573

To add an instance of SQL Server to the set of SQL Server instances managed by a utility control point.

Front 574

enrollment

Back 574

The process of requesting, receiving, and installing a certificate.

Front 575

Enrollment Agent

Back 575

A user account used to request smart card certificates on behalf of another user account. A specific certificate template is applied to an Enrollment Agent.

Front 576

enterprise license

Back 576

A license that authorizes protection of both file and application resources on a single computer.

Front 577

entity

Back 577

In Reporting Services, an entity is a logical collection of model items, including source fields, roles, folders, and expressions, presented in familiar business terms.

Front 578

entity integrity

Back 578

A state in which every row of every table can be uniquely identified.

Front 579

envelopes formula

Back 579

A financial formula that calculates "envelopes" above and below a moving average using a specified percentage as the shift. The envelopes indicator is used to create signals for buying and selling. You can specify the percentage the formula uses to calculate the envelopes.

Front 580

equijoin

Back 580

A join in which the values in the columns being joined are compared for equality, and all columns are included in the results.

Front 581

equirectangular projection

Back 581

In a map report item, a very simple equidistant cylindrical projection in which the horizontal coordinate is the longitude and the vertical coordinate is the latitude.

Front 582

error handling

Back 582

The process of dealing with errors (or exceptions) as they arise during the running of a program. Some programming languages, such as C++, Ada, and Eiffel, have features that aid in error handling.

Front 583

error log

Back 583

A file that lists errors that were encountered during an operation.

Front 584

error state number

Back 584

A number associated with SQL Server messages that helps Microsoft support engineers find the specific code location that issued the message.

Front 585

ETL

Back 585

The act of extracting data from various sources, transforming data to consistent types, and loading the transformed data for use by applications.

Front 586

ETW-based log sink

Back 586

A means of capturing trace events on the cache client or cache host with the Event Tracing for Windows (ETW) framework inside Windows.

Front 587

event

Back 587

The basic unit of data processed by the StreamInsight server. Each event contains a header that defines the event kind and the temporal properties of the event. An event (except the CTI event) typically contains an event payload, which is a .NET data structure that contains the data associated with the event.

Front 588

event

Back 588

Any significant occurrence in the system or an application that requires a user to be notified or an entry to be added to a log.

Front 589

event category

Back 589

In SQL Trace, a grouping of similar and logically related event classes.

Front 590

event chronicle

Back 590

A table that stores event state information.

Front 591

event chronicle rule

Back 591

One or more Transact-SQL statements that manage the data in the event chronicle.

Front 592

event class

Back 592

In SQL Trace, a collection of properties that define an event.

Front 593

event classification

Back 593

A means of differentiating types of events that occur on the cache client and cache host. The Windows Server AppFabric log sinks follow the classification established with the System.Diagnostics.TraceLevel enumeration.

Front 594

event collection stored procedures

Back 594

System-generated stored procedures that an application can call to submit events to the event table in the application database.

Front 595

event handler

Back 595

A software routine that executes in response to an event.

Front 596

event header

Back 596

The portion of an event that defines the temporal properties of the event and the event kind. Temporal properties include a valid start time and end time associated with the event.

Front 597

event kind

Back 597

Event metadata that defines the event type.

Front 598

event model

Back 598

The event metadata that defines the temporal characteristics (shape) of the event.

Front 599

event notification

Back 599

A special kind of trigger that sends information about database events to a service broker.

Front 600

event payload

Back 600

The data portion of an event in which the data fields are defined as CLR (common language runtime) types. An event payload is a typed structure.

Front 601

event provider

Back 601

A provider that monitors a source of events and notifies the event table when events occur.

Front 602

event source

Back 602

The point of origin of an event.

Front 603

event table

Back 603

A table in the application database that stores event data.

Front 604

Event Tracing for Windows (ETW)-based log sink

Back 604

A means of capturing trace events on the cache client or cache host with the Event Tracing for Windows (ETW) framework inside Windows.

Front 605

Everyone

Back 605

A type of user account.

Front 606

eviction

Back 606

The physical removal of a cached object from the memory of the cache host or hosts that it is stored on. This is typically done to keep the memory usage of the cache host service in check.

Front 607

exclusive lock

Back 607

A lock that prevents any other transaction from acquiring a lock on a resource until the original lock on the resource is released at the end of the transaction.

Front 608

execute

Back 608

To perform an instruction.

Front 609

execution tree

Back 609

The path of data in the data flow of a SQL Server 2005 Integration Services package from sources through transformations to destinations.

Front 610

exit module

Back 610

A Certificate Services component that performs post-processing after a certificate is issued, such as the publication of an issued certificate to Active Directory.

Front 611

expiration

Back 611

The point at which an object has exceeded the cache time-out value. When an object expires, it is evicted.

Front 612

explicit cap

Back 612

An explicit hierarchy used as the top level of a derived hierarchy structure.

Front 613

explicit hierarchy

Back 613

In Master Data Services, a hierarchy that uses consolidated members to group other consolidated and leaf members.

Front 614

explicit loading

Back 614

A pattern of loading where related objects are not loaded until explicitly requested by using the Load method on a navigation property.

Front 615

explicit transaction

Back 615

A group of SQL statements enclosed within transaction delimiters that define both the start and end of the transaction.

Front 616

exploded pie

Back 616

A pie chart that displays the contribution of each value to a total while emphasizing individual values, by showing each slice of the pie as "pulled out," or separate, from the whole.

Front 617

exploded pie chart

Back 617

A pie chart that displays the contribution of each value to a total while emphasizing individual values, by showing each slice of the pie as "pulled out," or separate, from the whole.

Front 618

exponential moving average

Back 618

A moving average of data that gives more weight to the more recent data in the period and less weight to the older data in the period. The formula applies weighting factors which decrease exponentially. The weighting for each older data point decreases exponentially, giving much more importance to recent observations while still not discarding older observations entirely.

Front 619

export format

Back 619

UI text for subscriptions and HTML viewer. Corresponds to rendering extensions.

Front 620

expression

Back 620

Any combination of operators, constants, literal values, functions, and names of fields (columns), controls, and properties that evaluates to a single value.

Front 621

expression host assembly

Back 621

All expressions found within a report are that are compiled into an assembly. The expression host assembly is stored as a part of the compiled report.

Front 622

extended permission

Back 622

A permission that is specific to an object added to the standard Active Directory object schema. The permission associated with the new object extends the existing default permission set.

Front 623

Extended property

Back 623

User-defined text (descriptive or instructional including input masks and formatting rules) specific to a database or database object. The text is stored in the database as a property of the database or object.

Front 624

Extended Protection for Authentication

Back 624

A security feature that helps protect against man-in-the-middle (MITM) attacks.

Front 625

extended stored procedure

Back 625

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.

Front 626

Extensible Stylesheet Language

Back 626

An XML vocabulary that is used to transform XML data to another form, such as HTML, by means of a style sheet that defines presentation rules.

Front 627

Extensible Stylesheet Language Transformation

Back 627

A declarative, XML-based language that is used to present or transform XML data.

Front 628

Extensible Stylesheet Language Transformations

Back 628

A declarative, XML-based language that is used to present or transform XML data.

Front 629

extent

Back 629

On a disk or other direct-access storage device, a continuous block of storage space reserved by the operating system for a particular file or program.

Front 630

external delivery system

Back 630

A system, such as Microsoft Exchange Server, that delivers formatted notifications to destination devices.

Front 631

extract

Back 631

To build a DAC package file that contains the definitions of all the objects in an existing database, as well as instance objects that are associated with the database.

Front 632

extraction, transformation, and loading

Back 632

The act of extracting data from various sources, transforming data to consistent types, and loading the transformed data for use by applications.

Front 633

facet

Back 633

A set of logical pre-defined properties that model the behavior or characteristics for certain types of managed targets (such as a database, table, login, view,etc) in policy-based management.

Front 634

Facet

Back 634

A set of logical pre-defined properties that model the behavior or characteristics for certain types of managed targets (such as a database, table, login, view,etc) in policy-based management.

Front 635

facet property

Back 635

A predefined property that applies to a specific facet in Policy-Based Management.

Front 636

fact

Back 636

A row in a fact table in a data warehouse. A fact contains values that define a data event such as a sales transaction.

Front 637

fact dimension

Back 637

A relationship between a dimension and a measure group in which the dimension main table is the same as the measure group table.

Front 638

fact table

Back 638

A central table in a data warehouse schema that contains numerical measures and keys relating facts to dimension tables.

Front 639

factory method

Back 639

A method, usually defined as static, whose purpose is to return an instance of a class.

Front 640

fail over

Back 640

To switch processing from a failed component to its backup component.

Front 641

failed transaction

Back 641

A transaction that encountered an error and was not able to complete.

Front 642

failover cluster

Back 642

A group of servers that are in one location and that are networked together for the purpose of providing live backup in case one of the servers fails.

Front 643

failover clustering

Back 643

A high availability process in which an instance of an application or a service, running over one machine, can fail-over onto another machine in the failover cluster in the case the first one fails.

Front 644

failover partner

Back 644

The server to use if the connection to the primary server fails. The failover partner can be obtained by two methods. In the first method, SQL Native Client caches the failover partner server name when connecting to the primary server. In the second method, the failover partner is explicitly specified in the connection string.

Front 645

fail-safe operator

Back 645

A user who receives the alert if the designated operator cannot be reached.

Front 646

failure notification

Back 646

A type of cache notification triggered when the cache client misses one or more cache notifications.

Front 647

fatal error

Back 647

An error that causes the system or a program to fail abruptly with no hope of recovery. An example of a fatal error is an uncaught exception that cannot be handled.

Front 648

federated database servers

Back 648

A set of linked servers that shares the processing load of data by hosting partitions of a distributed partitioned view.

Front 649

feed consumer

Back 649

A software component that extracts items from a FeedSync feed and applies them to a destination replica by using a synchronization provider.

Front 650

fiber

Back 650

A Windows NT lightweight thread scheduled within a single OS thread.

Front 651

fiber mode

Back 651

A situation where an instance of SQL Server allocates one Windows thread per SQL scheduler, and then allocates one fiber per worker thread, up to the value set in the max worker threads option.

Front 652

field

Back 652

An area in a window or record that stores a single data value.

Front 653

field length

Back 653

In bulk copy, the maximum number of characters needed to represent a data item in a bulk copy character format data file.

Front 654

field marshaller

Back 654

A SQL Server feature that handles marshaling for fields.

Front 655

field terminator

Back 655

In bulk copy, one or more characters marking the end of a field or row, separating one field or row in the data file from the next.

Front 656

file backup

Back 656

A backup of all the data in one or more files or filegroups.

Front 657

file differential backup

Back 657

A backup of one or more files containing only changes made to each file since its most recent file backup. A file differential backup requires a full file backup as a base.

Front 658

file DSN

Back 658

file Data Source Names. File-based data sources shared among all users with the same drivers installed. These data sources are not dedicated to a user or local to a computer.

Front 659

file mapping

Back 659

The association of a file's contents with a portion of the virtual address space of a process.

Front 660

file restore

Back 660

An operation that restores one or more files of a database.

Front 661

file rollover

Back 661

An option that causes SQL Server to close the current file and create a new file when the maximum file size is reached.

Front 662

filegroup

Back 662

A named collection of one or more data files that forms a single unit of data allocation or for administration of a database.

Front 663

file-mapping object

Back 663

An object that maintains the association of a file's contents with a portion of the virtual address space of a process.

Front 664

fill factor

Back 664

An attribute of an index that defines how full the SQL Server Database Engine should make each page of the index.

Front 665

filter forgotten knowledge

Back 665

The knowledge that is used as the starting point for filter tracking. A filter-tracking replica can save storage space by removing ghosts and advancing the filter forgotten knowledge to contain the highest version of the ghosts that have been removed.

Front 666

filter key

Back 666

A 4-byte value that maps to a filter in a filter key map.

Front 667

filtered replica

Back 667

A replica that stores item data only for items that are in a filter, such as a media storage replica that stores only songs that are rated as three stars or better.

Front 668

filter-tracking replica

Back 668

A replica that can identify which items are in a filter and which have moved in or out of the filter recently.

Front 669

fine-grained lock

Back 669

A lock that applies to a small amount of code or data.

Front 670

fit

Back 670

One of the criteria used for evaluating the success of a data mining algorithm. Fit is typically represented as a value between 0 and 1, and is calculated by taking the covariance between the predicted and actual values of evaluated cases and dividing by the standard deviations of the same predicted and actual values.

Front 671

fixed database role

Back 671

A predefined role that exists in each database. The scope of the role is limited to the database in which it is defined.

Front 672

fixed server role

Back 672

A predefined role that exists at the server level. The scope of the role is limited to the SQL Server instance in which it is defined.

Front 673

FK

Back 673

A key in a database table that comes from another table (also know as the "referenced table") and whose values match the primary key (PK) or unique key in the referenced table.

Front 674

flat file

Back 674

A file consisting of records of a single record type in which there is no embedded structure information that governs relationships between records.

Front 675

flatten

Back 675

To convert a nested structure into a flat structure.

Front 676

flattened interface

Back 676

An interface created to combine members of multiple interfaces.

Front 677

flattened rowset

Back 677

A multidimensional data set presented as a two-dimensional rowset in which unique combinations of elements of multiple dimensions are combined on an axis.

Front 678

flexible ID

Back 678

An identifier that is assigned to various synchronization entities, such as replicas. The identifier can be of fixed or variable length.

Front 679

flexible identifier

Back 679

An identifier that is assigned to various synchronization entities, such as replicas. The identifier can be of fixed or variable length.

Front 680

fold count

Back 680

A value that represents the number of partitions that will be created within the original data set.

Front 681

folder hierarchy

Back 681

A bounded namespace that uniquely identifies all reports, folders, shared data source items, and resources that are stored in and managed by a report server.

Front 682

forced service

Back 682

In a database mirroring session, a failover initiated by the database owner upon the failure of the principal server that transfers service to the mirror database while it is in an unknown state. Data may be lost.

Front 683

foreign key

Back 683

A key in a database table that comes from another table (also know as the "referenced table") and whose values match the primary key (PK) or unique key in the referenced table.

Front 684

foreign key association

Back 684

An association between entities that is managed through foreign key properties.

Front 685

foreign table

Back 685

A table that contains a foreign key.

Front 686

format file

Back 686

A file containing meta information (such as data type and column size) that is used to interpret data when being read from or written to a data file.

Front 687

forward-only cursor

Back 687

A cursor that cannot be scrolled; rows can be read only in sequence from the first row to the last row.

Front 688

free-form language

Back 688

A language whose syntax is not constrained by the position of characters on a line. C and Pascal are free-form languages; FORTRAN is not.

Front 689

full backup

Back 689

A backup of an entire database.

Front 690

full differential backup

Back 690

A backup of all files in the database, containing only changes made to the database since the most recent full backup. A full differential backup requires a full backup as a base.

Front 691

full outer join

Back 691

A type of outer join in which all rows in all joined tables are included, whether they are matched or not. For example, a full outer join between titles and publishers shows all titles and all publishers, even those that have no match.

Front 692

full recovery model

Back 692

A database recovery mode that fully logs all transactions and retains all the log records until after they are backed up. The database can be recovered to the point of failure if the tail of the log is backed up after the failure. All forms of recovery are supported.

Front 693

full-text catalog

Back 693

A collection of full-text index components and other files that are organized in a specific directory structure and contain the data that is needed to perform queries.

Front 694

full-text enabling

Back 694

The process of allowing full-text querying to occur on the current database.

Front 695

full-text query

Back 695

As a SELECT statement, a query that searches for words, phrases, or multiple forms of a word or phrase in the character-based columns (of char, varchar, text, ntext, nchar, or nvarchar data types). The SELECT statement returns those rows meeting the search criteria.

Front 696

full-text search

Back 696

A search for one or more documents, records, or strings based on all of the actual text data rather than on an index containing a limited set of keywords.

Front 697

Full-Text service

Back 697

The SQL Server component that performs the full-text querying.

Front 698

full-width character

Back 698

In a double-byte character set, a character that is represented by 2 bytes and typically has a half-width variant.

Front 699

function

Back 699

A piece of code that operates as a single logical unit. A function is called by name, accepts optional input parameters, and returns a status and optional output parameters. Many programming languages support functions.

Front 700

fuzzy grouping

Back 700

In Integration Services, a data cleaning methodology that examines values in a dataset and identifies groups of related data rows and the one data row that is the canonical representation of the group.

Front 701

fuzzy matching

Back 701

In Integration Services, a lookup methodology that uses an approximate matching algorithm to locate similar data values in a reference table.

Front 702

GAC

Back 702

A computer-wide code cache that stores assemblies specifically installed to be shared by many applications on the computer.

Front 703

gap depth

Back 703

A measure that specifies the distance between data series that are displayed along distinct rows, as a result of clustering.

Front 704

garbage collection

Back 704

A process for automatic recovery of heap memory. Blocks of memory that had been allocated but are no longer in use are freed, and blocks of memory still in use may be moved to consolidate the free memory into larger blocks.

Front 705

garbage collector

Back 705

The part of the operating system that performs garbage collection.

Front 706

gated link

Back 706

A protected link between two or more objects. During execution, permissions are not checked across the object relationship once it has been established and credentials don't have to be checked several times. This type of link is useful when it is not appropriate or manageable to give permissions to many dependent objects.

Front 707

gather-write operation

Back 707

A performance optimization where the Database Engine collects multiple modified data pages into a single write operation.

Front 708

GC

Back 708

A process for automatic recovery of heap memory. Blocks of memory that had been allocated but are no longer in use are freed, and blocks of memory still in use may be moved to consolidate the free memory into larger blocks.

Front 709

generated code

Back 709

Code that is automatically generated for the client project based on operations and entities exposed in the middle tier when a RIA Services link exists between the server and client projects.

Front 710

generator

Back 710

The component of Notification Services that matches events to subscriptions and produces notifications.

Front 711

geographic data

Back 711

A type of spatial data that stores ellipsoidal (round-earth) data, such as GPS latitude and longitude coordinates.

Front 712

geometric data

Back 712

A type of spatial data that supports planar, or Euclidean (flat-earth), data.

Front 713

ghost

Back 713

An item or change unit in a filtered replica that was in the filter and has moved out.

Front 714

ghost record

Back 714

Row in the leaf level of an index that has been marked for deletion, but has not yet been deleted by the database engine.

Front 715

ghost row

Back 715

Row in the leaf level of an index that has been marked for deletion, but has not yet been deleted by the database engine.

Front 716

global assembly cache

Back 716

A computer-wide code cache that stores assemblies specifically installed to be shared by many applications on the computer.

Front 717

global default

Back 717

A default that is defined for a specific database and is shared by columns of different tables.

Front 718

global ID

Back 718

A unique identifier that is assigned to a data item. The identifier must be unique across all clients. A global identifier is a flexible identifier and so can be any format, but it is typically a GUID and an 8-byte prefix.

Front 719

global identifier

Back 719

A unique identifier that is assigned to a data item. The identifier must be unique across all clients. A global identifier is a flexible identifier and so can be any format, but it is typically a GUID and an 8-byte prefix.

Front 720

global rule

Back 720

A rule that is defined for a specific database and is shared by columns of different tables.

Front 721

global subscription

Back 721

A subscription to a merge publication with an assigned priority value used for conflict detection and resolution.

Front 722

globalization

Back 722

The process of designing and developing a software product to function in multiple locales. Globalization involves identifying the locales that must be supported, designing features that support those locales, and writing code that functions equally well in any of the supported locales.

Front 723

granularity

Back 723

A description, from "coarse" to "fine", of a computer activity or feature (such as screen resolution, searching and sorting, or time slice allocation) in terms of the size of the units it handles (pixels, sets of data, or time slices). The larger the pieces, the coarser the granularity.

Front 724

granularity attribute

Back 724

The single attribute is used to specify the level of granularity for a given dimension in relation to a given measure group.

Front 725

graphical query designer

Back 725

A query designer provided by the Reporting Services that allows the user to interactively build a query and view the results for data source types SQL Server, Oracle, OLE DB, and ODBC.

Front 726

graphics primitive

Back 726

A basic shape (a point, a line, circle, curve, or polygon) that a graphics adapter can manipulate as a discrete entity.

Front 727

group

Back 727

A collection of users, computers, contacts, and other groups that is used as security or as e-mail distribution collections. Distribution groups are used only for e-mail. Security groups are used both to grant access to resources and as e-mail distribution lists.

Front 728

grouping

Back 728

A set of data that is grouped together in a report.

Front 729

half-width character

Back 729

In a double-byte character set, a character that is represented by one byte and typically has a full-width variant.

Front 730

hard disk

Back 730

An inflexible platter coated with material in which data can be recorded magnetically with read/write heads.

Front 731

hard page-break renderer

Back 731

A rendering extension that maintains the report layout and formatting so that the resulting file is optimized for a consistent printing experience, or to view the report online in a book format.

Front 732

hard-coding

Back 732

Basing numeric constants on the assumed length of a string; assumptions about language or culture-specific matters fixed in the code - e.g., string length, date formats, etc.

Front 733

hard-coding

Back 733

The process of putting string or character literals in the main body of code, instead of in external resource files.

Front 734

hardware security module

Back 734

A secure device that provides cryptographic capabilities, typically by providing private keys used in Public-key cryptography.

Front 735

hardware token

Back 735

A secure device that provides cryptographic capabilities, typically by providing private keys used in Public-key cryptography.

Front 736

hash partitioning

Back 736

A way of partitioning a table or index by allowing SQL Server to apply an internal hash algorithm to spread rows across partitions based on the number of partitions specified and the values of one or more partitioning columns.

Front 737

heat map

Back 737

A type of map presentation where the intensity of color for each polygon corresponds to the related analytical data. For example, low values in a range appear as blue (cold) and high values as red (hot).

Front 738

helpdesk

Back 738

An individual or team of support professionals that provide technical assistance for an organization's network, hardware devices, and software.

Front 739

heterogeneous data

Back 739

Data stored in multiple formats.

Front 740

hierarchy tree

Back 740

A structure in which elements are related to each other hierarchically.

Front 741

high availability

Back 741

The ability of a system or device to be usable when it is needed. When expressed as a percentage, high availability is the actual service time divided by the required service time. Although high availability does not guarantee that a system will have no downtime, a network often is considered highly available if it achieves 99.999 percent network uptime.

Front 742

high availability

Back 742

A Windows Server AppFabric feature that supports continuous availability of cached data by storing copies of that data on multiple cache hosts.

Front 743

high watermark

Back 743

A memory consumption threshold on each cache host that specifies when objects are evicted out of memory, regardless of whether they have expired or not, until memory consumption goes back down to the low watermark.

Front 744

high whisker

Back 744

The highest value that is not an outlier on a box plot chart.

Front 745

hint

Back 745

An option or strategy specified for enforcement by the SQL Server query processor on SELECT, INSERT, UPDATE, or DELETE statements. The hint overrides any execution plan the query optimizer might select for a query.

Front 746

history

Back 746

A list of the user's actions within a program, such as commands entered in an operating system shell, menus passed through using Gopher, or links followed using a Web browser.

Front 747

holdability

Back 747

Refers to the possibility of leaving result sets open ("on hold") that have been processed and are normally closed after this. For instance: "SQL Server supports holdability at the connection level only."

Front 748

holdout

Back 748

A percentage of training data that is reserved for use in measuring the accuracy of the structure of the data mining model.

Front 749

holdout data

Back 749

A percentage of training data that is reserved for use in measuring the accuracy of the structure of the data mining model.

Front 750

holdout store

Back 750

The data mining structure that is used to cache the holdout data. It contains references to the holdout data.

Front 751

Home

Back 751

Root folder in report server folder namespace.

Front 752

home page

Back 752

A document that serves as a starting point in a hypertext system. On the World Wide Web, an entry page for a set of Web pages and other files in a Web site. The home page is displayed by default when a visitor navigates to the site using a Web browser.

Front 753

homogeneous data

Back 753

Data that comes from multiple data sources that are all managed by the same software.

Front 754

hop

Back 754

In data communications, one segment of the path between routers on a geographically dispersed network.

Front 755

hopping window

Back 755

A type of window in which consecutive windows "hop" forward in time by a fixed period. The window is defined by two time spans: the period P and the window length L. For every P time unit a new window of size L is created.

Front 756

horizontal partitioning

Back 756

To segment a single table into multiple tables based on selected rows.

Front 757

hot standby

Back 757

A standby server that can support rapid failover without a loss of data from committed transactions.

Front 758

hot standby server

Back 758

A standby server that can support rapid failover without a loss of data from committed transactions.

Front 759

HSM

Back 759

A secure device that provides cryptographic capabilities, typically by providing private keys used in Public-key cryptography.

Front 760

HTML

Back 760

An application of the Standard Generalized Markup Language that uses tags to mark elements, such as text and graphics, in a document to indicate how Web browsers should display these elements to the user and should respond to user actions.

Front 761

HTML Viewer

Back 761

UI component consisting of a report toolbar and other navigation elements used to work with a report.

Front 762

hybrid OLAP

Back 762

A storage mode that uses a combination of multidimensional data structures and relational database tables to store multidimensional data.

Front 763

Hypertext Markup Language

Back 763

An application of the Standard Generalized Markup Language that uses tags to mark elements, such as text and graphics, in a document to indicate how Web browsers should display these elements to the user and should respond to user actions.

Front 764

identifying field

Back 764

A field or group of fields that identify an entity as a unique object.

Front 765

identifying relationship

Back 765

A relationship where the primary key of the principal entity is part of the primary key of the dependent entity. In this kind of relationship, the dependent entity cannot exist without the principal entity.

Front 766

identity column

Back 766

A column in a table that has been assigned the identity property.

Front 767

identity property

Back 767

A property that generates values that uniquely identify each row in a table.

Front 768

ideograph

Back 768

A character in an Asian writing system that represents a concept or an idea, but not a particular word or pronunciation.

Front 769

ideographic character

Back 769

A character in an Asian writing system that represents a concept or an idea, but not a particular word or pronunciation.

Front 770

IEC

Back 770

One of two international standards bodies responsible for developing international data communications standards. The International Electrotechnical Commission (IEC) works closely with the International Organization for Standardization (ISO) to define standards of computing. They jointly published the ISO/IEC SQL-92 standard for SQL.

Front 771

immediate updating subscription

Back 771

A subscription to a transactional publication for which the user is able to make data modifications at the Subscriber. The data modifications are then immediately propagated to the Publisher using the two-phase commit protocol (2PC).

Front 772

implicit cursor conversion

Back 772

The return of a different type of cursor than the user had declared.

Front 773

implicit transaction

Back 773

A connection option in which each SQL statement executed by the connection is considered a separate transaction.

Front 774

implied permission

Back 774

Permission to perform an activity specific to a role.

Front 775

inactive data source

Back 775

A data source that has been backed up on the DPM server but is no longer being actively protected.

Front 776

included column index

Back 776

A nonclustered index containing both key and nonkey columns.

Front 777

incoming message

Back 777

A message that has been sent across one or more messaging systems. It may have been sent only to you or to many other recipients. Incoming messages are placed in a receive folder designated to hold messages of a particular class. You can set up a different receive folder for each message class that you handle or use one folder for all of the classes.

Front 778

incremental update

Back 778

The set of operations that either adds new members to an existing cube or dimension, or adds new data to a partition.

Front 779

independent association

Back 779

An association between entities that is represented and tracked by an independent object.

Front 780

Index Allocation Map

Back 780

A page that maps the extents in a 4-GB part of a database file that is used by an allocation unit.

Front 781

index page

Back 781

A database page containing index rows.

Front 782

indexed view

Back 782

A view with a unique clustered index applied on it to improve the performance of some types of queries.

Front 783

inference attack

Back 783

A type of security threat in which a malicious user is able to derive the value of data without actually accessing it, for example by monitoring the response time to a query.

Front 784

information model

Back 784

An object-oriented schema that defines metadata constructs used to specify the structure and behavior of an application, process, component, or software artifact.

Front 785

information technology

Back 785

The formal name for a company's data processing department.

Front 786

initial snapshot

Back 786

Files that include schema and data, constraints, extended properties, indexes, triggers, and system tables that are necessary for replication.

Front 787

initial synchronization

Back 787

The first synchronization for a subscription, during which system tables and other objects that are required by replication, and the schema and data for each article, are copied to the Subscriber.

Front 788

initial tape

Back 788

In a media set using tape backup devices, the first tape in a media family.

Front 789

inner join

Back 789

An operation that retrieves rows from multiple source tables by comparing the values from columns shared between the source tables. An inner join excludes rows from a source table that have no matching rows in the other source tables.

Front 790

in-person authentication

Back 790

Physical authentication to complete a certificate request transaction. For example, an end user requesting his/her personal identification number (PIN) be unblocked will visit a certificate manager in person to provide in-person authentication with identification, such as an employee badge or drivers license.

Front 791

InProc

Back 791

A circumstance where the COM object’s code is loaded from a DLL file and is located in the same process as the client.

Front 792

input adapter

Back 792

An adapter that accepts incoming event streams from external sources such as databases, files, ticker feeds, network ports, manufacturing devices and so on.

Front 793

input member

Back 793

A member whose value is loaded directly from the data source instead of being calculated from other data.

Front 794

input set

Back 794

The set of data provided to a Multidimensional Expressions (MDX) value expression upon which the expression operates.

Front 795

input source

Back 795

Any table, view, or schema diagram used as an information source for a query.

Front 796

input stream

Back 796

A flow of information used in a program as a sequence of bytes that are associated with a particular task or destination. Input streams include series of characters read from the keyboard to memory and blocks of data read from disk files.

Front 797

insensitive cursor

Back 797

A cursor that does not reflect data modification made to the underlying data by other users while the cursor is open.

Front 798

insert event

Back 798

The event kind used to signify the arrival of an event into the stream. The insert event type consists of metadata that defines the valid lifetime of the event and the payload (data) fields of the event.

Front 799

Insert Into query

Back 799

A query that copies specific columns and rows from one table to another or to the same table.

Front 800

Insert Values query

Back 800

A query (SQL statement) that creates a new row and inserts values into specified columns.

Front 801

instance

Back 801

A copy of SQL Server running on a computer.

Front 802

instance control provider

Back 802

A provider that allows you to issue control commands against workflow instances in an instance store. For example, a SQL control provider lets you suspend, resume, or terminate instances stored in a SQL Server database. When you execute a cmdlet that controls a workflow instance in an instance store, the cmdlet internally uses the control provider for that instance store to send commands to the instance.

Front 803

instance query provider

Back 803

A provider that allows you to issue queries against an instance store. For example, a SQL query provider lets you query for workflow instances stored in a SQL Server database. When you execute a cmdlet that queries for instances against an instance store, the cmdlet internally uses the query provider to retrieve instances from that store.

Front 804

instance store

Back 804

A set of database tables that store workflow instance state and workflow instance metadata.

Front 805

instance store provider

Back 805

In Windows AppFabric, a provider that allows you to create instance store objects. For example, a SQL store provider allows clients to create SQL workflow instance store objects, which in turn allows clients to save and retrieve workflow instances to and from a persistence store.

Front 806

integration

Back 806

In computing, the combining of different activities, programs, or hardware components into a functional unit.

Front 807

integrity

Back 807

The accuracy of data and its conformity to its expected value, especially after being transmitted or processed.

Front 808

integrity constraint

Back 808

A property defined on a table that prevents data modifications that would create invalid data.

Front 809

intent lock

Back 809

A lock that is placed on one level of a resource hierarchy to protect shared or exclusive locks on lower-level resources.

Front 810

intent share

Back 810

A lock that is placed on one level of a resource hierarchy to protect shared or exclusive locks on lower-level resources.

Front 811

interactive structured query language

Back 811

An interactive command prompt utility provided with SQL Server that lets users run Transact-SQL statements or batches from a server or workstation and view the results that are returned.

Front 812

interface

Back 812

A defined set of properties, methods, and collections that form a logical grouping of behaviors and data.

Front 813

interface implication

Back 813

If an interface implies another interface, then any class that implements the first interface must also implement the second interface. Interface implication is used in an information model to get some of the effects of multiple inheritance.

Front 814

intermediate language

Back 814

A computer language used as an intermediate step between the original source language, usually a high-level language, and the target language, usually machine code. Some high-level compilers use assembly language as an intermediate language.

Front 815

International Electrotechnical Commission

Back 815

One of two international standards bodies responsible for developing international data communications standards. The International Electrotechnical Commission (IEC) works closely with the International Organization for Standardization (ISO) to define standards of computing. They jointly published the ISO/IEC SQL-92 standard for SQL.

Front 816

Internet Protocol security

Back 816

A set of industry-standard, cryptography-based services and protocols that help to protect data over a network.

Front 817

interprocess communication

Back 817

The ability of one task or process to communicate with another in a multitasking operating system. Common methods include pipes, semaphores, shared memory, queues, signals, and mailboxes.

Front 818

interval event

Back 818

An event whose payload is valid for a given period of time. The metadata of the interval event requires that both the start and end time of the interval be provided in the event metadata. Interval events are valid only for this specific interval.

Front 819

interval event model

Back 819

The event model of an interval event.

Front 820

invoke operation

Back 820

A domain operation that is executed without tracking or deferred execution.

Front 821

IP address

Back 821

A binary number that uniquely identifies a host (computer) connected to the Internet to other Internet hosts, for the purposes of communication through the transfer of packets.

Front 822

IPC

Back 822

The ability of one task or process to communicate with another in a multitasking operating system. Common methods include pipes, semaphores, shared memory, queues, signals, and mailboxes.

Front 823

IPsec

Back 823

A set of industry-standard, cryptography-based services and protocols that help to protect data over a network.

Front 824

isolation level

Back 824

The property of a transaction that controls the degree to which data is isolated for use by one process, and is guarded against interference from other processes.

Front 825

ISQL

Back 825

An interactive command prompt utility provided with SQL Server that lets users run Transact-SQL statements or batches from a server or workstation and view the results that are returned.

Front 826

item

Back 826

A unit of data or metadata that is being synchronized. A typical item of data might be a file or record, whereas a typical item of metadata might be a knowledge item.

Front 827

item-level role assignment

Back 827

A security policy that applies to an item in the report server folder namespace.

Front 828

item-level role definition

Back 828

A security template that defines a role used to control access to or interaction with an item in the report server folder namespace.

Front 829

iterate

Back 829

To execute one or more statements or instructions repeatedly. Statements or instructions so executed are said to be in a loop.

Front 830

job

Back 830

A specified series of operations, called steps, performed sequentially by a program to complete an action.

Front 831

job history

Back 831

Log that keeps a historical record of jobs.

Front 832

join

Back 832

To combine the contents of two or more tables and produce a result set that incorporates rows and columns from each table. Tables are typically joined using data that they have in common.

Front 833

join column

Back 833

A column referenced in a join condition.

Front 834

join condition

Back 834

A comparison clause that specifies how tables are related by their join columns.

Front 835

join filter

Back 835

A filter used in merge replication that extends the row filter of one table to a related table.

Front 836

join operator

Back 836

A comparison operator in a join condition that determines how the two sides of the condition are evaluated and which rows are returned.

Front 837

join path

Back 837

A series of joins indicating how two tables are related.

Front 838

junction table

Back 838

A table that establishes a relationship between other tables.

Front 839

Kagi chart

Back 839

A chart, mostly independent of time, used to track price movements and to make decisions on purchasing stock.

Front 840

key

Back 840

A string that identifies an object in the cache. This string must be unique within a region. Objects are associated with a key when they are added and then retrieved with the same key.

Front 841

key

Back 841

In encryption, authentication, and digital signatures, a value used in combination with an algorithm to encrypt or decrypt information.

Front 842

key

Back 842

In an array, the field by which stored data is organized and accessed.

Front 843

key

Back 843

A column or group of columns that uniquely identifies a row (primary key), defines the relationship between two tables (foreign key), or is used to build an index.

Front 844

key attribute

Back 844

The attribute of a dimension that links the non-key attributes in the dimension to related measures.

Front 845

key column

Back 845

A column whose contents uniquely identify every row in a table.

Front 846

key generator

Back 846

A hardware or software component that is used to generate encryption key material.

Front 847

key performance indicator

Back 847

A predefined measure that is used to track performance of a strategic goal, objective, plan, initiative, or business process. A KPI is evaluated against a target. An explicit and measurable value taken directly from a data source. Key performance indicators (KPIs) are used to measure performance in a specific area, for example, revenue per customer.

Front 848

key range lock

Back 848

A lock that is used to lock ranges between records in a table to prevent phantom additions to, or deletions from, a set of records. Ensures serializable transactions.

Front 849

key recovery

Back 849

The process of recovering a user's private key.

Front 850

Key Recovery Agent

Back 850

A designated user that works with a certificate administrator to recover a user’s private key. A specific certificate template is applied to a Key Recovery Agent.

Front 851

keyset-driven cursor

Back 851

A cursor that shows the effects of updates made to its member rows by other users while the cursor is open, but does not show the effects of inserts or deletes.

Front 852

knowledge

Back 852

The metadata about all the changes that a participant has seen and maintains.

Front 853

KPI

Back 853

A predefined measure that is used to track performance of a strategic goal, objective, plan, initiative, or business process. A KPI is evaluated against a target. An explicit and measurable value taken directly from a data source. Key performance indicators (KPIs) are used to measure performance in a specific area, for example, revenue per customer.

Front 854

KRA

Back 854

A designated user that works with a certificate administrator to recover a user’s private key. A specific certificate template is applied to a Key Recovery Agent.

Front 855

Language for non-Unicode programs

Back 855

A Regional and Language Options setting that specifies the default code pages and associated bitmap font files for a specific computer that affects all of that computer's users. The default code pages and fonts enable a non-Unicode application written for one operating system language version to run correctly on another operating system language version.

Front 856

language service parser

Back 856

A component that is used to describe the functions and scope of the tokens in source code.

Front 857

What OT passage is being alluded to in 1 Timothy 5:18–19 (ESV)
18 For the Scripture says, “You shall not muzzle an ox when it treads out the grain,” and, “The laborer deserves his wages.” 19 Do not admit a charge against an elder except on the evidence of two or three witnesses.

Back 857

Deuteronomy 25:4
4 “You shall not muzzle an ox when it is treading out the grain.
Deuteronomy 24:15
Laborer worth his hire

Front 858

latch

Back 858

A short-term synchronization object protecting actions that need not be locked for the life of a transaction. A latch is primarily used to protect a row that the storage engine is actively transferring from a base table or index to the relational engine.

Front 859

latency

Back 859

The delay that occurs while data is processed or delivered.

Front 860

lazy loading

Back 860

A pattern of data loading where related objects are not loaded until a navigation property is accessed.

Front 861

lazy schema validation

Back 861

An option that delays checking the remote schema to validate its metadata against a query until execution in order to increase performance.

Front 862

lead byte

Back 862

The byte value that is the first half of a double-byte character.

Front 863

lead host

Back 863

A cache host that has been designated to work with other lead hosts and to keep the cluster running at all times.

Front 864

leaf

Back 864

A node with no child objects represented in the tree.

Front 865

leaf level

Back 865

The bottom level of a clustered or nonclustered index, or the bottom level of a hierarchy.

Front 866

leaf member

Back 866

A member that has no descendents.

Front 867

leaf node

Back 867

A node with no child objects represented in the tree.

Front 868

learned knowledge

Back 868

The current knowledge of a source replica about a specific set of changes, and the logged conflicts of that replica.

Front 869

least recently used

Back 869

The type of eviction used by the cache cluster, where least recently used objects are evicted before the most recently used objects.

Front 870

left outer join

Back 870

A type of outer join in which all rows from the left-most table in the JOIN clause are included. When rows in the left table are not matched by rows in the right table, all result set columns that come from the right table are assigned a value of NULL.

Front 871

level

Back 871

The name of a set of members in a dimension hierarchy such that all members of the set are at the same distance from the root of the hierarchy. For example, a time hierarchy may contain the levels Year, Month, and Day.

Front 872

lift chart

Back 872

In Analysis Services, a chart that compares the accuracy of the predictions of each data mining model in the comparison set.

Front 873

lightweight pooling

Back 873

An option that provides a means of reducing the system overhead associated with the excessive context switching sometimes seen in symmetric multiprocessing (SMP) environments by performing the context switching inline, thus helping to reduce user/kernel ring transitions.

Front 874

line layer

Back 874

The layer in a map report that displays spatial data as lines, for example, lines that indicate paths or routes.

Front 875

linked dimension

Back 875

A reference in a cube to a dimension in a different cube (that is, a cube with a different data source view that exists in the same or a different Analysis Services database). A linked dimension can only be related to measure groups in the source cube, and can only be edited in the source database.

Front 876

linked measure group

Back 876

A reference in a cube to a measure group in a different cube (that is, a cube with a different data source view that exists in the same or a different Analysis Services database). A linked measure group can only be edited in the source database.

Front 877

linked server

Back 877

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.

Front 878

linked table

Back 878

An OLE DB rowset exposed by an OLE DB data source that has been defined as a linked server for use in SQL Server distributed queries.

Front 879

linking table

Back 879

A table that has associations with two other tables, and is used indirectly as an association between those two tables.

Front 880

LINQ

Back 880

A query syntax that defines a set of query operators that allow traversal, filter, and projection operations to be expressed in a direct, declarative way in any .NET-based programming language.

Front 881

little endian

Back 881

Pertaining to a processor memory architecture that stores numbers so that the least significant byte is placed first.

Front 882

local cache

Back 882

A feature that enables deserialized copies of cached objects to be saved in the memory of the same process that runs the cache-enabled application.

Front 883

local Distributor

Back 883

A server that is configured as both a Publisher and a Distributor for SQL Server Replication.

Front 884

local partitioned view

Back 884

A view that joins horizontally partitioned data from a set of member tables across a single server, making the data appear as if from one table.

Front 885

local subscription

Back 885

A subscription to a merge publication that uses the priority value of the Publisher for conflict detection and resolution.

Front 886

locale

Back 886

A collection of rules and data specific to a language and a geographic area. Locales include information on sorting rules, date and time formatting, numeric and monetary conventions, and character classification.

Front 887

localization

Back 887

The process of adapting a product and/or content (including text and non-text elements) to meet the language, cultural, and political expectations and/or requirements of a specific local market (locale).

Front 888

lock

Back 888

A restriction on access to a resource in a multiuser environment.

Front 889

lock escalation

Back 889

The process of converting many fine-grain locks into fewer coarse-grain locks, thereby reducing system overhead.

Front 890

log backup

Back 890

A backup of transaction logs that includes all log records not backed up in previous log backups. Log backups are required under the full and bulk-logged recovery models and are unavailable under the simple recovery model.

Front 891

log chain

Back 891

A continuous sequence of transaction logs for a database. A new log chain begins with the first backup taken after the database is created, or when the database is switched from the simple to the full or bulk-logged recovery model. A log chain forks after a restore followed by a recovery, creating a new recovery branch.

Front 892

log provider

Back 892

A provider that logs package information at run time. Integration Services includes a variety of log providers that make it possible to capture events during package execution. Logs are created and stored in formats such as XML, text, database, or in the Windows event log.

Front 893

Log Reader Agent

Back 893

In Replication, the executable that monitors the transaction of each database configured for transactional replication, and copies the transactions marked for replication from the transaction into the distribution database.

Front 894

log sequence number

Back 894

A unique number assigned to each entry in a transaction log. LSNs are assigned sequentially according to the order in which entries are created.

Front 895

log shipping

Back 895

Copying, at regular intervals, log backup from a read-write database (the primary database) to one or more remote server instances (secondary servers). Each secondary server has a read-only database, called a secondary database, that was created by restoring a full backup of the primary database without recovery. The secondary server restores each copied log backup to the secondary database. The secondary servers are warm standbys for the primary server.

Front 896

log shipping configuration

Back 896

A single primary server, one or more secondary servers (each with a secondary database), and a monitor server.

Front 897

log shipping job

Back 897

A job performing one of the following log-shipping operations: backing up the transaction log of the primary database at the primary server (the backup job), copying the transaction log file to a secondary server (the copy job), or restoring the log backup to the secondary database on a secondary server (the restore job). The backup job resides on the primary server; the copy and restore jobs reside on each of the secondary servers. See also: primary database, primary server, secondary database, secondary server.

Front 898

log sink

Back 898

A tracing function of the cache client and cache host. Log sinks capture trace events from the cache client or cache host and can display them in a console, write them to a log file, or report them to the Event Tracing for Windows (ETW) framework inside Windows.

Front 899

logic error

Back 899

An error, such as a faulty algorithm, that causes a program to produce incorrect results but does not prevent the program from running. Consequently, a logic error is often very difficult to find.

Front 900

logical name

Back 900

A name used by SQL Server to identify a file.

Front 901

logical record

Back 901

A merge replication feature that allows you to define a relationship between related rows in different tables so that the rows are processed as a unit.

Front 902

login ID

Back 902

A string that is used to identify a user or entity to an operating system, directory service, or distributed system. For example, in Windows® integrated authentication, a login name uses the form "DOMAIN\username."

Front 903

login security mode

Back 903

A security mode that determines the manner in which an instance of SQL Server validates a login request.

Front 904

long parsing

Back 904

In the SQL system there are two typical types of threads: - short thread: it is a process that use the resources for a short time and - long thread: it is a process that use the resources for a long time. long parsing: is the analysis of the threads that lived for a long time Note: the definition of short/long is based on the system calculation/statistic for each process.

Front 905

Low Box

Back 905

The lowest value of a box on a Box Plot chart.

Front 906

low watermark

Back 906

A memory consumption threshold on each cache host that specifies when expired objects are evicted out of memory.

Front 907

low whisker

Back 907

The lowest value that is not an outlier on a box plot chart.

Front 908

LRU

Back 908

The type of eviction used by the cache cluster, where least recently used objects are evicted before the most recently used objects.

Front 909

LSN

Back 909

A unique number assigned to each entry in a transaction log. LSNs are assigned sequentially according to the order in which entries are created.

Front 910

luring attack

Back 910

An attack in which the client is lured to voluntarily connect to the attacker.