2. What is 24*7 running
database
• Definition of 24*7*365 running database.
• The database which constantly online for
24 hours a day for whole week and for
whole year.
• The database doesn’t bring down.
• Because people are accessing this
database constantly 24*7*365.
• Example for Telecommunication,
Banking type databases.
3. 24*7*365 running database
• Specially called as OnLine Transaction
Processing database.
• OLTP handles real time transactions
which inherently have some special
requirements.
• Designed for real time business
operations.
• Online Transaction Processing has
two key benefits: simplicity and
efficiency
4. OLTP Database
• What is OLTP database?
• Online Transaction Processing has two
key requirements availability &
performance.
• Optimized for a common set of
transactions, usually adding or retrieving
a single row at a time per table.
• Supports thousands of concurrent users.
• It processes single transaction.
• It fetches single row from database.
5. OLAP Database
• OnLine Analytical Processing Database.
• OLAP database is different than OLTP
database.
• It may run 24*7 and may not run 24*7.
• It provides time series and trend analysis
views of database.
• The term OLAP was created as a slight
modification of the traditional database
term OLTP.
6. Usage of OLAP
• OLAP is part of the broader category of
business intelligence, which also
encompasses relational reporting and
data mining.
• The typical applications of OLAP are in
business reporting for sales, marketing,
management reporting, business process
management (BPM),budgeting and
forecasting, financial reporting and
similar areas.
8. More about 24*7 databases
• Remember important things.
• Database which doesn’t bring down
because it is being accessed by clients
constantly.
• All online databases like banking,
telecommunication etc.
• Which application of database is used by
customers.
• Application needs to bring database
always up for customers.
9. Special requirements of 24*7
running databases
• 24*7 running database requires high
availability.
• It requires minimum downtime.
• It requires maximum security protection.
• It requires maximum uptime.
• It requires constant monitoring.
• It requires special hardware or external
hardware.
• It requires effective database structuring.