Instance.Drop Method (String, String, String, String, Boolean)

  • Article

Deletes the instance of Notification Services using SQL Server Authentication. Also provides an option to attempt to force the closure of any open connections to the instance and application databases.

Namespace: Microsoft.SqlServer.Management.Nmo
Assembly: Microsoft.SqlServer.Smo (in microsoft.sqlserver.smo.dll)

Syntax

'Declaration
Public Shared Sub Drop ( _
    serverName As String, _
    instanceName As String, _
    sqlUserName As String, _
    sqlPassword As String, _
    forceDelete As Boolean _
)

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

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

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

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

Parameters

  • serverName
    The name of the Database Engine instance that hosts the Notification Services instance.
  • instanceName
    The name of the Notification Services instance to delete.
  • sqlUserName
    A SQL Server Authentication login used to connect to the Database Engine and delete the instance and application objects.
  • sqlPassword
    The password for sqlUserName.
  • forceDelete
    true to force the closure of open database connections; otherwise, false

Remarks

The sqlUsername account 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.

Thread Safety

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.

Platforms

Development Platforms

For a list of the supported platforms, see Hardware and Software Requirements for Installing SQL Server 2005.

Target Platforms

For a list of the supported platforms, see Hardware and Software Requirements for Installing SQL Server 2005.

See Also

Reference

Instance Class
Instance Members
Microsoft.SqlServer.Management.Nmo Namespace
UnregisterLocal

Other Resources

Starting and Stopping Instances of Notification Services
Deleting Instances of Notification Services