Why does RRDI need an OS-level Administrator account on a database server?
We are planning an enterprise installation with RRDI, and have noticed that some instructions for the pre-setup tasks involve having an account that is an operating system level Administrator on the DB server. I know that there is some file access done during the setup and usage, but could we not simply create a non-administrative user who can access those file locations and the database?
For security reasons our client does not want to create a full system administrator account for RRDI to have on the database server. The DB server and application server are separate. I seem to remember having done previous installations of RRDI using just SQL Server accounts, and setting the WebSphere instance with RRDI up as a service. Am I mistaken?
2 answers
One thing I have experienced, is that the initial setup needs an ID with sufficient authority on the server hosting the data warehouse database. Operationally, however, the ID used to connect to the warehouse is not the same, rather a much less capable ID ( connect, select authorities ), and the warehouse is catalogged to a local (to the RRDI server) database.
To setup the RRDI configuration database requires the ID that owns the database instance and must have the authority to create databases, connect, create tables, etc.
To setup the RRDI configuration database requires the ID that owns the database instance and must have the authority to create databases, connect, create tables, etc.