An instance of an RDBMS such as SQL Server contains many objects. Object purists out there may quibble with whether Microsoft's choice of what to (and what not to) call an object actually meets the normal defi nition of an object, but, for SQL Server's purposes, the list of some of the more important database objects can be said to contain such things as:
- Database itself
- The transaction log: Every SQL Server database has a transaction log that records all transactions and the database modifications made by each transaction. The transaction log is a critical component of the database. If there is a system failure, you will need that log to bring your database back to a consistent state.
- Tables
- Indexes: An index is an on-disk structure associated with a table or view that speeds retrieval of rows from the table or view. An index contains keys built from one or more columns in the table or view. These keys are stored in a structure (B-tree) that enables SQL Server to find the row or rows associated with the key values quickly and efficiently.
- Filegroups: Filegroups are the physical files on your disc volumes that hold SQL Server's data and can be used for backup and administrative management purposes.
- Diagrams
- Views
- Stored procedures
- User-defined functions
- Sequences
- Users
- Roles
- Assemblies
- Reports
- Full-text catalogs:
- User-defined data types: CREATE TYPE (Transact-SQL): Creates an alias data type or a user-defined type in the current database in SQL Server or Azure SQL Database. The implementation of an alias data type is based on a SQL Server native system type. A user-defined type is implemented through a class of an assembly in the Microsoft .NET Framework common language runtime (CLR). To bind a user-defined type to its implementation, the CLR assembly that contains the implementation of the type must first be registered in SQL Server by using CREATE ASSEMBLY.
In the next lesson, the requirements for this course will be discussed.