Deletes the specified Microsoft Communications Server 2010 database.
Syntax
add-attachmentfilterentry -Name <String> -Type <ContentType | FileName> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]] |
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
|
Role |
Optional |
String |
Communications Server database to be deleted. Database roles include ArchivingStore; MonitoringStore; UserStore; and ApplicationStore. To delete the Central Management database, use the –CentralMgmtStore rather than the –Role parameter. |
|
SqlServer |
Required |
String |
Fully qualified domain name of the computer or SQL cluster where the database is located. For example: -SqlServer atl-sql-001.litwareinc.com. |
|
InstanceName |
Optional |
String |
Name of the database instance containing the database to be removed. (A database instance is simply a set of running processes that provides access to database files.) |
|
CentralMgmtStore |
Optional |
Switch Parameter |
If present, uninstalls the Central Management database. You cannot use both –CentralMgmtStore and –Role in the same command. |
|
Detach |
Optional |
Switch Parameter |
If present, "detaches" the specified database. When a database is detached, all the file locks imposed by SQL Server are removed. This enables you to directly access the database files in order to do such things as copy those files to another computer. |
|
Report |
Optional |
String |
Enables you to specify a file path for the log file created when the cmdlet runs. For example: -Report "C:\Logs\UninstallDatabase.xml" |
|
Force |
Optional |
Switch Parameter |
If present, forces removal of the database even if that database is currently in use. |
|
WhatIf |
Optional |
Switch Parameter |
Describes what would happen if you executed the command without actually executing the command. |
|
Confirm |
Optional |
Switch Parameter |
Prompts you for confirmation before executing the command. |
Detailed Description
Microsoft Communications Server 2010 makes extensive use of SQL Server databases: configuration information is stored in the Central Management database; archiving data is stored in the Archiving database; etc. As a general rule, these databases are set up at the same time you install Communications Server or at the same time you install a Communications Server role (such as Monitoring Server) that requires a database backed. After the databases have been installed you will rarely need to uninstall them.
Of course, "rarely" does not mean "never." Although somewhat atypical, you might need to uninstall your Communications Server databases from time-to-time; this might be because you need to move a database to another server, or because a setup-related problem installed the database without correctly configuring the associated server role. Regardless of the reason, the Uninstall-CsDatabase cmdlet provides a way for you to remove (or detach) any of the SQL Server databases used by Microsoft Communications Server.
Return Types
Uninstall-CsDatabase does not return any values or objects.
Examples
-------------------------- Example 1 ------------------------
 Copy Code |
|
|---|---|
Uninstall-CsDatabase -CentralMgmtStore -SqlServer atl-sql-001.litwareinc.com |
|
The command shown in Example 1 deletes the Central Management database from the computer (or SQL Server cluster) atl-sql-001.litwareinc.com.
-------------------------- Example 2 ------------------------
| Copy Code |
|
|---|---|
Uninstall-CsDatabase -Role UserStore -SqlServer atl-sql-001.litwareinc.com |
|
In Example 2, the UserStore database is deleted from the computer (or SQL Server cluster) atl-sql-001.litwareinc.com. When you use the –Role parameter, all stores related to the specified role are deleted.