All databases, including those that you create with SQL Server, are made up of specific components. Some of these (such as tables and indexes) will be discussed in the chapters of this project; however, for this chapter you should at least have a cursory understanding of what each component is and how it functions in relation to the other database components.

Tables
Perhaps the quintessential database components, tables are the information repositories where all of your data is stored. All databases should have at least one table, and each table will consist of columns and rows, which are defined in the following sections.

Columns
Columns contain specific information that, when taken collectively, comprise a complete table. Each column has specific attributes assigned to it.

Rows
Once you have established a set of columns, each combination of columns represents one row of information in your database. The number of rows that can exist within your individual tables is limited only by the amount of disk space at your disposal.

Stored Procedures
As you move through your SQL Server development, you will quickly come to the realization that you must repeat some data manipulation tasks on a regular (daily? weekly?) basis. These tasks are good candidates for automation. Stored procedures are just the ticket for such tasks because they allow specific data manipulation functions and processes to be run automatically.

Indexes
Indexes allow you to determine how your information is stored, sorted, and (as a combination of these two attributes) ultimately manipulated. A well-defined index will allow your procedures and processes to run much faster and more efficiently, thus greatly increasing the speed at which critical data result sets are returned to you and your users.

Columns Rows
The number of rows in your database is limited only by your available disk space!

Views
Views allow you to create specific windows to your data. Not real tables in and of themselves, views are a specific amalgamation of information that consists of attributes and configurations that you specify. You can use views to streamline how data is presented, and they are also a somewhat effective data security measure because they allow users to view only specific pieces of information stored in the database.

Transaction Logs
Although perhaps not as essential as the components discussed in the preceding sections, transaction logs are still a critical component of any database. In essence, transaction logs give you the ability to track the successful (or unsuccessful) execution of various processes and procedures. Transaction logs can become quite lengthy and therefore take up a fair amount of disk space, and they can also be a bit confusing, at least initially. Note that transaction logs also allow you to restore your database to a certain point in time, if a problem occurs.