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.
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.