Instance.Drop Method (String, String, Boolean)

Artículo
12/15/2008

Deletes the named instance of Notification Services on the specified server. Also provides an option to attempt to force the closure of any open connections to the instance and application databases.

Espacio de nombres: Microsoft.SqlServer.Management.Nmo
Ensamblado: Microsoft.SqlServer.Smo (in microsoft.sqlserver.smo.dll)

Sintaxis

'Declaración
Public Shared Sub Drop ( _
    serverName As String, _
    instanceName As String, _
    forceDelete As Boolean _
)

public static void Drop (
    string serverName,
    string instanceName,
    bool forceDelete
)

public:
static void Drop (
    String^ serverName, 
    String^ instanceName, 
    bool forceDelete
)

public static void Drop (
    String serverName, 
    String instanceName, 
    boolean forceDelete
)

public static function Drop (
    serverName : String, 
    instanceName : String, 
    forceDelete : boolean
)

Parámetros

serverName
The name of the Database Engine (Motor de base de datos) instance that hosts the Notification Services instance.

instanceName
The name of the Notification Services instance to delete.

forceDelete
true to force the closure of open database connections; otherwise, false

Notas

The account used to drop the instance must have permission to drop databases. This includes membership in the dbcreator or sysadmin fixed server role.

When you delete an instance of Notification Services, you delete the database objects for the instance and its applications. If Notification Services created the databases, the databases are deleted. Otherwise, only the objects created by Notification Services in the instance and application schemas are deleted.

After you delete an instance, you should also unregister the instance, unless you are going to recreate the instance and want to use the same registry information.

Deleting the instance when some databases have open connections can leave the instance in an inconsistent state.

Make sure to stop the Notification Services engine components before deleting the instance.

Seguridad para subprocesos

Any public static (Shared in Microsoft Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.