Content Security Reporter Database Schema Version

[Abdelaziz_Salah]

We have a CSR 2.7 on ePO 5.10 update 8 and MS SQL 2017.
Our ePO & CSR share the same instance, but have separate databases; we configured the database of CSR; test status successfully connected to the report database, but the schema version not found so, initializing a connect failed and availability always shown set to offline.
Does any advice, please?

[jacek]

According to CSR Installation Guide:

You must update the database schema after upgrading Content Security Reporter, as the schema becomes out of date after the upgrade.
Before you begin
Make sure that you back up the database before updating the schema.
The database schema is the definition of tables and fields used in the Content Security Reporter database.
When Content Security Reporter detects that the database schema is out of date (such as after an upgrade), the database status is set to Offline. Schema is out of date. and an Update Schema button is provided.

Task
1 Select Menu | Configuration | Report Server Settings | Database.
2 Click Update Schema.
The database status appears as Connected.

[Abdelaziz_Salah]

Thank you for your information, but it is not the case here because it is a new implementation and we did not perform any upgrade.

Anyway, we released that our database was on a high availability group with the always-on feature enabled; so we created a new database without the always-on feature and it is connected without any issue.

A question here now, any document or KB mentioned database with always-on feature compatibility?