|
Database Permissions |
  
|
|
Database Permissions |
|
SpaceObServer stores scanned file system information in a backend database. To communicate with the database you can use the "Windows Authentication" (for Microsoft database systems only) or the "SQL Server Authentication". In both cases the used login needs sufficient permissions on the database. This section shows which kind of permissions you need to ensure the correct work of SpaceObServer.
Note: This section was written for database administrators, so the content is quite technical.
Since SpaceObServer can be used with many different kind of databases with different names of permissions, we are using our own types of permissions here.
We split the needed database permissions in 4 types:
Select permission |
The permission to execute SELECT statements on the connected database. |
Update permission |
The permission to execute UPDATE statements on existing tables in the connected database. |
Insert permission |
The permission to execute INSERT statements on existing tables in the connected database. |
Create permission |
The permission to create new tables, foreign keys, stored procedures and indexes in the connected database. |
The following table shows what kind of permissions your SpaceObServer application needs:
SpaceObServer |
Select permission; Update permission; Insert permission; Create permissions |
SpaceObServer Remote Client (remote scan configuration) |
Select permission; Update permission; Insert permission (only needed when adding new scans) |
SpaceObServer Remote Client (remote reporting only) |
Select permission |
Note: When using "Windows Authentication" and a specified logon for the SpaceObServer Agent (See SpaceObServer Agent) the user interface and the agent could have different permissions. In this case the user interface needs the at least the permissions of the SpaceObServer Remote Client. The SpaceObServer Agent always need the full permissions.
MS SQL Server: When using an MS SQL Server ensure that the default schema of the database user account is "dbo". Otherwise this could cause visibility issues when using multiple user accounts.