...

See Database Users, Roles, and Passwords for a general database setup for Datical DB. Create a Login User

...

Create a REF Datical Login and User

Make sure that you are connected to the master database as the Server admin and the user you will create has access to read the metadata.use the master database to run commands:

CREATE LOGIN [datical_ref_login] WITH PASSWORD=N

'<password>';
CREATE USER [datical_ref_user] FOR LOGIN [datical_ref_login];
EXEC sp_addrolemember 'dbmanager', 'datical_ref_user';

The dbmanager role is a Server-level role required for managing and creating databases. Additionally, if the Datical User needs the ability to create and manage logins, include the following role:

EXEC sp_addrolemember 'loginmanager', 'datical_ref_user';

Create a REF Database User

Create a user (datical_ref_user) for databases under Datical DB management and assign the needed roles to the user:

Step 1: Identify the appropriate permissions for the Datical User

Datical permissions, which are needed for all environments.

...

a database where Packager operation will be performed:

CREATE USER [datical_ref_user] FOR LOGIN [datical_ref_login];
EXEC sp_addrolemember 'db_owner', 'datical_ref_user';

Create a non-REF Datical Login and User

Make sure that you are connected to the master database as the Server admin and use the master database to run commands:

CREATE LOGIN [datical_login] WITH PASSWORD=N'<password>';
CREATE USER [datical_user] FOR LOGIN [datical_login];

Create a non-REF Database User

Create a user (datical_user) for database where Forecast and Deploy (not Packager) operations will be performed:

Datical packager permissions, which are required on reference database environments only. These permissions are additional to the DATICAL_ROLE permissions.

...

Role

...

When is this required?

...

Permissions

...

dbcreator

...

This is required to create an ephemeral copy of the database.   

...

Can create and delete databases. A member of the dbmanager role that creates a database, becomes the owner of that database which allows that user to connect to that database as the dbo user. The dbo user has all database permissions in the database. Members of the dbmanager role do not necessarily have permission to access databases that they do not own.

Also, a user with the dbmanager role can perform database restores.

If the database being restored does not exist, the user must have CREATE DATABASE permissions to be able to execute RESTORE. If the database exists, RESTORE permissions are default to members of the sysadmin and dbmanager fixed server roles and the owner (dbo) of the database.

RESTORE permissions are given to roles in which membership information is always available to the server. You can check a fixed database role membership only when the database is accessible and undamaged, which is not always the case when RESTORE is executed. For this reason, members of the db_owner fixed database role do not have RESTORE permissions.

If you want to use Deploy Packager, assign the roles of db_owner and dbmanager to the user. If you don’t want to use Deploy Packager, assign the roles of db_datawriter or db_datareader. Additionally, if you need to deploy the objects listed below, grant the db_ddladmin role to the user.

CREATE

Step 2: Grant the appropriate permissions as defined to the Datical User

Example script to assign roles to datical_user.

DATICAL_USER

USER [datical_user] FOR LOGIN [datical_login]

;
EXEC sp_addrolemember 

'db_ddladmin', 

'datical_user'

;
EXEC sp_addrolemember 

'db

_

datawriter', 

'datical_user';

EXEC sp_addrolemember 

'db_

datareader', 

'datical_user'

Example script to assign additional roles to datical_user for the reference database environments and packaging only:

DATICAL_USER

;