Access Rights for Post Prognosis Advanced Reporting Deployment
Access Rights Required After Deploying Prognosis Reporting Advanced:
This User (or Service Account) will be used to run ETLs through the proxy account.
It will be used to create tables, stored procedures, functions, etc.
It will also be used to connect Prognosis to SQL Server Staging tables and feed data via the ODBC connection.
For SQL Database Server: The User (or Service Account) needs to be able to logon to the SQL Server and have db_owner rights to the two SQL Server Databases: BigDataInsightUC and BigDataInsightUCSource.
For SSIS Server: it should be allowed to logon to the SQL Server. This will run the SQL Server Agent.
The User (or Service Account) does not need to log onto the SSRS Server. It does need to have Content Manager permissions after everything is configured and set up by the SQL team. In summary, the User (or Service Account) will not need to have logon rights to any servers apart from the Prognosis Insight (Management) server.
If a separate reporter AD account is needed, the DBA will need to provide this user account the following permissions on BigDataInsightUC database: db_datareader and public.
A separate reporter AD account will also need to have Content Manager permissions on the SSRS server.