لطفا منتظر باشید ...
L
large level
A dimension level that contains a number of members that equals or exceeds the threshold for large levels. This threshold varies and is set in the Properties dialog box of Analysis Manager.
latency
The amount of time that elapses when a data change is completed at one server and when that change appears at another (for example, the time between when a change is made at a Publisher and when it appears at the Subscriber).
LCID
See locale identifier (LCID).
leaf
In a tree structure, an element that has no subordinate elements. For example, in Analysis Services, a leaf is a dimension member that has no descendants. See also non-leaf.
leaf level
The bottom level of a clustered or non- clustered index. In a clustered index, the leaf level contains the actual data pages of the table. In a nonclustered index, the leaf level either points to data pages or points to the clustered index (if one exists), rather than containing the data itself.
leaf member
A dimension member that does not have descendants.
left outer join
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.
level
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 can contain the levels Year, Month, and Day. See also dimension, hierarchy.
level hierarchy
See dimension hierarchy.
library
In Analysis Services, a folder that contains shared objects (such as shared dimensions) that can be used by multiple objects within a database.
linked cube
A cube that is based on a cube defined on another Analysis server. See also publishing server, source cube, subscribing server.
linked server
A definition of an OLE DB data source used by SQL Server 2000 distributed queries. The linked server definition specifies the OLE DB provider required to access the data and includes enough addressing information for the OLE DB provider to connect to the data. Any rowsets exposed by the OLE DB data source can then be referenced as tables (called linked tables) in SQL Server 2000 distributed queries. See also local server.
linked table
An OLE DB rowset exposed by an OLE DB data source that has been defined as a linked server for use in SQL Server 2000 distributed queries. The rowsets exposed by the linked server can be referenced as tables in distributed queries.
linking table
A table that has associations with two other tables and is used indirectly as an association between those two tables.
livelock
A request for an exclusive lock that is repeatedly denied because a series of overlapping shared locks keeps interfering. SQL Server detects the situation after four denials and refuses further shared locks. A livelock also occurs when read transactions monopolize a table or a page, forcing a write transaction to wait indefinitely. See also deadlock.
local cube
A cube created and stored with the extension .CUB on a local computer by using PivotTable Service.
local Distributor
A server that is configured as both a Publisher and a Distributor for SQL Server Replication. See also Distributor, remote Distributor.
local group
A group in Windows NT 4.0 or Windows 2000 containing user accounts and global groups from the domain group in which they are created and any trusted domain. Local groups cannot contain other local groups.
local login identification
The identification (ID) that a user must use to log in to a local server. A login ID can have up to 128 characters. The characters can be alphanumeric; however, the first character must be a letter (for example, CHRIS or TELLER8).
local server
In SQL Server 2000 connections, an instance of SQL Server 2000 running on the same computer as the application. When resolving references to database objects in a Transact-SQL statement, the local server is the instance of SQL Server 2000 executing the statement. In SQL Server 2000 distributed queries, the local server is the instance of SQL Server 2000 executing the distributed query. The local server then accesses any linked servers referenced in the query. In SQL Server 2000 remote stored procedures, the local server is the instance of SQL Server executing an EXEC statement that references a remote stored procedure. The local server then passes the execution request to the remote server on which the remote stored procedure resides. See also remote server.
local subscription
A subscription to a merge publication that uses the priority value of the Publisher for conflict detection and resolution.
local variable
A user-defined variable that has an assigned value. A local variable is defined with a DECLARE statement, is assigned an initial value by a SELECT or SET statement, and is used within the statement batch or procedure in which it was declared.
locale
The Windows operating system attribute that defines certain behaviors related to language. The locale defines the code page, or bit patterns, used to store character data and the order in which characters are sorted. The locale also defines language-specific items such as the format used for dates and time and the character used to separate decimals in numbers. A unique number called a locale identifier (LCID) identifies each locale. SQL Server 2000 collations are similar to locales in that the collations define language-specific types of behaviors for instances of SQL Server 2000. See also collation, locale identifier (LCID).
locale identifier (LCID)
A number that identifies a Windows-based locale. See also locale.
lock
A restriction on access to a resource in a multi-user environment. SQL Server automatically locks users out of a specific row, column, or file in order to maintain security or to prevent concurrent data modification problems.
lock escalation
The process of converting many fine-grain locks into fewer coarse-grain locks, thereby reducing system overhead.
log file
A file or set of files containing a record of the modifications made in a database. See also data file.
logical database design
The design of a database based on business requirements, without regard for the physical implementation. Logical database design serves to verify the requirements, before physical implementation, which is much costlier to change, takes place.
logical data model
A formal model of business data based on business requirements, without regard for the physical implementation. Generally, the logical model is the first tool designed for a database, and it serves to verify the business assumptions, before physical implementation of a database takes place.
logical name
A name that SQL Server uses to identify a file. A logical name for a file must correspond to the rules for identifiers and can have as many as 30 characters (for example, ACCOUNTING or LIBRARY).
logical operators
The operators AND, OR, and NOT, which are used to connect search conditions in WHERE clauses.
login (account)
An identifier that gives a user permission to connect to SQL Server 2000 by using SQL Server Authentication. Users who connect to SQL Server 2000 by using Windows NT Authentication are identified by their Windows 2000 logon and do not need a separate SQL Server 2000 login.
login security mode
A security mode that determines the manner in which a SQL Server 2000 instance validates a login request. There are two types of login security: Windows Authentication and SQL Server authentication.
lookup table
A table, either in a database or hard- coded in the English Query application, that contains codes and the English words or phrases that they represent. For example, a gender lookup table contains the following code and English descriptions: M, Male.
