Designing and Implementing Structured Storage (Database Engine)
A client/server database system is made up of two components:
Programs that provide an interface for client-based users to access data.
The database structure that manages and stores the data on the server.
For example, if you use SQL Server 2005 to create a checking account application, you must set up a database structure to manage the account transaction data and an application that acts as the user interface to the database. This allows users to access checking account information.
Creating a database to serve your business needs requires an understanding of how to design, create, and maintain each of these components to make sure that your database performs optimally.
In This Section
Describes how databases are used to represent, manage, and access data. Includes designing, implementing, and maintaining databases.
Federated Database Servers
Describes design guidelines and considerations for implementing a federated database tier.
Describes how tables are used to store rows of data and define the relationships between multiple tables.
Describes how indexes are used to increase the speed of accessing data in the table.
Partitioned Tables and Indexes
Describes how partitioning can make large tables and indexes more manageable and scalable.
Describes views and their usefulness in providing an alternative way of looking at data in one or more tables.
Assemblies (Database Engine)
Describes how assemblies are used in SQL Server to deploy functions, stored procedures, triggers, user-defined aggregates, and user-defined types that are written in one of the managed code languages hosted by the Microsoft .NET Framework common language runtime (CLR), and not written in Transact-SQL.
Describes how a synonym can be used to reference a base object. A synonym is another name for a schema-contained object.
Designing and Implementing Structured Storage How-to Topics
Contains procedure topics for various database tasks.