Udostępnij za pośrednictwem

The “Exclusive” on the Database

  • Artykuł

One of the frustrating things when multiple user are connecting to a single SQL Server Embedded Database is that the first person (with full permissions for the database) who opens Database Manager when no other Embedded tools are open can prevent all other users from connecting to the database.

This is because the default mode for opening Database Manager, when it is the sole Embedded tool open, is “Exclusive” – see screenshot below.

This mode allows for users with sufficient permissions to delete components, repositories and packages, and to change the repository roots. At this time no other users can be connected to the database. However, having any user unknowingly put the database in exclusive mode and thereby preventing others from connecting can be seriously inconvenient.

In order to mitigate this you are able to prevent the database from being put into an exclusive state at all. In my previous post I had talked about the built-in Roles for the Embedded MantisSQLDB database. Within these roles you can change the setting for “Set single user” to "Disabled" which will prevent any one user putting the database into exclusive mode- see screenshot below. When a delete function is required, the admin can briefly re-enable this setting after giving other users of the database fair warning to disconnect from the database.

- Lynda

Comments