Within the SeRP environment once a project space is created and data ingested or provisioned. a specific project schema is created this is the name of the project.
Should users wish to create objects within that schema, either tables or views of that underlying data. Then they can do this by creating separate tables or views from that original project data and sharing that for all permitted users of that project.
SeRP has a permissions based model that implements stated permissions controlled by SeRP every hour. Once an object is created it could take up 3 hours for this to be present to all users,
Note: This user guide is intended for all SeRP users but each implementation may differ and you may not be provided with appropriate permissions to carry out this activity.
Step-by-step guide
Pre Requisites:
- Users will require rw permissions on the database within a project.
- There is a mixed estate on how schemas are named, they are either named following the project name or the SeRP tenancy AND the project name. To clarify which pattern you'll need to use when saving your object, you'll need to check the schema name created.
- The screenshot below is from SQL Management Studio where you can see the pattern in this example is
dsbtraining_cambridgeDSB being the SeRP Name andtraining_cambridgebeing the Project name.
How to configure:
- Any object (Views/Table/Queries etc) will need to be prefixed with the name of the project followed by a full stop
- In the example below the project name is Restricted. Therefore if a view called
"joinoftables"was generated for this project the action would be"create view restricted.joinoftables"or"create view dsbrestricted.joinoftables"
3. Once created, this will be for users with r or rw access to the project database schema.