|
<< Click to Display Table of Contents >> Navigation: Options > System > Database > Database Permissions |
SpaceObServer stores scanned file system information in a backend database. To communicate with the database you can use the "Windows Authentication" (only available for some supported database systems) 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 in intended 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 six 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, views, foreign keys, stored procedures and indexes in the connected database. |
Alter permission |
The permission to change the properties, except ownership, of a particular securable. |
Execute permission |
The permission to execute stored procedures |
The following table shows what kind of permissions your SpaceObServer application needs:
SpaceObServer Enterprise/Standard Edition |
Select permission; Update permission; Insert permission; Create permission; Alter permission; Execute permission |
SpaceObServer Remote Client
|
Select permission; Update permission; Insert permission (only needed when adding new scans); Alter permission |
SpaceObServer Remote Client
|
Select permission |
Note: When using "Windows Authentication" and a specified logon for the SpaceObServer scan service (See SpaceObServer scan service) the user interface and the SpaceObServer scan service could have different permissions. In this case the user interface needs the at least the permissions of the SpaceObServer Remote Client. The SpaceObServer scan service 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.