A configuration of two SQL Server installations in a clustered environment where each node is initially configured with one SQL Server installation but where either node can host both "active" SQL Servers. This term applies to SQL Server 6.5 and SQL Server 7.0 clusters only. It has been replaced by a multipleinstance cluster for SQL Server 2000.

A configuration with one SQL Server installation in a clustered environment where one "active" node runs the SQL Server resources, and the other is waiting for a potential failover. This term applies to SQL Server 6.5 and SQL Server 7.0 clusters only. It has been replaced by a single-instance cluster for SQL Server 2000.

The process allowing changes to applications to occur in a predictable fashion with minimal or no impact on the service. Change management applies to all phases of a lifecycle.

The process of diverting client or application usage to another SQL Server database in the event of a replication failure—if replication is the high-availability method employed—or in the event of a role change.

A collection of cluster resources analogous to a folder on your hard drive that contains multiple files.

A physical server participating in a cluster.

Object types which may be added to cluster resource groups to provide a specific type of cluster functionality that can be utilized by the cluster. Default cluster resource types include DHCP servers, MSDTC, file shares, generic applications/services, servers running IIS, IP addresses, network names, MSMQ, physical disks, print spoolers, and time services.

See cluster group.

An application that runs on a node, is managed as a cluster resource, and is designed to be aware of and interact with the server cluster environment. SQL Server 2000 is an example of a cluster-aware application. The clustering application program interface provides the programming elements necessary to work directly with cluster objects and to interact with the Cluster Service service.

Connecting two or more computers in such a way that they behave like a single computer to an application or client. Clustering is used for parallel processing, load balancing, and fault tolerance.

The process used by Network Load Balancing to reach consensus on what the Network Load Balancing cluster looks like. See Network Load Balancing.

See direct attached storage.

An installation of SQL Server 2000 that generally uses the name of the underlying server, or a specific name in a server cluster that is the name of neither an individual node nor the server cluster itself. A default instance is similar to the experience of having one installation of SQL Server 7.0 or earlier per server. There can only be one default instance of SQL Server on an individual standalone server or a single server cluster. All other instances must be named instances.

A type of database backup that only backs up changes made to the database since the last full database backup.

An external disk array connected to one or more servers via traditional disk protocols such as SCSI.

The process of executing documented procedures to restore a server or an entire environment after a catastrophic problem occurs.

The fundamental unit of data storage for SQL Server. The page size in SQL Server 2000 is 8192 bytes, or 8 KB.

The amount of time that a given system or solution is not available for servicing requests.

The basic unit by which space is allocated to a table or an index. An extent is eight continuous disk pages, which equates to 64 KB.

The process in which, in response to a node or resource failure, resources in a cluster switch ownership and start on another node in the server cluster. This term applies to a server cluster/failover cluster combination only. In log shipping implementations, the similar terms switch and role change are used to describe the change in ownership that occurs between primary and secondary servers.

The SQL Server 2000 implementation of clustering for availability that is built on a Windows Server Cluster.

A grouping of SQL servers used together to achieve scalability by employing a distributed partition view. A federated cluster is not used for availability, only for achieving scalability through scale out.

A named collection of one or more disk files that represent a single allocation on or for administration of a database. A database can have more than one filegroup.

Shorthand for a system’s being available, or having uptime, 99.999 percent of the time.

A complete point-in-time backup of a database.

See private network.

A check in the server cluster, run after LooksAlive, that is an applicationspecific health check. For SQL Server 2000, this issues a SELECT @@ Servername query to determine if the SQL Server instance can handle requests.

The process of testing an application, entire solution, or hardware component under realistic conditions, or load, to ensure that it will behave properly in a highly utilized production environment.

A unique identifier assigned to a record in the transaction log that is incremented automatically.

The process of backing up a transaction log on one SQL Server, copying it, and then applying it to another SQL Server where a full database backup of that original database has been applied with the proper settings.

The log shipping primary/secondary combination.

The server containing the database source of the transaction logs.

The server containing the database recipient of the transaction logs in a log-shipping pair.

See logical drive.

Any volume created that Windows can see, after it has been formatted and assigned a drive letter. You can have multiple logical drives per volume.

See volume.

A specifically coded application-level health check in a server cluster to ensure that the application is up and running. For SQL Server, this is a lightweight check.

See Log Sequence Number (LSN).

See volume.

A relationship between a specific volume and a host at the disk controller level.

The average expected time between failures of a specific component.

The average time it takes to recover from a failure.

The original name for a server cluster under Windows NT 4.0.

See Microsoft Cluster Service (MSCS).

See mean time between failures (MTBF).

See mean time to recovery (MTTR).

A SQL Server 2000 failover cluster with more than one SQL Server virtual server.

An installation of SQL Server 2000 that has a unique name to differentiate itself from other SQL Server instances. The name must be unique for both the server as well as the domain. There can be multiple named instances of SQL Server on an individual standalone server or a single server cluster.

Low-cost, high-density storage generally used to store files; generally not used with databases.

The type of clustering under Windows Clustering that provides scalability and availability for IP-based services and some SQL Server uses.

Refers to the digit 9 in a percentage that represents availability. For example, three nines is 99.9 percent.

See cluster node.

The amount of time that a system or application is unavailable to those who normally access it from a business standpoint, although the server itself may be up and running and having normal maintenance performed on it, or one part of the overall solution is down, preventing access to that server.

The actual disk used internally in a system or as part of a disk array.

See log shipping primary.

In a cluster, the dedicated intra-cluster network used to run processes that check to see if the cluster is up and running. For non-clustered machines or other uses, a private network is one that is segmented off from the public network on a different subnet to offload tasks such as large file copies.

On a standalone server or a cluster, the network that allows clients and applications to access the server itself.

In a server cluster, contains the master copy of the server cluster’s configuration and is also used as a tie-breaker if all network communication fails between the nodes. Depending on the type of server cluster implemented, this may or may not be a physical disk on the shared cluster disk array.

See redundant array of independent disks (RAID).

The database-level setting—either Bulk-Logged, Full, or Simple under SQL Server 2000—that controls the amount of logging that occurs.

A specific fault-tolerant disk array system design strategy that takes into account issues of cost benefit, reliability, and performance. It can be implemented at a hardware or a software level; each provides a different profile of cost, reliability, and performance. Depending on the person defining RAID, the word independent may be substituted with inexpensive.

See cluster resource group.

The process of switching from the log shipping primary to the secondary; applies to log shipping only. This is a manual process.

A centralized and continually updated collection of information such as contacts, phone numbers, disaster recovery plans, software license information, support information, and so on. It is used in the event of an emergency to ensure the system can be brought back online in a timely fashion.

See storage area network (SAN).

See log shipping secondary.

The type of Windows Clustering that provides availability only. It is a collection of nodes that allow resources to be failed over to another node in the event of a problem. SQL Server 2000 failover clustering is installed and configured on top of a server cluster.

A signed agreement of system service requirements between two parties (such as your company and an ASP or between your department and end users) that defines the guidelines, response times, actions, and so on, that will be adhered to for the life of the agreement.

In a server cluster, the DAS or SAN that contains the disks used by the nodes.

This is a SQL Server 2000 failover cluster configured with only one SQL Server virtual server. This replaces the term active/passive.

See service level agreement (SLA).

Another name for an individual physical disk.

A server configured to be brought online in the event of a failure of the current server used in production. Standby servers are commonly referred to as "hot" or "warm" standby servers to reflect how quickly the server can be pressed into production.

An external disk array connected to one or more servers via underlying networking protocols, such as fibre, and requiring specialized hardware. SANs provide flexibility, availability, scalability, reliability, and ease of configuration.

The process of switching from one server to another in the event of a problem. This is usually used for non-clustered implementations where a manual process is implied.

A backup of the transaction log that flushes the transactions from the transaction log to a file. To have transaction log backup integrity, each consecutive file must not break the LSN chain.

The amount of time that a given system or solution is available for servicing requests.

The combination of the network name and IP address that makes up the clustered application or server that a client or application will access. This appears as a normal application or server. Both the server cluster itself, and a SQL Server 2000 instance installed on a cluster, can be considered virtual servers.

The amount of physical disk that Windows recognizes after the storage is configured at a hardware level (whether one individual disk or a RAID subsystem). The volume is then formatted and configured in other ways so Windows and applications can use it in different ways.

A server waiting to be brought online; generally refers to the secondary in a log shipping pair.

The umbrella group of clustering technologies for the Windows platform, which currently includes a server cluster and Network Load Balancing.

Isolating volumes on a SAN so that only designated computers that have access to the zone can see them and activity in that zone will not affect other volumes and users on the SAN.