De-allocating Databases

The same principles for allocating databases, as described above, apply to de-allocating databases.

If users are reading a database at any satellite location and it is de-allocated at that location by the hub while it is being read, then the database(s) de-allocated will not immediately be deleted from the satellite locations.

The command will be stalled in the transaction database and, once all users at the location exit their session, the database(s) will be de-allocated and the database files deleted.

Note:
Only secondary databases can be de-allocated. If a database is primary at a satellite, first make it secondary, then de-allocate it. If changing a database from primary to secondary while a user is reading/writing to it, the user will be able to write to the database until such a time as that user changes modules. A dB does not need to be primary at the HUB, just as long as it is not primary at the location where it is being de-allocated.