Glossary of
Terms
|
|
|
|
Autoshrink option |
Tries to shrink the database without manual intervention. It
does so five minutes after startup and every thirty minutes thereafter. The
file is shrunk to a size where 25% of the file is unused space or to the size
of the file when it was created, whichever is greater. |
|
|
|
|
Batch |
A batch is a set of Transact-SQL statements that are submitted
together and executed as a group. Use a GO statement in SQL Query Analyzer
and the osql utility to signal the end of a
batch. The scope of user-defined variables is limited to a batch. §
CREATE PROCEDURE §
CREATE VIEW §
CREATE TRIGGER §
CREATE RULE §
CREATE DEFAULT |
|
Information about extents modified by bulk operations since the
last BACKUP LOG statement. |
|
|
|
|
|
Cascading referential integrity automatically propagates changes
to the database. |
|
|
Type of integrity: Domain |
|
|
Type of integrity: Referential
|
|
|
Clustered Index |
In a clustured index, the leaf level is the actual data page.
Data is physically stored on a data page in ascending order. The order of the
values in the index pages is also ascenging. §
Each Table Can Have
Only One Clustered Index §
the Physical Row
Order of the Table and the Order of Rows in the Index Are the Same §
Key Value Uniqueness
is maintained Explicitly or Implicitly §
Average Size is
About 5% of the Table Size §
During Index
Creation SQL Server requires about 1.2 (1 = data and .2 = index) Times the
Table Size. |
|
Clustered Table |
Table with a clustered index |
|
Collation |
A collation specifies
the bit patterns that represent each character and the rules
by which characters are sorted and compared. |
|
Composite Index |
Composite indexes specify more than one column as the kay value.
|
|
Constraint |
Preferred method of enforcing data integrity.
|
|
|
|
|
Data Integrity |
Integrity types: |
|
Contains content other than text, ntext and image data. |
|
|
Criteria that the data must meet as a part of an object definition.
SQL-Server automatically ensures that the data conformes
to the criteria. |
|
|
Type of integrity: Domain
|
|
|
Density |
Density is the average percentage of duplicate rows in an
index. If the data or query is not very selective (low selectivity) you have a high amount of
density. |
|
Information about extents that have changed since the last
BACKUP DATABASE statement. |
|
|
|
|
|
8 Pages (64 KB), 16 extents per megabyte. |
|
|
|
|
|
Fill Factor |
FILLFACTOR is a value from 1 through 100 that specifies the
percentage of the index page to be left empty. |
|
Type of integrity: Referential
|
|
|
|
|
|
Global Allocation Map. Each GAM page covers 63'904 extents, or nearly 4
GB of data. The GAM page contains one bit for each extent that it covers. the bit is set to 0 if the extent is allocated, and set to
1 if it is free. |
|
|
Ghost Record |
Deleted rows from the leaf level of an index marked as invalid. |
|
|
|
|
Heap |
Table with no clustered
index. Collection of data
pages for a table. |
|
|
|
|
Index Allocation Map. The IAM page contains the location of the eight
initial pages and a bitmap of extents indicating which extents are in use for
that object. A single IAM page can track up to 512'000 data pages (4'000 MB).
SQL Server adds more IAM pages for larger tables. Each object has at least one IAM for each file
on which it has extends. |
|
|
Index Node |
Page in an index. |
|
Contains index structures. |
|
|
Indexed view |
|
|
Information Schema Views |
There are 20 views:
|
|
|
|
|
Leaf Level |
The bottom level of a clustered or nonclustered
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. |
|
|
|
|
Indexed view. The first
index is always a clustered index. It has the same structure as a table that
has a clustered index and is stored in the database. |
|
|
Merge replication allows various sites to work autonomously
(online or offline) and merge data modifications made at multiple sites into
a single, uniform result at a later time. The initial snapshot is applied to
Subscribers and then SQL Server 2000 tracks changes to published data at the
Publisher and at the Subscribers. |
|
|
Mixed extent |
See extent. |
|
|
|
|
Null block |
A null block is a variable-length set of bytes. It constists of 2 bytes storing the number of columns
followed by a null bitmap inicating wether each individual column is null. The size of the
null bitmap is equal to one bit per column, rounded to the nearest byte. One
to eight columns require a 1-byte bitmap. Nine to sixteen columns require a
2-byte bitmap. |
|
|
|
|
SQL-Server supports the following objects:
|
|
|
|
|
|
PAD_INDEX |
The PAD_INDEX option specifies the percentage to which to fille the non-leaf -level index pages. You can use the
PAD_INDEX only in when FILLFACTOR is specified, because the PAD_INDEX
percentage is determined by the percentage value specified for FILLFACTOR.
|
|
PAG |
Page number. The page is identified by a fileid:page combination, where fileid
is the fileid in the sysfiles
table, and page is the logical page number within that file. |
|
8 KB, 128 Pages per
megabyte. Type of pages: §
Pages that track
space allocation §
Pages that contain
user and index data §
Other |
|
|
The process of moving half the rows or entries in a full data or
index page to two new pages to make room for a new row or index entry. |
|
|
Page Free Space page. This page is an allocation
page that contains information about free space available on the pages
in a file. Page 1 of each file is a PFS page. SQL Server adds other PFS pages
as needed. Each PFS page can track 8'000 contiguos pages, which is nearly 64 MB of data. For each
page, the PFS page contains a byte that tracks:
|
|
|
Type of integrity: Entity
|
|
|
Scripts that define both the criteria that the data must meet
and enforce the criteria. |
|
|
|
|
|
Type of integrity: Domain |
|
|
RID |
Row Identifier. |
|
|
|
|
Selectivity is derived from the percentage of rows in a table
that are accessed or returned by a query. |
|
|
Secondary Global Allocation Map. SGAM pages track mixed extents that currently
have at least one unused page. They cover 63'904 extents. A bit set to 0
indicates that an extent is either a uniform or a mixed extent without any
free pages. A bit set to 1 indicates a mixed extent with one ore more free
pages. |
|
|
Snapshot replication copies the entire publication from one
SQL-Server computer to another. |
|
|
SQL Server Collation |
Each SQL Server
collation specifies three properties:
|
|
|
|
|
Tabular Data Stream |
See TDS. |
|
Contains text, ntext and
image content. |
|
|
Tabular Data Stream.
SQL-Server specific application-level protocol. §
TDS 8.0 - SQL Server
2000 Clients §
TDS 7.0 - SQL Server
7.0 Clients §
TDS 4.2 - SQL Server
6.5, 6.0 or 4.21 clients |
|
|
With transactional replication, an initial snapshot of data is
propagated to Subscribers, and then when data modifications are made at the
Publisher, the individual transactions are captured and propagated to
Subscribers. |
|
|
|
|
|
Uniform extent |
See extent. |
|
Type of integrity: Entity
|
|
|
|
|
|
Variable block |
A variable block consists of two bytes that describe how many
variable-length columns are present. An additional two bytes per column point
to the end of each variable-length column. The variable block is ommited if there are no variable-length columns. |
|
|
|
|
WITH CHECK OPTION |
The WITH_CHECK_OPTION forces all data modification statements
that are executed against the view to adhere to certain criteria. These criterias are specified within the SELECT statement that defines
the view. If the changed values are out of the range of the view definition,
SQL Server rejects the modifications. |
|
|
|