sapio365 creates a local cache for the lists of users, groups and sites for each installation.
An option to centralize the cache is to store it in a SQL database within your network.
The cache can be updated in one location. This update be scheduled.
All sapio365 users will always have access to fresh data.
Here’s what you need to do to enable this.
Ask your database administrator to create a single database that can be accessed for a specific user. This user must to be able to create tables in the database.
Set up the connection in sapio365 for a specific session or directly, or for a delegated RBAC role when setting up credentials.
Set SQL Server Protocol (OLEDB or ODBC) in Preferences ->Global.
Note that this requires that everyone access the SQL Server on the same port 1433 (or any other port you choose to use).
The cache is stored by tenant. So the first user on a given tenant who connects to the SQL cache for the first time or after a database purge will re-build the cache (this may take some time). Users who connect afterwards will be able to only do a refresh of the data.
Set on a specific session
Select a session and from the right-click menu, ‘Set Cache Options’.
Set ‘Use SQL Server’ to True and fill in the settings.
You can test the connection by clicking on the Test icon.