Skip to main content
F
FrankArthurIII
Participant
July 14, 2011
Answered

level of permission on database account

  • July 14, 2011
  • 1 reply
  • 712 views

Hi All!

About to install RoboHelp Server 8.

We've created a SQL database and a RoboHelp username and password for that database.

For the install of RoboHelp Server 8 I'm assuming the db account needs DBO permissions (full owner).

Our DBA group however does not like leaving accounts with DBO permission.

After install can the level of permission for the database account be lowered? to say modify or read/write?

Thanks for the info!

Frank

This topic has been closed for replies.
Correct answer RoboColum_n_

Hi Frank and welcome to the RH forums.

When you first start the RHS it is not connected to the DB. You have to specify logon details for a user with full admin rights. This is used to create an Admin group and user complete with various permissions so the admin rights are definitely used there. You'd then be creating other users, groups, permissions requiring admin rights on the logon.

Perhaps (I'm not sure) that you could get away with read/write access if all you were doing was maintaining areas, running reports, etc. However you'd have to get admin rights each time you need to create/amend/delete users or contexts. Personally I wouldn't have thought it was worth the hassle.

If you go back to your DBA and remind them that only you has access to the Config Manager where the DB security can be compromised, would this appease them?

  The RoboColum(n)   @robocolumn   Colum McAndrew

1 reply

RoboColum_n_
RoboColum_n_Correct answer
Legend
July 14, 2011

Hi Frank and welcome to the RH forums.

When you first start the RHS it is not connected to the DB. You have to specify logon details for a user with full admin rights. This is used to create an Admin group and user complete with various permissions so the admin rights are definitely used there. You'd then be creating other users, groups, permissions requiring admin rights on the logon.

Perhaps (I'm not sure) that you could get away with read/write access if all you were doing was maintaining areas, running reports, etc. However you'd have to get admin rights each time you need to create/amend/delete users or contexts. Personally I wouldn't have thought it was worth the hassle.

If you go back to your DBA and remind them that only you has access to the Config Manager where the DB security can be compromised, would this appease them?

  The RoboColum(n)   @robocolumn   Colum McAndrew
F
FrankArthurIIIAuthor
Participant
July 14, 2011

Colum, Great info on the what functions require different db rights. Thanks!

Frank

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices