Database - Installation guide

Owned by Morten Lindequist Køhler
Last updated: Apr 29, 2024 by Anders Winther Thorndahl
4 min read

Install Perfion database

The Perfion database requires a running SQL Server before you can install it. Follow these steps to install a Perfion database.

Important: Upgrading after 5.2.0, the SqlServer must be be using a default collation that is CI (CaseInsensitve) - DBinstaller will nok work if master/temp DB is CS (Case Sensitive). If you have an installation that default IS CS, you will have to create a new name instance of sqlserver that is CI.

Download installation file

  1. Download the most recent Database Installer from the Perfion knowledge base - Perfion Database Installer - Latest Version - Perfion Knowledge Base - Perfion Knowledge Base (atlassian.net)

  2. Extract all files from the zip-file and place them in a dedicated folder (e.g., c:\Perfion\Database)

  3. Run Perfion.DBInstaller.exe for a wizard guided installation or Perfion.DBInstaller.CommandLine.exe /help to install via a commandline/script

Install the Perfion database

Run the Perfion database installer setup package and choose ‘Install new database'

Connection

On the connection page, you setup the Microsoft SQL Server instance on which you want to install the new Perfion database and Windows Authentication or SQL Server Authentication depending on your setup. The user must be able to install a database on the specified SQL server.

Enter the name you want to use for the new Perfion database and click Next.

Database properties

On the database properties page, you can specify additional details about collation name, recovery model and the location of the SQL Server data- and log files for the database. In a standard setup all options can be left unchanged.

NOTE: Perfion requires a case insensitive (CI) collation. If your server default is case sensitive (CS) you have to choose a specific case insensitive collation name in this dialog (e.g Latin1_General_CI_AI)

Demo data

On the next dialog, you can choose if you want to install demo data. Click Next when you have made your selection.

Scheduled tasks

On the next dialog, you can choose whether or not to enable scheduled tasks for automatically updating the system license and database statistics and index maintenance. The scheduled tasks are created within the Perfion Scheduler and may be updated after installation. Default Values are once per week. On large installations or if running lot’s of import we recommend the schedule runs once per day.

Summary

The summary dialog now appears with a summary of the chosen installation options. If you are satisfied with the chosen installation options check I am sure I want to setup the new database option and click Next. This will start the actual installation.

You have now successfully installed the Perfion Database. Click Finish on the closing screen.

Create SQL Login and -User

As a best practice, you should create a separate SQL login that is restricted to the individual Perfion databases.

Create SQL Login

First create a SQL login (the username/password)

USE [Master] CREATE LOGIN [perfion-dbuser] WITH PASSWORD = '<strong password>' CREATE USER [perfion-dbuser] FROM LOGIN [perfion-dbuser]

Create SQL user

Once the SQL Login is created, a SQL user account can be created within the Perfion database and the account can be granted access.

Perfion currently require the database user to have Database Owner rights.

USE [<perfion database>] CREATE USER [perfion-dbuser] FROM LOGIN [perfion-dbuser] EXEC sp_addrolemember 'db_owner', 'perfion-dbuser'

Upgrading the Perfion database

The process of upgrading the Perfion database is mostly the same as when you are installing a new database. But when upgrading the Perfion database there are a few things that you should be aware of.

You should make sure that no one is actively using the database, as this can slow down the upgrade dramatically, or even corrupt database.

  • Stop the application server service

  • Stop the web client (IIS) site and application pool

  • Stop the API (IIS) site and application pool

  • Make sure all users close their Windows client

Under some circumstances the database upgrade can take a lot of time. Factors like size of the database, if you are jumping major versions, and how many versions you are jumping, all have an impact on the time it takes for the database upgrade to complete.

During the upgrade the installation wizard might become unresponsive. This does not mean that the upgrade crashed, or that it isn’t progressing. This is normal and expected behavior. It is very important not to terminate the upgrade prematurely as it will render the database corrupt.

Â