Hi Gaurav,

I would suggest to install the services on the DR instances with a DB user having the required permissions. Afterwards you can stop the services and start them in case of DR. You can also uncheck the “start services automatically” flag in the installer to avoid auto-startup after e.g. VM reboots.

Best regards
Roman

Thanks Roman. We already have a user but database team says that since this is a disaster recovery system, the databases in DR are passive only(ready only) and technically they can’t be written in any condition. So, need to find a way to install PSO. May be give permission to the user during installation only and then revoke it later.

You require a DB user with db_owner role to deploy the PSO tables / install the system. You can refer also to the Installation Guide:
 

As you can see the DB user will also require at least db_writer role afterwards.A read-only DB user will not work and will cause system errors, if the services will be running. Of course, you can stop the services and only run them in a disaster scenario but in that case it makes sense to leave the DB connection string with the above mentioned db user permissions. Otherwise you will have to reconfigure first, which will cost time.

Best regards
Roman 

Thanks Roman for the comprehensive answer. Will discuss it with the database team regarding the mandatory conditions to install PSO.