Wiley Professional Microsoft SQL Server 2008 Programming 978-0-470-25702-9 Manuel D’Utilisation
Codes de produits
978-0-470-25702-9
Chapter 1: Being Objective: Re-Examining Objects in SQL Server
assume that you are already somewhat familiar with most of the objects discussed here, but the goal
is to fill in any holes and fully prepare you for the more advanced discussions to come.
is to fill in any holes and fully prepare you for the more advanced discussions to come.
In this chapter, we will take a high-level look into:
❑
Database objects
❑
Data types (including some that are new with SQL Server 2008!)
❑
Other database concepts that ensure data integrity
An Over view of Database Objects
An RDBMS such as SQL Server contains many objects. Object purists out there may quibble with whether
Microsoft’s choice of what to call an object (and what not to) actually meets the normal definition 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:
Microsoft’s choice of what to call an object (and what not to) actually meets the normal definition 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:
The database itself
Indexes
The transaction log
CLR assemblies
Tables
Reports
Filegroups
Full-text catalogs
Diagrams
User-defined data types
Views
Roles
Stored procedures
Users
User-defined functions
Encryption Keys
This is far from being a comprehensive list, and is in no particular order, but it does give you some of a
feel for the breadth of objects that your SQL Server can manage.
feel for the breadth of objects that your SQL Server can manage.
The Database Object
The database is effectively the highest-level object that you can refer to within a given SQL Server. (Tech-
nically speaking, the server itself can be considered to be an object, but not from any real ‘‘programming’’
perspective, so we’re not going there.) Most, but not all, other objects in a SQL Server are children of the
database object.
nically speaking, the server itself can be considered to be an object, but not from any real ‘‘programming’’
perspective, so we’re not going there.) Most, but not all, other objects in a SQL Server are children of the
database object.
If you are familiar with old versions of SQL Server you may now be saying, ‘‘What? What happened
to logins? What happened to Remote Servers and SQL Agent tasks?’’ SQL Server has several other
objects (as listed previously) that exist in support of the database. With the exception of linked servers,
and perhaps Integration Services packages, these are primarily the domain of the database administrator
and as such, you generally don’t give them significant thought during the design and programming
processes. (They are programmable via something called the SQL Management Objects [SMO], but that
is far too special a case to concern you with here. We will look at SMO more fully in Chapter 26.)
to logins? What happened to Remote Servers and SQL Agent tasks?’’ SQL Server has several other
objects (as listed previously) that exist in support of the database. With the exception of linked servers,
and perhaps Integration Services packages, these are primarily the domain of the database administrator
and as such, you generally don’t give them significant thought during the design and programming
processes. (They are programmable via something called the SQL Management Objects [SMO], but that
is far too special a case to concern you with here. We will look at SMO more fully in Chapter 26.)
2