Installing SQL Server

Before you install MiVoice AnalyticsMiContact Center Business, you must install SQL Server 2014/ 2016/ 2017/ 2019 Express. If you need full version of SQL to be installed onto a remote server, see the System Engineering Guide. Your SQL Server version must include Management Tools (available as a separate download for SQL Server 2016/ 2017/ 2019 Express Edition).

Before installing SQL Server, you must configure the appropriate default collation settings. See the following Mitel Knowledge Base article for details: https://mitel.custhelp.com/app/answers/answer_view/a_id/1000779/loc/en_US.

Note:

You can download SQL Server Express Editions free from the Microsoft website.

Note:

You must install BluStar server for Line State monitoring.

Adding SQL Server security roles to the administrative account

In order to properly create and configure databases, the administrative account being used to install MiContact Center BusinessMiVoice Analytics must have the dbcreator role on the SQL server.

If you have installed SQL Server 2014/ 2016/ 2017/ 2019 Express (or a full version of SQL Server 2014/ 2016/ 2017/ 2019), you must also verify that the NT AUTHORITY\SYSTEM server role also has these permissions. For more information, see the following KB article: https://mitel.custhelp.com/app/answers/answer_view/a_id/1002628/loc/en_US.

Note:
If you do not want the administrative account being used to install MiContact Center BusinessMiVoice Analytics to be configured with those SQL permissions, there are two alternatives:
  • Add the local system account as dbcreator.
  • Set the following services, application pools, and local databases to run under the identity account:
    • Services:
      • MiContact Center Media Router
      • MiContact Center Mass Transit Runtime
    • Application Pool:
      • CCMWa
    • Local databases:
      • CCMRouting
      • CCMRuntimeServices
      • Ccmwa

SQL Server best practices

If you are installing SQL Server 2014/ 2016/ 2017/ 2019 Express (or a full version of SQL Server 2014/ 2016/ 2017/ 2019), ensure you follow these best practices: