Database Server Requirements and Considerations

  • Windows OS version installed with all updates.

  • Proper version of 64-bit Microsoft SQL Server installed with all updates applied. SQL Server Enterprise Edition or versions beyond SQL Server Standard 2017 are recommended for larger, more complicated deployments due to support for table partitioning.

    • Required Components:

      • Database Engine

      • Management Tools

  • High Performance Power Plan has been enabled.

  • Verify that the Microsoft SQL Server Database Server has the recommended amount of free disk space available and room to grow overtime.

  • Update the SQL Server Database Transaction Log to grow by file size and not by percentage.   OneStream recommends setting the growth to grow in 100 MB Increments.

  • To enhance performance over time in the Application Databases, OneStream recommends re-indexing the Application Databases periodically.

  • Sizing is based on Customer Data Center Specs for CPU and Memory.

  • Authentication and Rights

    • Windows Integrated vs. SQL Server Native:

      • Use Native SQL Server Service Account instead of a Windows Integrated Account for the database to ensure fast connection and reduce network traffic for our hundreds of connections to the database.

      • If using Windows Integrated Security for SQL, the service account used in IIS will be the Database Account.

    • The OneStream Database account needs admin rights to the Master database in SQL Server in order for the administrator to be able to create new databases via the OneStream Database Configuration Utility.

    • The OneStream Database account should be given full user rights to Public and Sysadmin under Roles in SQL server.

  • Backup / Recovery

    • All critical information is stored in the Framework and Application databases.

    • Verify that the SQL Server Database for the OneStream Framework and Applications are backed up per company backup policy.  OneStream recommends a minimum of daily backups for the Application and Framework Databases.  This can be handled by creating a SQL Server Maintenance Plan using the New Maintenance Plan wizard in SQL Server Management Studio. It is recommended to also backup Framework and Application databases used for development and test purposes, especially during initial build-out.

    • Verify that the SQL Server Database Transaction Logs are backed up on a regular basis in conjunction with the databases to avoid the Transaction Log growing to a full state.