DB Permissions for Project transfer

[skiwi]

We are creating a new SQL Server repository.
Our DB created the database and executed the EA schema SQL.
I then attempted to open the new repository and as expected received a prompt to transfer an existing project in.
I, like all users, have read-write access to the repository.
I get an error. "Cannot find the object "t_category" because it does not exist or you do not have permissions.
Yet I can see the table using SQL Server management studio.


Do I need initial additional permissions for this step?

[Aaron B]

Make sure that the user performing the transfer has 'db_ddladmin' permission.

See:
http://sparxsystems.com/enterprise_architect_user_guide/12.1/the_model_repository/sqlserver_security_perms.html

[skiwi]

Thanks, now I re-read http://sparxsystems.com/enterprise_architect_user_guide/12.1/the_model_repository/createanewsqlserverreposi.html I see it is noted in the fineprint 

[Geert Bellekens]

It's because of the truncate table commands executed by the model transfer you need the ddladmin rights.

For "regular" users who don't need to to model transfer dbeader and dbwriter are enough I think.

Geert