Configure Platform Analytics to Use a Different Repository Database Name

Platform Analytics is configured with a PostgreSQL database and schema named platform_analytics_wh out-of-the-box. It is possible to configure Platform Analytics to use a different database as long as the schema is named platform_analytics_wh.

Connect to your PostgreSQL instance.
Create a user. If the mstr and mstr_pa users already exist from the MicroStrategy installation, skip this step.
Copy
```
CREATE USER mstr_pa WITH ENCRYPTED PASSWORD '<password>' NOSUPERUSER CREATEDB;
```

Create the Database and Grant Database privileges:

Copy

CREATE DATABASE YOUR_DATABASE_NAME;
GRANT ALL ON DATABASE YOUR_DATABASE_NAME TO mstr_pa;

Update the pg_hba.conf file, if necessary:

Copy

host YOUR_DATABASE_NAME mstr_pa 127.0.0.1/32 password
host YOUR_DATABASE_NAME mstr_pa ::1/128 password
host YOUR_DATABASE_NAME mstr_pa samenet password

Open the PAConsumerConfig.yaml file and update pgWhDb and any other necessary fields.

Copy

whDbType: postgresql
…
pgWarehouseDbConnection:
    pgWhHost: YOUR_HOST
    pgWhUser: mstr_pa
    pgWhPasswd: YOUR_PASSWORD
    pgWhPort: 5432
    pgWhDb: YOUR_DATABASE_NAME

Start populating the Platform Analytics repository by running platform-analytics-custom-install.

Windows: platform-analytics-custom-install.bat -o install

Linux: ./platform-analytics-custom-install.sh -o install
Check the etl_pa_version table. The DDLs and procedures should match the latest version.
Copy
```
SELECT * FROM etl_pa_version;
```

Grant the required schema privileges and alter roles:

Copy

GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA platform_analytics_wh to mstr_pa;
ALTER ROLE mstr_pa in DATABASE YOUR_DATABASE_NAME SET search_path to platform_analytics_wh;

Update the DSN used for Platform Analytics by changing the database in the DSN to the one you created.