Install-CsDatabase

Syntax

Install-CsDatabase
       [-CentralManagementDatabase]
       [-Clean]
       [-Collocated]
       [-DatabasePaths <String[]>]
       [-GlobalCatalog <Fqdn>]
       [-GlobalSettingsDomainController <Fqdn>]
       [-SkipPrepareCheck]
       [-SqlInstanceName <String>]
       -SqlServerFqdn <Fqdn>
       [-Update]
       [-UseDefaultSqlPaths]
       [-Force]
       [-Report <String>]
       [-WhatIf]
       [-Confirm]
       [-Backup]
       [-DatabasePathMap <Hashtable>]
       [-NoReindex]
       [<CommonParameters>]

Install-CsDatabase
       [-Clean]
       [-Collocated]
       [-DatabasePaths <String[]>]
       -DatabaseType <DatabaseNameType>
       [-GlobalCatalog <Fqdn>]
       [-GlobalSettingsDomainController <Fqdn>]
       [-SkipPrepareCheck]
       [-SqlInstanceName <String>]
       -SqlServerFqdn <Fqdn>
       [-Update]
       [-UseDefaultSqlPaths]
       [-Force]
       [-Report <String>]
       [-WhatIf]
       [-Confirm]
       [-DatabasePathMap <Hashtable>]
       [-NoReindex]
       [<CommonParameters>]

Install-CsDatabase
       [-Clean]
       [-ConfiguredDatabases]
       [-DatabasePaths <String[]>]
       [-ExcludeCollocatedStores]
       [-ForDefaultInstance]
       [-ForInstance <String>]
       [-GlobalCatalog <Fqdn>]
       [-GlobalSettingsDomainController <Fqdn>]
       [-SkipPrepareCheck]
       -SqlServerFqdn <Fqdn>
       [-Update]
       [-UseDefaultSqlPaths]
       [-Force]
       [-Report <String>]
       [-WhatIf]
       [-Confirm]
       [-DatabasePathMap <Hashtable>]
       [-NoReindex]
       [<CommonParameters>]

Install-CsDatabase
       [-Clean]
       [-DatabasePaths <String[]>]
       [-ForDefaultInstance]
       [-ForInstance <String>]
       [-GlobalCatalog <Fqdn>]
       [-GlobalSettingsDomainController <Fqdn>]
       [-LocalDatabases]
       [-SkipPrepareCheck]
       [-Update]
       [-UseDefaultSqlPaths]
       [-Force]
       [-Report <String>]
       [-WhatIf]
       [-Confirm]
       [-DatabasePathMap <Hashtable>]
       [-NoReindex]
       [<CommonParameters>]

Description

Skype for Business Server makes extensive use of SQL Server databases, ranging from the Central Management store to the Archiving database. As a general rule, these databases are set up at the same time you Skype for Business Server or at the same time you install a Skype for Business Server role (such as Monitoring Server) that requires a database back end. After installation has taken place these databases typically will not need to be reinstalled or moved to new locations.

On rare occasions, however, you might need to manually install a Skype for Business Server database; this could be because you need to move a database to another server, or because a setup-related problem failed to install the database for you. The Install-CsDatabase cmdlet provides a way for you to install any of the SQL Server databases used by Skype for Business Server.

When running the Install-CsDatabase cmdlet there are basically three different ways to handle the configuration of the database being installed:

Option 1 -- Run the cmdlet without including a parameter that specifies the database paths. When the Install-CsDatabase cmdlet is run without the DatabasePaths or the UseDefaultSqlPath parameter the cmdlet uses a built-on algorithm to choose the storage location for the database logs and data files. Note that this built-in algorithm works with a stand-alone SQL Server, it will not work with a SQL Server cluster. To install a database on a SQL Server cluster your command must include either the DatabasePaths or the UseDefaultSqlPath parameter

Option 2 -- Run the cmdlet along with the DatabasePaths parameter. When the Install-CsDatabase is cmdlet run with the DatabasePaths parameter the built-in algorithm is not used to choose the storage location for the database logs and data files. Instead, administrators can select the location for these logs and data files. To install both data files and SQL Server logs in the same location, simply specify the path to the folder where this data should be stored. For example:

-DatabasePaths C:\SqlData

To store data files in one location and log files in a second location, specify the path to each folder, separating the two locations by using a comma (be careful not to put a blank space before or after the comma):

-DatabasePaths C:\SqlLogs,D:\SqlData

The log files will always be stored on the first location specified, while data files will be stored in the second location.

In a pool backend, certain log files might be stored on a drive all by themselves. If you have a pool backend with a single drive, files will be distributed like this:

Drive 1 - Rtcdyn log; Rtc log; other logs; other data.

If you have two drives, files will be distributed like this:

Drive 1 - Rtcdyn log; Rtc log.

Drive 2 - Other logs; other data.

With three drives:

Drive 1 - Rtcdyn log.

Drive 2 - Rtc log.

Drive 3 - Other logs; other data.

And with four drives:

Drive 1 - Rtcdyn log.

Drive 2 - Rtc log.

Drive 3 - Other logs.

Drive 4 - Other data.

Option 3 -- Run the cmdlet along with the UseDefaultSqlPaths parameter. When the Install-CsDatabase cmdlet is run using the UseDefaultSqlPaths parameter, the built-in algorithm is not used to choose the storage locations for the database logs and data files. Instead, log and data files are stored in the locations specified by the SQL Server defaults path (these paths must be configured in advanced by a SQL Server administrator). Data files will be stored in the default SQL Server data file location while log files will be stored in the default SQL Server log file location.

Before running the Install-CsDatabase cmdlet you should make sure that the RTCUniversalServerAdmins groups has not been assigned as the database owner. If that group is listed as the owner the group could possibly be deleted when you call the Install-CsDatabase cmdlet.

Examples

-------------------------- EXAMPLE 1 --------------------------

Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn atl-sql-001.litwareinc.com -DatabasePaths "E:\CSLog","F:\CSLog","G:\CSDB"

In Example 1, the Install-CsDatabase cmdlet reads in the Skype for Business Server topology, and then installs any required databases on the pool atl-sql-001.litwareinc.com.

-------------------------- EXAMPLE 2 --------------------------

Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn atl-sql-001.litwareinc.com -SqlInstanceName rtc -DatabasePaths "G:\CSDB"

The command shown in Example 2 installs the Central Management store on the pool atl-sql-001.litwareinc.com. The database will be installed in the rtc instance, and make use of the folder G:\CSDB.

Parameters

-Backup

-CentralManagementDatabase

-Clean

-Collocated

-ConfiguredDatabases

-Confirm

-DatabasePathMap

-DatabasePaths

-DatabaseType

-ExcludeCollocatedStores

-Force

-ForDefaultInstance

-ForInstance

-GlobalCatalog

-GlobalSettingsDomainController

-LocalDatabases

-NoReindex

-Report

-SkipPrepareCheck

-SqlInstanceName

-SqlServerFqdn

-Update

-UseDefaultSqlPaths

-WhatIf

Inputs

None. The Install-CsDatabase cmdlet does not accept pipelined input.

Outputs

The Install-CsDatabase cmdlet does not return any values or objects.

Related Links

• Uninstall-CsDatabase