> OctoPerf Enterprise Edition - Migration from 11.x.x to 12.0.x.

Source: https://api.octoperf.com/doc/on-premise-infra/migration/11.x.x-to-12.0.x/

# 11.x.x to 12.0.x

A database migration is performed on `octoperf_users` indice. This migration is automatically handled by the server after startup. Starting from OctoPerf `12.0.0`, a [PostgreSQL](https://www.postgresql.org/) database is required (along with [Elasticsearch](https://www.elastic.co/elasticsearch/)) by the test scheduler.

Various settings (defined in `application.yml`) have been updated / added:

- Database settings:

```yaml
elasticsearch:
  indices:
    prefix: octoperf_
    include_type_name: true # not used anymore
```

`include_type_name` can be safely removed if present within your configuration.

- Default Test Scheduler database settings:

```yaml
spring:
  datasource:
    url: "jdbc:postgresql://postgres/postgres"
    username: "postgres"
    password: "postgres"
  quartz:
    job-store-type: jdbc
    jdbc:
      initialize-schema: always
      schema: "classpath:tables_@@platform@@.sql"
    properties:
      org.quartz.scheduler:
        instanceId: AUTO
        instanceIdGenerator.class: "org.quartz.simpl.HostnameInstanceIdGenerator"
      org.quartz.jobStore:
        isClustered: true
        driverDelegateClass: "org.quartz.impl.jdbcjobstore.PostgreSQLDelegate"
```

By default, the test scheduler is configured to use a PostgreSQL database with hostname `postgres`, with database `postgres`, username `postgres` and password `postgres`. The database schema is initialized automatically when starting OctoPerf On Premise Infra server.