ExtendedStoredProcedure-Klasse
The ExtendedStoredProcedure object represents an extended stored procedure on the instance of Microsoft SQL Server.
Namespace: Microsoft.SqlServer.Management.Smo
Assembly: Microsoft.SqlServer.Smo (in Microsoft.SqlServer.Smo.dll)
Syntax
'Declaration
Public NotInheritable Class ExtendedStoredProcedure _
Inherits ScriptSchemaObjectBase _
Implements IObjectPermission, ICreatable, IAlterable, IDroppable, _
IExtendedProperties
'Usage
Dim instance As ExtendedStoredProcedure
public sealed class ExtendedStoredProcedure : ScriptSchemaObjectBase,
IObjectPermission, ICreatable, IAlterable, IDroppable, IExtendedProperties
public ref class ExtendedStoredProcedure sealed : public ScriptSchemaObjectBase,
IObjectPermission, ICreatable, IAlterable, IDroppable, IExtendedProperties
[<SealedAttribute>]
type ExtendedStoredProcedure =
class
inherit ScriptSchemaObjectBase
interface IObjectPermission
interface ICreatable
interface IAlterable
interface IDroppable
interface IExtendedProperties
end
public final class ExtendedStoredProcedure extends ScriptSchemaObjectBase implements IObjectPermission, ICreatable, IAlterable, IDroppable, IExtendedProperties
Hinweise
Extended stored procedures are user-defined routines in a programming language such as C that extend the functionality of SQL Server. Extended stored procedures are executed in the same way as stored procedures on an instance of SQL Server. They can be passed parameters and return values.
To get ExtendedStoredProcedure object properties, users can be a member of the public fixed server role.
To set ExtendedStoredProcedure object properties, users must have ALTER permission on the extended stored procedure, or be a member of db_owner fixed database role.
To create a extended stored procedure, users must have CREATE PROCEDURE permission on the parent database or be a member of the db_owner fixed database role.
To drop a extended stored procedure, users must have CONTROL permission on the extended stored procedure or be a member of the db_owner fixed database role.
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.
Vererbungshierarchie
System. . :: . .Object
Microsoft.SqlServer.Management.Smo. . :: . .SmoObjectBase
Microsoft.SqlServer.Management.Smo. . :: . .SqlSmoObject
Microsoft.SqlServer.Management.Smo. . :: . .NamedSmoObject
Microsoft.SqlServer.Management.Smo. . :: . .ScriptNameObjectBase
Microsoft.SqlServer.Management.Smo. . :: . .ScriptSchemaObjectBase
Microsoft.SqlServer.Management.Smo..::..ExtendedStoredProcedure
Threadsicherheit
Alle öffentlichen static (Shared in Visual Basic) Member dieses Typs sind threadsicher. Bei Instanzmembern ist die Threadsicherheit nicht gewährleistet.
Siehe auch