Control updates StabiBase Database with SQL Studio management
Not version-specific
Stabicad
Problem:
A Stabibase administrator wants to prevent anyone from updating the shared database to a new version without authorization. Unintended updates occur when the database becomes locked—a requirement for any upgrade.
Solution:
- In Studio Management, navigate to the server-level security settings and grant the user or group the Public role.

- Under database-level security for the shared database, assign the DB_Writer and DB_Reader roles to the same user or group.
- Ensure the user’s or group’s default database is set to your Stabicad database.

- Set the default schema for that user or group to dbo.
- Grant EXECUTE permissions on the database so the user or group can run the stored procedures needed by Stabicad.

- To verify, start Stabicad and try creating a new project or drawing. If the database is not locked and you can create a project, your permissions are correctly set.
If you have any questions about this article, please contact the helpdesk directly