Partager via


Classe SqlAssembly

The SqlAssembly class represents an assembly in the Microsoft .NET environment.

Espace de noms :  Microsoft.SqlServer.Management.Smo
Assembly :  Microsoft.SqlServer.Smo (dans Microsoft.SqlServer.Smo.dll)

Syntaxe

'Déclaration
Public NotInheritable Class SqlAssembly _
    Inherits ScriptNameObjectBase _
    Implements IObjectPermission, IAlterable, IDroppable, IExtendedProperties,  _
    IScriptable
'Utilisation
Dim instance As SqlAssembly
public sealed class SqlAssembly : ScriptNameObjectBase, 
    IObjectPermission, IAlterable, IDroppable, IExtendedProperties, IScriptable
public ref class SqlAssembly sealed : public ScriptNameObjectBase, 
    IObjectPermission, IAlterable, IDroppable, IExtendedProperties, IScriptable
[<SealedAttribute>]
type SqlAssembly =  
    class
        inherit ScriptNameObjectBase
        interface IObjectPermission
        interface IAlterable
        interface IDroppable
        interface IExtendedProperties
        interface IScriptable
    end
public final class SqlAssembly extends ScriptNameObjectBase implements IObjectPermission, IAlterable, IDroppable, IExtendedProperties, IScriptable

Notes

SQL Server requires assemblies to be registered in a database before these can be used by stored procedures, user-defined functions, triggers, and user-defined data types. In SQL Server Management Objects (SMO), the SqlAssembly object provides programmatic access to the assembly.

To get SqlAssembly object permissions, users can be a member of the public fixed server role.

To set SqlAssembly object permissions, users must have ALTER permission on the assembly.

To create an assembly, users must have CREATE ASSEMBLY permission on the database or be a member of the db_owner fixed database role.

To drop an assembly, users must have CONTROL permission on the assembly.

To grant, deny, or revoke permission to other users on the assembly, users must have CONTROL permission on the assembly.

Thread Safety

Tout membre statique public (Partagé dans Microsoft Visual Basic) de ce type est sûr dans le cadre des opérations à plusieurs threads. Tous les membres de l'instance ne sont pas garantis comme sûrs.

Sécurité des threads

Tous les membres publics static (Shared dans Visual Basic) de ce type sont thread-safe. Il n'est pas garanti que les membres d'instance soient thread-safe.