...
See Database Users, Roles, and Passwords for a general database setup for Datical DB.
Info |
---|
The Datical Packager process requires elevated privileges on a REF Azure SQL Database as an ephemeral database is created and dropped as part of the Backup and Restore operations. The below instructions show how to setup separate Logins and Users for a REF database versus a non-REF database. |
Create a REF Datical Login and User
Make sure that you are connected to the master
database and the user you will create has access to read the metadata.as the Server admin:
|
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 role below.
|
Info |
---|
The default Azure password complexity rules are the following: minimum length of 8 characters, minimum of 1 uppercase character, minimum of 1 lowercase character, minimum of 1 number. |
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.
...
database where Packager operation will be performed:
Role/Permission | When is this required? | Permissions |
---|---|---|
db_owner | This role is required if you need to perform all configuration and some maintenance activities on the databasefor REF databases and the Packager process to create an ephemeral copy of the database during Backup and Restore. | Manage fixed-database role membership, configuration, and maintenance activities. |
VIEW DATABASE STATE | This is required for some Datical operations such as using Approximate Row Counts. | Read data from dynamic management views scoped to the database. |
Info |
---|
You must be connected to the database instance you want to use with Datical DB while granting permissions. |
|
Create a non-REF Datical Login and User
Make sure that you are connected to the master
database as the Server admin:
|
Info |
---|
The default Azure password complexity rules are the following: minimum length of 8 characters, minimum of 1 uppercase character, minimum of 1 lowercase character, minimum of 1 number. |
Create a non-REF Database User
Create a user (datical_user
) for database where Packager operation will be performed:
Role/Permission | When is this required? | Permissions | |||
---|---|---|---|---|---|
db_ddladmin | This is required if you do not connect as the database owner. | Run any Data Definition Language (DDL) command in a database. | |||
db_datawriter | This is required if you do not connect as the database owner. | Add, delete, or change data in all user tables. | |||
db_datareader | This is required if you do not connect as the database owner. | Read all data from all user tables. | db_loginmanager | This is required if grants are allowed in scripts. If you have this role, you can create and delete logins in the virtual master database. | Perform grants to all objects in the database. |
VIEW DATABASE STATE | This is required for some Datical operations such as using Approximate Row Counts. | Read data from dynamic management views scoped to the database. |
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.
Info |
---|
You must be connected to the database instance you want to use with Datical DB while granting permissions. |
|
Step 2: Grant the appropriate permissions as defined to the Datical User
Info |
---|
Additional permissions are typically added to the reference database environments. |
Example script to assign roles to datical_user
.
DATICAL_USER
|
Example script to assign additional roles to datical_user
for the reference database environments and packaging only:
DATICAL_USER
|