• Artikel

SqlAssembly-Klasse

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

Namespace:  Microsoft.SqlServer.Management.Smo
Assembly:  Microsoft.SqlServer.Smo (in Microsoft.SqlServer.Smo.dll)

Syntax

'Declaration
Public NotInheritable Class SqlAssembly _
    Inherits ScriptNameObjectBase _
    Implements IObjectPermission, IAlterable, IDroppable, IExtendedProperties,  _
    IScriptable
'Usage
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

Hinweise

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

Alle öffentlichen, statischen Elemente dieses Typs (Shared in Microsoft Visual Basic) sind für Vorgänge mit mehreren Threads sicher. Für Instanzelemente kann nicht sichergestellt werden, dass sie für Threads sicher sind.

Beispiele

Skripterstellung

Threadsicherheit

Alle öffentlichen static (Shared in Visual Basic) Member dieses Typs sind threadsicher. Bei Instanzmembern ist die Threadsicherheit nicht gewährleistet.