Temporal database
A temporal database is a database that needs some aspect of time for the
organization of information. In the temporal database, each tuple in relation is
associated with time. It stores information about the states of the real world and
time. The temporal database does store information about past states it only stores
information about current states. Whenever the state of the database changes, the
information in the database gets updated. In many fields, it is very necessary to
store information about past states. For example, a stock database must store
information about past stock prizes for analysis. Historical information can be
stored manually in the schema.
There are various terminologies in the temporal database:
• Valid Time: The valid time is a time in which the facts are true with
respect to the real world.
• Transaction Time: The transaction time of the database is the time at
which the fact is currently present in the database.
• Decision Time: Decision time in the temporal database is the time at
which the decision is made about the fact.
Temporal databases use a relational database for support. But relational databases
have some problems in temporal database, i.e. it does not provide support for
complex operations. Query operations also provide poor support for performing
temporal queries.
Applications of Temporal Databases
Finance: It is used to maintain the stock price histories.
1. It can be used in Factory Monitoring System for storing information
about current and past readings of sensors in the factory.
2. Healthcare: The histories of the patient need to be maintained for
giving the right treatment.
3. Banking: For maintaining the credit histories of the user.
Examples of Temporal Databases
1. An EMPLOYEE table consists of a Department table that the
employee is assigned to. If an employee is transferred to another
department at some point in time, this can be tracked if the
EMPLOYEE table is an application time-period table that assigns the
appropriate time periods to each department he/she works for.
Temporal Relation
A temporal relation is defined as a relation in which each tuple in a table of the
database is associated with time, the time can be either transaction time or valid
time.
Types of Temporal Relation
There are mainly three types of temporal relations:
1. Uni-Temporal Relation: The relation which is associated with valid or
transaction time is called Uni-Temporal relation. It is related to only one time.
2. Bi-Temporal Relation: The relation which is associated with both valid time
and transaction time is called a Bi-Temporal relation. Valid time has two parts
namely start time and end time, similar in the case of transaction time.
3. Tri-Temporal Relation: The relation which is associated with three aspects
of time namely Valid time, Transaction time, and Decision time called as Tri-
Temporal relation.
Features of Temporal Databases
• The temporal database provides built-in support for the time
dimension.
• Temporal database stores data related to the time aspects.
• A temporal database contains Historical data instead of current data.
• It provides a uniform way to deal with historical data.
Challenges of Temporal Databases
1. Data Storage: In temporal databases, each version of the data needs
to be stored separately. As a result, storing the data in temporal
databases requires more storage as compared to storing data in non-
temporal databases.
2. Schema Design: The temporal database schema must accommodate
the time dimension. Creating such a schema is more difficult than
creating a schema for non-temporal
databases.
3. Query Processing: Processing the query in temporal databases
is slower than processing the query in non-temporal databases due to
the additional complexity of managing temporal data.
Temporal database
A system called a temporal database is explicitly created to manage and store
temporal data, or data that varies over time. It enables applications to analyze and
query data with a temporal dimension by enabling the storing and retrieval of data
about the past, present, and future states of the data.
Temporal databases increase traditional databases' capabilities by adding the
concept of time to the data model. They provide the storage and querying of data
with corresponding time intervals, enabling the monitoring of changes and the
history of the data through time. As in financial systems, scientific research,
historical records, and process monitoring, this temporal feature can be helpful in
various fields where the evolution of data is crucial.
Valid time and transaction time are often the two fundamental components of
temporal databases. While transaction time refers to the period during which the
fact is kept or recorded in the database, valid time refers to the amount of time
during which a fact is true in the actual world. Temporal databases allow storing
temporal data with conventional data properties by capturing both valid and
transaction times.
The temporal database does contain data about earlier states. It just keeps data
about the condition of things right now. The data in the database is updated
whenever the status of the database changes. Information on previous states must
be kept on hand in many industries. For instance, a stock database must keep
records of previous stock awards for analysis. Manual archiving of historical data
is possible in the schema.
Different methods may be used to implement the temporal databases:
• Valid Time
• Transaction Time
• Decision Time
Valid Time: The period during which a fact or a statement is actual is referred to
as the "valid time," also known as the "valid-time period" or the "valid period."
It denotes the time frame within which a person, thing, or relationship is regarded
as accurate or relevant. Valid time is a crucial element used to collect and manage
the temporal dimension of data in the context of temporal databases.
Each record or fact in a temporal database has a valid-time interval associated
with it that specifies the duration of its validity. A single timestamp representing
a single point in time or a mix of start and end timestamps can describe this
period. The period when a fact was accurate or valid in the real world is known
as the valid-time interval.
Consider a database that has employee data, for instance. Every employee record
is allowed to have a valid interval corresponding to the period they were
employed. The employee's start timestamp would show the day they started
working for the firm, and their end timestamp would show either the day they left
the company or the day they are still working.
Describing changes and historical states is possible by enabling valid-time
periods to overlap or be disconnected. Temporal databases, which store a
complete history of changes and enable temporal querying, analysis, and retrieval
of data based on specific periods or points, capture the valid time.
Transaction Time: A fact or statement is recorded or saved in the database
during a time known as transaction time, sometimes referred to as system time or
database time. It is the temporal component related to the administration and
storage of data in a temporal database.
Each record or fact in a temporal database is linked to a transaction-time interval
that denotes the moment the fact was entered into the database. This time frame
encapsulates the span of the data's applicability or validity inside the database
system.
The start and finish timings of the recording or storing operation are commonly
used as timestamps to describe the transaction-time interval. The database's start
timestamp showed when the fact was added, changed, or deleted, while the end
timestamp showed when the action was finished or a later modification replaced
the fact.
The database's data development and history may be captured using transaction
time. It enables temporal querying and analysis using the transaction-time
dimension by preserving several versions or states of the data.
Take a database that contains customer data as an illustration. Each customer
record may be assigned a transaction-time interval that shows when the record
was added, changed, or removed. The database may keep an exhaustive audit trail
of modifications by recording the transaction time, offering a historical data view.
Transaction time is essential for maintaining data consistency, concurrency
management, and integrity within temporal databases. It makes it possible to keep
track of data changes, spot incompatible processes, and go back in time if
necessary.
Decision Time: "Decision time" describes the time frame in which a decision or
selection is made and finalized. It symbolizes the time component of decision-
making processes in various circumstances, including work, personal life, and
problem-solving situations.
Depending on how complex and important the decision is, it may take a while to
make a decision. It can range from quick judgments made at the moment to longer
procedures, including extensive deliberation, analysis, and appraisal of the
options.
Situations Critical: Making decisions quickly is crucial in emergencies. It is the
window within which essential decisions must be taken to assure safety, reduce
risks, or react to unforeseen events.
Personal Life: Personal decision-making, such as selecting a job, choosing a
partner, establishing financial plans, and changing one's lifestyle, are all
significant to decision time. It entails assessing possibilities, considering many
circumstances, and eventually deciding on a course of action.
The quantity and quality of the information available, the choice's complexity, the
number of stakeholders involved, and the decision-makers preferences and
decision-making style can all affect how long it takes to make a decision.
Effective time management, data analysis, evaluation of various outcomes, and
alignment with goals and values are frequently necessary for efficient decision-
making. It may also entail consulting experts, asking for guidance, or employing
decision-making frameworks to improve the decision-making process.
Temporal Relation:
Each tuple in a temporal relationship has an associated time that may be the
transaction time, the valid time, or both.
Uni-Temporal Relations: has a single axis of time: Transaction Time or Valid
Time.
Bi-Temporal Relations: Contains the Valid Time and Transaction Time time axes.
It comprises Transaction Start Time, Transaction End Time, Valid Start Time, and
Valid End Time.
Advantages of temporal Database:
Temporal databases have several benefits over standard databases when
organizing and analyzing time-varying data. The following are some significant
benefits of temporal databases:
• Temporal databases allow for analyzing historical data trends, patterns, and
changes. They give users a thorough historical perspective, enabling them
to follow and examine the development of the data and comprehend the
context of the present condition.
• Temporal Databases Support Temporal searches: Temporal databases
allow users to obtain data in response to point-in-time, historical, or
interval-specific searches. This makes it possible to retrieve temporal data,
supporting sophisticated analysis and decision-making accurately and
adaptable.
• Data Integrity and Auditing: Temporal databases keep track of data
changes over time, preserving data changes' history and enabling data
integrity checks. It enables tracking and verifying data updates across time,
which is helpful for compliance, regulatory requirements, and forensic
investigation.
Disadvantages of the temporal database:
• Increased Complexity: When compared to conventional databases,
temporal databases add more complexity. Understanding and using
temporal semantics, operators, and constraints are necessary for managing
and accessing temporal data. The creation, use, and maintenance of
temporal databases may be more difficult because of this complexity.
• Data Storage Overhead: More storage space is frequently needed when
storing temporal data than with typical databases. Temporal databases must
preserve past versions of the data, which can result in higher storage needs,
particularly for datasets that see frequent updates or have significant
amounts of historical data.
• Performance Impact: The performance of temporal databases may be
affected by temporal querying and processing. Compared to
straightforward relational queries, handling temporal intervals and running
complicated temporal queries may need more computing power and longer
query execution times.
• Creating and running temporal queries might be more complex than doing
so with regular queries. It takes a firm grasp of temporal ideas and syntax
to effectively use temporal querying, which entails establishing valid-time
and transaction-time requirements, managing temporal operators, and
dealing with temporal intervals.
