Microsoft for Outlook: Transitioning from Microsoft SQL Server to MySQL Community Server

Document created by user.oxriBaJeN4 Employee on Sep 4, 2015Last modified by user.oxriBaJeN4 Employee on Oct 10, 2016
Version 2Show Document
  • View in full screen mode

This article applies to customers with existing multi user deployments of Mimecast for Outlook (v5.1 to v5.2) who are upgrading to a later version.


MySQL Community Server provides a cost effective database platform for use with multi user installations of Mimecast for Outlook. This is especially true where customers would otherwise not have cause to use Microsoft SQL Server.


What You'll Need


  • Mimecast for Outlook v5.3 or higher
  • Mimecast for Outlook Configuration Tool v5.3 or higher
  • MySQL Installer - Community Server v5.6.21 or higher
  • MySQL Workbench 6.2 CE

    The MySQL Community Server connector must be configured before commencing the installation of Mimecast for Outlook.



During the migration, we recommend operating the Microsoft SQL Server and MySQL server in parallel, until the multi user environment is fully upgraded to Mimecast for Outlook 5.3. This ensures the availability of Mimecast for Outlook to the end users, and provides a streamlined administrator experience. Information outlined in this article follows this approach.


When installing MySQL Community Server, carefully consider the following points:

  1. Choose a suitable server on which to install MySQL Server.
  2. If the host is dedicated to running MySQL Community Server, select Dedicated Machine as the Config Type (recommended option). Alternatively select the Server Machine option as the Config Type, where MySQL Server is expected to co-exist with server applications on the same host.
  3. Ensure the root password at the time of configuring adheres to your organization's password policy. The root password should to be stored in a secure location, and will be required to create the Database Login and Database for the Mimecast for Outlook add in later on.




Step 1: Installing MySQL Community Server


  1. Download and install MySQL Server. Use the relevant instructions relating to your specific version of MySQL.


Step 2: Configuring MySQL for Client Connections


Once MySQL Server has been installed, you will need to configure it to allow client connections from the network. By default MySQL Server will only allow local connections (i.e. connections originating from the local machine).

  1. Install MySQL Workbench.
  2. Connect to your local instance of MySQL Server.
  3. Click on the Server | User Privileges menu entry.
  4. Click on the Add Account button.
  5. Complete the dialog as follows:

    Field / OptionValue
    Login NameRoot
    Limit to Hosts Matching%
    PasswordEnter the root password.
    Confirm PasswordEnter the root password.
  6. Click the Apply button.
  7. Close MySQL Workbench.



Step 3: Configuring Mimecast for Outlook


To configure Mimecast for Outlook:

  1. Download and open the Mimecast for Outlook Configuration Tool.
  2. Click the File | Open menu item and load the Mimecast for Outlook installation MSI.
  3. Navigate to the SQL Settings section of the tool.
  4. Select the following options:
    • Override
    • Customize SQL Settings
  5. Change the Database Provider dropdown to "MySQL". 
  6. Customize the the Mimecast for Outlook installer as required.
  7. Click the File | Save As menu item to save the customized package.


Further information regarding customizing the installer can be found in the Mimecast for Outlook Configuration Tool article.


Step 4: Deploying the Mimecast for Outlook Clients to Use MySQL Community Server


To transition from Mimecast for Outlook with a Microsoft SQL Server database backend, to Mimecast for Outlook with a MySQL Community Server backend:

  1. Deploy the customized installer for Mimecast for Outlook created in Step 3, using your preferred deployment technology.
  2. Test that data is populated into the database when client machines connect.
    1. Open MySQL Workbench.
    2. Navigate to the relevant Schema.
    3. Query the useroption table and validate that the table contains data.


Next Steps


Once the deployment is complete the Microsoft SQL Server environment may be decommissioned.