Page 129 - DCAP508_DATABASE_ADMINISTRATION

Unit 9: Database Recovery Models

2. Disaster recovery planning: The process of formulating, documenting, and testing the Notes
procedures that would be performed if production data in one or more SQL Server databases
were to be lost or modified in an unforeseen disaster or malicious attack.
3. Minimally logged operations (bulk load operations): Data movement operations that
require minimal logging in the transaction log. These operations include bcp, certain Data
Transformation Services (DTS) operations, and SELECT INTO. Depending on the recovery
model for a database, any of these operations might either be fully logged or minimally
logged.
4. Filegroup: A logical grouping of SQL Server database files. By default, a new SQL Server
database contains the Primary filegroup.
5. Log Sequence Number (LSN): The unique number that each operation is stamped with
when it is written to the transaction log. A single SQL Server transaction may contain
several LSNs.
6. Logical file names: The names that are used by SQL Server to identify files within an SQL
Server database.
7. Physical file names: The name used by the operating system to identify specific files. All
SQL Server database files have both a physical and a logical file name.

8. Extent: A collection of 8 data pages. Since a data page is 8 KB, an extent is 64 KB.
9. SQL Query Analyzer: A graphical tool provided with SQL Server client utilities to query
SQL Server databases using the Transact-SQL commands.

10. Transaction: A set of modifications that are performed as a single unit of work. A transaction
follows the ACID guidelines. For more information on the ACID standard, see
“Transactions” in SQL Server Books Online.
11. Transaction log: A record of modifications performed to a database. The amount of
information logged in the transaction log depends on the recovery model for a database.

12. Tail of transaction log: The transactions that have been committed but not backed up
since the previous complete or differential database backup or transaction log backup.
13. Transaction undo file: File containing information regarding any modifications that were
made as part of incomplete transactions at the time the backup was performed. A transaction
undo file is required if a database is loaded in read-only state. In this state, further transaction
log backups may be applied.
14. Virtual Log File (VLF): A logical section within an SQL Server database’s transaction log.
When performing a truncate of the transaction log, an entire VLF is cleaned out.

Self Assessment

Name the following:
1. A logical section within an SQL Server database’s transaction log.
2. A set of modifications that are performed as a single unit of work.

3. The unique number that each operation is stamped with when it is written to the transaction
log.
4. A graphical tool provided with SQL Server client utilities to query SQL Server databases
using the Transact-SQL commands.

LOVELY PROFESSIONAL UNIVERSITY 123