To easily manage the permissions in your solution database, it is recommended you define a set of roles based on job functions and assign each role the permissions that apply to that job.
SQL Server roles exist within a database and cannot span more than one database. Because roles are unique to each database, you can reuse a role name, such as "Reviewer" in each database that you create.
To assign users and groups to database roles, the users and groups must have valid Windows NT domain accounts and SQL Server logins. For details, see Creating Windows NT User and Group Accounts, and Creating SQL Server Logins.
You have two options when creating database roles for your team solutions:
After creating your database roles, you can add users to your team solutions. For details, see Creating Team Solution Database Users.
Note If you make any changes to the membership of database roles in your team solution, you need to synchronize the user directory in order for role permissions to work properly. For details, see Synchronizing User Information in the Access Workflow Designer Administrator's Guide.
By default, SQL Server Enterprise Manager is installed by SQL Server Setup as part of the server software on computers running Windows NT and as part of the client software on computers running Windows NT, Windows 95, and Windows 98.
To create a SQL Server role using the Enterprise Manager
Repeat these steps as necessary to create your database roles.
Microsoft Access can be used to create database roles for your SQL Server database using an Access data project.
To create database roles using Access
Note When an Access data project is loaded and you are working in the Access Workflow Designer, you can access the Security option from the Tools menu in the designer as well.
Repeat these steps as necessary to create additional database roles.