Database User Privileges

Because of the security risks, we recommend that you do not use the database administrator user for maintaining your Silk Central database. This topic lists the database roles that can be used for specific tasks, as follows:

Microsoft SQL Server
If Microsoft SQL Server is your DBMS for Silk Central, the following database user roles/privileges are required for your Silk Central database:
Either: Or:
  • db_owner
  • db_ddladmin
  • VIEW SERVER STATE
  • db_datareader
  • db_datawriter
  • db_ddladmin
  • EXECUTE
  • VIEW SERVER STATE
These roles/privileges allow creating and configuring database tables, working with a previously created database, and installing and upgrading the software.
Note: The Silk Central database user requires these roles/privileges. Otherwise, errors occur.
Note: The read-only user requires the role db_datareader.
Oracle
If Oracle is your DBMS for Silk Central, set the following Oracle database user privileges to work with Silk Central:
  • CREATE SESSION
  • CREATE PROCEDURE
  • CREATE SEQUENCE
  • CREATE TABLE
  • CREATE TRIGGER
  • CREATE VIEW
Note: The Silk Central database user requires all the preceding privileges. Otherwise, errors occur. To get all database-related analysis data in system diagnostics, it is also recommended to assign the SELECT_CATALOG_ROLE to your database user.
Note: The Oracle user must have sufficient quotas to work with Silk Central.
When setting up an Oracle DBMS for Silk Central, ensure that the Oracle environment meets the following requirements:
  • At least 2 GB of temporary tablespace is available.
  • Sufficient disk space is available to handle the size of the temporary tablespace.
The read-only user has to have the following privileges in the Silk Central database schema:
  • READ on all tables and views
  • READ, INSERT, DELETE on the table SCC_TEMPTABLE0
Parent topic: Databases