9.4 SQL Database Planning

9.4.1 Database Planning Tips and Caveats

  • TeamWorks supports the following databases:

    • PostgreSQL 9.6.x and later

    • Microsoft SQL 2008 R2 and later

    If you have a PostgreSQL or Microsoft SQL installation, Micro Focus recommends that you leverage that resource and take advantage of your existing infrastructure.

  • Ensure that the TeamWorks and Search appliances’ shared storage (the /vashare mount point) is protected by traditional clustering to provide for high availability.

  • The PostgreSQL or Microsoft SQL server and database that TeamWorks appliances access should also be protected for high availability.

9.4.2 Database Sizing

The amounts shown in “Worksheet 12 - SQL Database” are explained in Table 9-4. As noted elsewhere, you can adjust the numbers shown with green borders. Data numbers in white cells are fixed and should not be changed. Cells with black dashes are calculated based on information you entered previously and you should not modify them directly.

Table 9-4 Using Worksheet 12 - SQL Database


Recommendations and Guidelines

Planning Worksheet Example

  • / (PostgreSQL appliance)

  • 20 GB fixed


  • Database

    /vastorage on PostgreSQL appliance

Use the following guidelines when planning for the SQL database:

  • Allocate 40 GB as a starting amount.

  • Allocate 20 GB for rooms, topics, and comments.

  • Allocate 20 KB per user.

The worksheet calculates this as follows in both the SQL Database and PostgreSQL Appliance sections:

  1. It includes 40 GB as a base database amount.

  2. It adds whatever amount you have set for room, topic, and comment storage.

  3. It multiples the total number of users by 20 KB (.000020 GB).

  • /var (PostgreSQL appliance)

  • 4 GB for log files

  • Three times the RAM for core dumps.


  • CPUs

  • The default allocation at install time is 2 CPUs. However, large installations usually require 4 CPUs.

The planning worksheet reflects a large installation, so 4 CPUs are planned.

  • RAM (PostgreSQL appliance)

Use the following guidelines when planning the RAM allocation for the PostgreSQL appliance.

  • 8 GB or 8% of /vastorage, whichever is greater.

The worksheet calculates this as follows in the PostgreSQL Appliance section:

  1. It multiples the /vastorage size by .08 to get 8%.

  2. If the result is greater than 8, it displays the result. Otherwise, it displays 8.