When working with a local installation of RockSolid it is necessary to configure users of the SQL Server application to have login access to the SQL Server application. This is because RockSolid maintains the security context of the authenticating user at all tiers in the application stack, and does not use the security context of a middle tier user account. This method provides a higher level of security where access to the information within the RockSolid repositories is controlled at all levels.
NOTE: This article is discussing user login access required for the central RockSolid application SQL Server instance. This is in no way related to what permissions RockSolid requires to monitor SQL Server instances deployed within your environment.
Configuring SQL Server Login Access for RockSolid Users
Typically users requiring login access to RockSolid are added to a Windows Group for the purpose of easing administration. Once configured, this Windows Group must be configured as a SQL Server login to the central RockSolid application repository instance.
This Windows Groups is required to be associated with a database user within the following databases:
No other database level role assignment is required other than membership of the default public database role.
Configuring SQL Server Reporting Services Access for RockSolid Users
The same windows group login specified above also requires access to the SQL Server reporting services instance associated with the RockSolid application. The group associate with users of the RockSolid application only requires the Reporting Services System User role in order to execute RockSolid application reports. For more information view:
NOTE: Granting group membership to SQL Server does not automatically give members access to the RockSolid application. RockSolid application users will still require RockSolid users to be create via the RockSolid console before they can use the RockSolid application. Click here more information.