Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

SQL Server Security Permissions

The security model implemented by Microsoft's SQL Server is quite powerful and highly configurable, supporting many different possible solutions for securing the data contained in SQL Server databases, ensuring it is only accessible to users with the required permissions. For a more detailed description and explanation of SQL Server permissions, see the SQL Server documentation.

Enterprise Architect users who plan to add, edit and delete contents in a SQL Server repository must have permissions to perform SELECT, UPDATE, INSERT and DELETE statements on all Tables in the Enterprise Architect database. The easiest way to achieve this is to grant the database roles of 'db_datareader' and 'db_datawriter' to each user.

Additional Permissions for Project Transfers

When an Enterprise Architect repository is transferred into a SQL Server based repository it is necessary for Enterprise Architect to perform a number of SET IDENTITY_INSERT (table) {ON | OFF} commands during the process. This means the user performing the transfer must have a high level of security, the role of 'db_ddladmin'.

Does Enterprise Architect support Windows Authentication?

Enterprise Architect does support Windows Authentication. However, the type of authentication is determined by the configuration of the connection used and not by Enterprise Architect.

Windows Authentication to SQL Server is commonly used by Enterprise Architect users, but this requires that all Windows users in Enterprise Architect be defined on the SQL Server server and be granted the security roles 'db_datareader' and 'db_datawriter' for the repository.

Learn more