| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | |||
|---|---|---|---|---|---|---|---|---|---|---|---|
Assemblies (Database Engine) |
A SQL Server instance can host assemblies that deploy functions, procedures, triggers, and user-defined aggregates and types written in a CLR language. |
rwestMSFT |
randolphwest |
12/27/2024 |
sql |
clr |
reference |
|
[!INCLUDE SQL Server]
The articles in this section provide information to help you understand, design, and implement assemblies.
Assemblies are DLL files used in an instance of [!INCLUDE ssNoVersion] to deploy functions, stored procedures, triggers, user-defined aggregates, and user-defined types. Assemblies are written in one of the managed code languages hosted by the [!INCLUDE dnprdnshort] common language runtime (CLR), instead of in [!INCLUDE tsql].
An assembly in [!INCLUDE ssNoVersion] is an object that references a managed application module (.dll file) that was created in the [!INCLUDE dnprdnshort] common language runtime. An assembly contains class metadata and managed code. Uploading an assembly to an instance of SQL Server is the first step toward creating any of the following database objects:
-
CLR functions. For more information, see Create CLR functions.
-
CLR stored procedures. For more information, see CLR stored procedures.
-
CLR triggers. For more information, see Create CLR triggers.
-
User-defined aggregate functions. For more information, see Create user-defined aggregates.
-
User-defined types. For more information, see Using User-Defined Types in SQL Server Native Client.
Assemblies perform the following functions in [!INCLUDE ssNoVersion]:
-
Contain the managed code that runs the functionality of one or more of the CLR database objects previously listed.
-
Contain metadata that includes the version number and culture of the assembly, an optional public key that uniquely identifies the list of classes of the assembly, the methods that are defined in the assembly, and the processor architecture of the assembly.
-
Manage the degree to which managed code can access outside resources by regulating code access permissions.
-
Contain metadata about dependencies on other assemblies referenced by the assembly.
| Article | Description |
|---|---|
| Design assemblies | Explains what you have to consider before creating an assembly. This includes packaging assemblies, code access permissions, and other restrictions. |
| Implement assemblies | Explains how to create and drop assemblies, how and when to modify assemblies, and how to retrieve metadata about assemblies. |
| Get information about assemblies | Lists the catalog views and functions that can be queried for metadata about assemblies. |