What is an active database?
Active database is an automated interface that performs certain features that depend on specific inputs of information. Programmers and administrators can manipulate active database systems to carry out transactions according to predefined relationships. Like the idea of the cause and consequence, some of these relationships or questions are referred to as "connection". In the database design, there are parameters that specify what information will be shared and shared with. Automated account payments are an example of an active database. A banking customer can order its institution to pay the recipient a specific amount each month on a certain date. After reaching the specified date, the electronic payment is automatically sent to the recipients marked in the database.
Sometimes referred to as AR controlled events, the active database is designed to take steps based on certain triggers. There is usually a relationship between events. For example, database points (POS) database systemsThey can automatically rework the product for a retail store once they receive information that the current inventory has dropped to a predefined amount. Depending on how the database parameters are set, the actual overwork may be immediately as a separate transaction or is delayed.
Immediate transactions occur along with triggering events. For example, the POS system can re -buy a product according to the universal product code (UPC) or units to maintain inventory (SCR). It can process stock levels and ordering transactions simultaneously. Many bulk retailers operate under this type of active database that receives continuous inputs from several sources, including selling and receiving staff.
separate transactions are set to occur at different times. The database is usually designed to explore the trigger event and may have to compare it with DALby the reasons to take action. For example, the POS retailer system may be lowered by a low level of inventory, but the measures taken may depend on whether the product is interrupted or whether the item is delivered via the supplier. The database does not have to process the order if the rules are set to reject the action if the product does not pass the evaluation.
Delayed transactions are similar to the idea of separate transactions, except that the first must end before the second processing. In an example of POS, the database may notice that supplies for a particular product have fallen below acceptable levels early during the day. In the case of a delayed transaction, the re -ordering process would not be carried out until the business was closed when the final stock levels are recorded.