Systems and methods are provided for database scheduling. Scheduling entries are created and stored in a central database and an entity's database. In response to a user request to view the availability of the entity, a scheduling system can retrieve the scheduling data of an entity from the central database. The scheduling database system attempts to connect to an entity to propagate a scheduling entry in near time. If a connection to the entity from the scheduling database system can be made, the system updates the entity's database in near time. However, an attempted connection may have a fail status due to network issues and/or a VPN connection being unavailable. If a connection is unavailable, the updated scheduling data is propagated via a synchronization process. In the scheduling database system, a scheduling entry in the central scheduling database includes a synchronization status that marks the scheduling entry for future propagation. A synchronization status is set in the entities' database(s) to mark an entry for synchronization purposes. The scheduling database system permits double booking.