Designing and Creating Databases
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 Microsoft 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.
Topic | Description |
---|---|
Describes how databases are used to represent, manage, and access data. Includes designing, implementing, and maintaining databases. |
|
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. |
|
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. |
|
Describes how these Transact-SQL programs centralize business rules, tasks, and processes within the server. |
|
Describes the function of DML triggers as special types of stored procedures executed only when data in a table is modified. |
|
Describes the function of DDL Triggers as a special kind of trigger that fires in response to Data Definition Language (DDL) statements. |
|
Describes logon triggers, which fire in response to the LOGON event. |
|
Describes event notifications as a special kind of database object that can send information about server and database events to a service broker. |
|
Describes how functions are used to centralize tasks and processes within the server |
|
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. |