The document provides an overview of a database system. It includes examples of different types of databases and database applications. It also discusses the advantages and implications of the database approach compared to a file-based approach. This includes features like data independence, data sharing, and transaction processing. The document also summarizes the historical development of database technology from early hierarchical and network models to today's relational, object-oriented, and web-based databases.
This document provides an overview of relational database design for geographic information systems (GIS). It discusses how GIS databases can be designed using a relational model with spatial data stored in tables along with associated attribute data for efficient management and analysis. The key aspects covered include normalization of tables, use of primary and foreign keys to link features to their attributes, and queries using SQL to access both spatial and non-spatial data together. Maintaining data integrity and relationships between features and attributes is also emphasized.
The Whats, Whys and Hows of Database as a ServicePeak 10
Companies have long used relational database management systems (RDBMS) to power their mission-critical applications. However, these systems have proven to be cumbersome to manage as more and more applications with database back-ends are deployed. They can’t automatically scale their resources in response to varying workload demands, licensing costs continue to escalate, and ongoing administration including monitoring, backups, and event remediation is onerous.
The document discusses the database development process and information engineering methodology. It covers planning the information systems architecture, developing an enterprise data model, and using techniques like prototyping and the system development life cycle for database design and implementation. Project management tools like Gantt charts and PERT charts are used to manage the people involved in database development projects.
January 2006 Document Scanning Considerations PresentationJohn Wang
This document discusses considerations for scanning and digitizing paper documents. It notes that 90% of business information exists on paper and the volume is growing rapidly. Documents are often lost or misfiled, costing time and money. A digital document management system can solve these problems by scanning documents into a searchable electronic format. The document outlines various scanning options like full or partial backfile conversion, indexing processes, and typical applications that are good candidates for digitization like accounts payable or medical records. It also addresses challenges that may arise during conversion from old legacy systems to new digital formats.
This document describes a proposed scheduling and shift management software called Shift-iT. Surveys and interviews revealed inefficiencies in current scheduling procedures used by industries, public sector, and private services companies. Shift-iT aims to address these inefficiencies by providing an automated scheduling solution using a service-oriented architecture with web and mobile applications. The product is expected to provide scheduling optimization, real-time duty management, and transparency. Financial projections estimate the product can achieve profitability in its second year with a valuation of $5-10 million by its fifth year as it targets the global market for scheduling and shift management software.
DB Luminous [DBL) is a web-based solution that allows any stake holders, analysts, DBA's and the management team to easily comprehend the documentation of complexities within the database.
At their fingertips, DBL creates a console for a comprehensible view of large, sophisticated databases.
This document provides an overview of relational database design for geographic information systems (GIS). It discusses how GIS databases can be designed using a relational model with spatial data stored in tables along with associated attribute data for efficient management and analysis. The key aspects covered include normalization of tables, use of primary and foreign keys to link features to their attributes, and queries using SQL to access both spatial and non-spatial data together. Maintaining data integrity and relationships between features and attributes is also emphasized.
The Whats, Whys and Hows of Database as a ServicePeak 10
Companies have long used relational database management systems (RDBMS) to power their mission-critical applications. However, these systems have proven to be cumbersome to manage as more and more applications with database back-ends are deployed. They can’t automatically scale their resources in response to varying workload demands, licensing costs continue to escalate, and ongoing administration including monitoring, backups, and event remediation is onerous.
The document discusses the database development process and information engineering methodology. It covers planning the information systems architecture, developing an enterprise data model, and using techniques like prototyping and the system development life cycle for database design and implementation. Project management tools like Gantt charts and PERT charts are used to manage the people involved in database development projects.
January 2006 Document Scanning Considerations PresentationJohn Wang
This document discusses considerations for scanning and digitizing paper documents. It notes that 90% of business information exists on paper and the volume is growing rapidly. Documents are often lost or misfiled, costing time and money. A digital document management system can solve these problems by scanning documents into a searchable electronic format. The document outlines various scanning options like full or partial backfile conversion, indexing processes, and typical applications that are good candidates for digitization like accounts payable or medical records. It also addresses challenges that may arise during conversion from old legacy systems to new digital formats.
This document describes a proposed scheduling and shift management software called Shift-iT. Surveys and interviews revealed inefficiencies in current scheduling procedures used by industries, public sector, and private services companies. Shift-iT aims to address these inefficiencies by providing an automated scheduling solution using a service-oriented architecture with web and mobile applications. The product is expected to provide scheduling optimization, real-time duty management, and transparency. Financial projections estimate the product can achieve profitability in its second year with a valuation of $5-10 million by its fifth year as it targets the global market for scheduling and shift management software.
DB Luminous [DBL) is a web-based solution that allows any stake holders, analysts, DBA's and the management team to easily comprehend the documentation of complexities within the database.
At their fingertips, DBL creates a console for a comprehensible view of large, sophisticated databases.
Join us to discover how Ivanti File Director can consolidate the management of your on-premises and cloud storage, delivering user profile data on-demand to physical and multi-user virtual workstations. We will also cover our modern device management capabilities by means of Intune.
This document discusses LinkedIn's data infrastructure. It describes how LinkedIn handles large volumes of user data across online, nearline and offline systems. Key systems discussed include Kafka for messaging, Databus for change data capture, Voldemort for online key-value storage, and Espresso for indexed, timeline-consistent distributed storage. Espresso provides a rich data model and APIs for applications to access user data.
This document discusses databases and how they are used to organize data. It defines key database concepts like data, records, fields and files. It explains how databases improve on traditional file processing systems by reducing redundancy and improving data sharing and integrity. Different types of database models are covered, including relational, object-oriented and multidimensional databases. The roles of database administrators and analysts are described in managing and designing database systems. Web databases that power online services are also summarized.
This document provides an overview and update on Kuali OLE, an open source library management system project. It summarizes the project's first year, highlights features and functionality in development milestones, and outlines plans for the second year and beyond. The presentation was given by Andy Sarno, Beth Camden, and Michael Winkler and covered the community-sourced approach, development progress to date including a version 0.3 prototype, and roadmaps for upcoming releases focusing on core functionality, technologies, and partner integration needs.
This document provides information about the role of a database administrator (DBA). A DBA is responsible for installing, configuring, maintaining, and optimizing databases. Key skills required for a DBA include communication skills, knowledge of database theory and SQL, and an understanding of storage technologies and operating systems. Employers typically require a Bachelor's degree or higher in computer science or a related field. Duties of a DBA include installing database software, allocating storage, managing user access privileges, monitoring performance, and backing up databases.
Zahid Ayub is a senior database administrator with over 14 years of experience managing SQL Server and Oracle databases. He has extensive experience designing and implementing database solutions, including high availability, backup/recovery, and replication. Currently he works as a senior database technical architect for Secure-IT in the UK, where his responsibilities include Oracle database migrations and implementing centralized monitoring.
Impact of in-memory technology and SAP HANA on your business, IT, and careerVitaliy Rudnytskiy
The document discusses the impact of in-memory technology, specifically SAP HANA, on businesses, IT, and careers. It notes that SAP HANA is becoming a major part of SAP solutions and is reshaping how businesses and IT use SAP. It also impacts the skills required for different roles. The document provides examples of how SAP HANA enables faster analysis and real-time decision making compared to traditional databases. Finally, it outlines how various roles from business to development will need new skills to work with SAP HANA and in-memory solutions.
The document describes a collateral aggregation and analysis reporting system (CAARS) that addresses challenges with external broker margin data management. CAARS captures data from various file formats, standardizes the data, loads it into a central repository, reconciles the data with internal records, and generates reports. It provides automated workflow processing, file capture, position matching, margin reconciliation, and reporting capabilities. CAARS helps facilitate collateral management processes and counterparty risk management.
Aras Vision and Roadmap with Aras Innovator PLM SoftwareAras
The document discusses Aras's product roadmap and vision. It outlines Aras's goals of developing a premier, connected, open, and community-driven PLM platform. The roadmap includes expanding client support, improving the user interface, integrating social features, and offering packaged and cloud-based solutions. It also details plans to enhance existing capabilities in areas like requirements management, ERP integration, and application lifecycle management.
SAN File System provides a simplified way to manage files and data across multiple servers connected through a SAN. It creates a single global namespace and allows files to be accessed from different platforms. SAN File System also implements policy-based automation to better match storage costs with data value through tiered storage management. This simplifies administration and improves storage utilization and data sharing across heterogeneous environments.
Oracle Warehouse Builder is Oracle's tool for designing, deploying, and managing business intelligence and data integration projects on the Oracle database. It provides a graphical environment to extract, transform, and load data from various sources into a Oracle data warehouse or datamarts. Warehouse Builder manages the full lifecycle of metadata and data, and enables users to design and deploy ETL processes, reporting infrastructure, and manage the target schema.
HCLT Brochure: E-Discovery and Document Review SolutionsHCL Technologies
http://www.hcltech.com/search/apachesolr_search/business-services~ More on Business Services
With the number of litigations expected to increase due to the economy, corporations and law firms are increasingly concerned with cost effective high-quality electronic d`iscovery (“e-discovery”) solutions. With 70% of the total cost of a litigation attributed to the document review fees, corporations and law firms must select innovative document review solutions to stay in budget. Simple Solutions’ e-Discovery and Document Review Services provides corporations and law firms with high quality, cost-effective document review services that gives them the cost certainty needed to stay in budget.
e-Discovery companies are leveraging cloud computing and deployment of Software as a Service (SaaS) platforms with focus on back office services to improve legal compliance service levels.
Download our e-Discovery and Document Review Solutions Brochure to understand how HCL focuses on creating efficient and cost effective document review solutions by marrying e-discovery.
The document discusses the database development process, including defining terms like enterprise data models and information systems architecture. It describes the system development life cycle and prototyping approaches for database development. It also covers topics like the roles of individuals, three-schema architecture, and packaged data models in database design.
Impact of in-memory technology and SAP HANA (2012 Update)Vitaliy Rudnytskiy
The document is a presentation from September 2012 about the impact of in-memory technology and SAP HANA on businesses, IT, and careers. It discusses how SAP is executing on its in-memory vision and how this is reshaping how businesses and IT use SAP solutions. It also impacts the skills required for different roles. The presentation provides an overview of in-memory concepts, principles, and the SAP HANA platform, and how they can be applied using tools like SAP BusinessObjects. It encourages attendees to learn more about this emerging technology area.
The document discusses the key components of a database management system (DBMS), including data models, languages for defining and manipulating data, transaction management, storage structure, the role of database administrators, and types of users. A DBMS provides logical and physical views of data that are abstracted from end users and allows for consistent data storage and retrieval through features like transaction processing, concurrency control, and a data dictionary. The document outlines the architecture of a DBMS and how various components work together to define, organize, and access the data in a database.
This document provides an overview and summary of key topics related to database design and management. It outlines the course contents, which include concepts of database management, database modeling, SQL, distributed databases, and database administration. It also discusses database terminology, the advantages of using a database management system (DBMS) compared to file-based systems, including improved data sharing and reduced redundancy. The components of a DBMS environment are identified as hardware, software, data, procedures, and people.
This document provides an outline for a course on databases and database users. It introduces key concepts about databases including what a database is, database properties, database management systems, actors involved with databases like administrators and designers, advantages of databases over file systems, and common database applications. The outline covers topics that will be taught like introduction to PHP and MySQL, how to code applications with databases, and how to perform common tasks with databases.
The document discusses the traditional approach to data management and the disadvantages of file processing such as data redundancy and limited data sharing. It then introduces the components of a database environment including DBMS, database, application programs, and data administrators. The document also outlines some disadvantages of DBMS like security risks and need for data quality controls. Finally, it describes the overall system structure of a database including query processor, storage manager, and application architectures.
This document discusses database management systems (DBMS) and their components. It describes DBMS as a set of programs that allow for the storage and retrieval of data. It then discusses the key components of a DBMS including the physical, logical, and view levels of abstraction, data models, data independence, data definition and manipulation languages like SQL, and the roles of database administrators and users. The document provides an overview of the architecture and design of database systems.
*What is DBMS
*Database System Applications
*The Evolution of a Database
*Drawbacks of File Management System / Purpose of Database Systems
*Advantages of DBMS
*Disadvantages of DBMS
*DBMS Architecture
*types of modules
*Three-Tier and n-Tier Architectures for Web Applications
*different level and types
*Data Abstraction
*Data Independence
*Database State or Snapshot
*Database Schema vs. Database State
*Categories of data models
*Different Users
*Database Languages
*Relational Model
*ER Model
*Object-based model
*Semi-structured data model
The document discusses a database systems course, including its objectives, importance, outlines, and lecture overview. The lecture overview introduces basic concepts of databases, including definitions of databases and comparisons to prior data processing approaches. It also discusses the components of a database environment and the evolution of database systems from flat files to modern relational, object-oriented, and web-enabled systems.
Join us to discover how Ivanti File Director can consolidate the management of your on-premises and cloud storage, delivering user profile data on-demand to physical and multi-user virtual workstations. We will also cover our modern device management capabilities by means of Intune.
This document discusses LinkedIn's data infrastructure. It describes how LinkedIn handles large volumes of user data across online, nearline and offline systems. Key systems discussed include Kafka for messaging, Databus for change data capture, Voldemort for online key-value storage, and Espresso for indexed, timeline-consistent distributed storage. Espresso provides a rich data model and APIs for applications to access user data.
This document discusses databases and how they are used to organize data. It defines key database concepts like data, records, fields and files. It explains how databases improve on traditional file processing systems by reducing redundancy and improving data sharing and integrity. Different types of database models are covered, including relational, object-oriented and multidimensional databases. The roles of database administrators and analysts are described in managing and designing database systems. Web databases that power online services are also summarized.
This document provides an overview and update on Kuali OLE, an open source library management system project. It summarizes the project's first year, highlights features and functionality in development milestones, and outlines plans for the second year and beyond. The presentation was given by Andy Sarno, Beth Camden, and Michael Winkler and covered the community-sourced approach, development progress to date including a version 0.3 prototype, and roadmaps for upcoming releases focusing on core functionality, technologies, and partner integration needs.
This document provides information about the role of a database administrator (DBA). A DBA is responsible for installing, configuring, maintaining, and optimizing databases. Key skills required for a DBA include communication skills, knowledge of database theory and SQL, and an understanding of storage technologies and operating systems. Employers typically require a Bachelor's degree or higher in computer science or a related field. Duties of a DBA include installing database software, allocating storage, managing user access privileges, monitoring performance, and backing up databases.
Zahid Ayub is a senior database administrator with over 14 years of experience managing SQL Server and Oracle databases. He has extensive experience designing and implementing database solutions, including high availability, backup/recovery, and replication. Currently he works as a senior database technical architect for Secure-IT in the UK, where his responsibilities include Oracle database migrations and implementing centralized monitoring.
Impact of in-memory technology and SAP HANA on your business, IT, and careerVitaliy Rudnytskiy
The document discusses the impact of in-memory technology, specifically SAP HANA, on businesses, IT, and careers. It notes that SAP HANA is becoming a major part of SAP solutions and is reshaping how businesses and IT use SAP. It also impacts the skills required for different roles. The document provides examples of how SAP HANA enables faster analysis and real-time decision making compared to traditional databases. Finally, it outlines how various roles from business to development will need new skills to work with SAP HANA and in-memory solutions.
The document describes a collateral aggregation and analysis reporting system (CAARS) that addresses challenges with external broker margin data management. CAARS captures data from various file formats, standardizes the data, loads it into a central repository, reconciles the data with internal records, and generates reports. It provides automated workflow processing, file capture, position matching, margin reconciliation, and reporting capabilities. CAARS helps facilitate collateral management processes and counterparty risk management.
Aras Vision and Roadmap with Aras Innovator PLM SoftwareAras
The document discusses Aras's product roadmap and vision. It outlines Aras's goals of developing a premier, connected, open, and community-driven PLM platform. The roadmap includes expanding client support, improving the user interface, integrating social features, and offering packaged and cloud-based solutions. It also details plans to enhance existing capabilities in areas like requirements management, ERP integration, and application lifecycle management.
SAN File System provides a simplified way to manage files and data across multiple servers connected through a SAN. It creates a single global namespace and allows files to be accessed from different platforms. SAN File System also implements policy-based automation to better match storage costs with data value through tiered storage management. This simplifies administration and improves storage utilization and data sharing across heterogeneous environments.
Oracle Warehouse Builder is Oracle's tool for designing, deploying, and managing business intelligence and data integration projects on the Oracle database. It provides a graphical environment to extract, transform, and load data from various sources into a Oracle data warehouse or datamarts. Warehouse Builder manages the full lifecycle of metadata and data, and enables users to design and deploy ETL processes, reporting infrastructure, and manage the target schema.
HCLT Brochure: E-Discovery and Document Review SolutionsHCL Technologies
http://www.hcltech.com/search/apachesolr_search/business-services~ More on Business Services
With the number of litigations expected to increase due to the economy, corporations and law firms are increasingly concerned with cost effective high-quality electronic d`iscovery (“e-discovery”) solutions. With 70% of the total cost of a litigation attributed to the document review fees, corporations and law firms must select innovative document review solutions to stay in budget. Simple Solutions’ e-Discovery and Document Review Services provides corporations and law firms with high quality, cost-effective document review services that gives them the cost certainty needed to stay in budget.
e-Discovery companies are leveraging cloud computing and deployment of Software as a Service (SaaS) platforms with focus on back office services to improve legal compliance service levels.
Download our e-Discovery and Document Review Solutions Brochure to understand how HCL focuses on creating efficient and cost effective document review solutions by marrying e-discovery.
The document discusses the database development process, including defining terms like enterprise data models and information systems architecture. It describes the system development life cycle and prototyping approaches for database development. It also covers topics like the roles of individuals, three-schema architecture, and packaged data models in database design.
Impact of in-memory technology and SAP HANA (2012 Update)Vitaliy Rudnytskiy
The document is a presentation from September 2012 about the impact of in-memory technology and SAP HANA on businesses, IT, and careers. It discusses how SAP is executing on its in-memory vision and how this is reshaping how businesses and IT use SAP solutions. It also impacts the skills required for different roles. The presentation provides an overview of in-memory concepts, principles, and the SAP HANA platform, and how they can be applied using tools like SAP BusinessObjects. It encourages attendees to learn more about this emerging technology area.
The document discusses the key components of a database management system (DBMS), including data models, languages for defining and manipulating data, transaction management, storage structure, the role of database administrators, and types of users. A DBMS provides logical and physical views of data that are abstracted from end users and allows for consistent data storage and retrieval through features like transaction processing, concurrency control, and a data dictionary. The document outlines the architecture of a DBMS and how various components work together to define, organize, and access the data in a database.
This document provides an overview and summary of key topics related to database design and management. It outlines the course contents, which include concepts of database management, database modeling, SQL, distributed databases, and database administration. It also discusses database terminology, the advantages of using a database management system (DBMS) compared to file-based systems, including improved data sharing and reduced redundancy. The components of a DBMS environment are identified as hardware, software, data, procedures, and people.
This document provides an outline for a course on databases and database users. It introduces key concepts about databases including what a database is, database properties, database management systems, actors involved with databases like administrators and designers, advantages of databases over file systems, and common database applications. The outline covers topics that will be taught like introduction to PHP and MySQL, how to code applications with databases, and how to perform common tasks with databases.
The document discusses the traditional approach to data management and the disadvantages of file processing such as data redundancy and limited data sharing. It then introduces the components of a database environment including DBMS, database, application programs, and data administrators. The document also outlines some disadvantages of DBMS like security risks and need for data quality controls. Finally, it describes the overall system structure of a database including query processor, storage manager, and application architectures.
This document discusses database management systems (DBMS) and their components. It describes DBMS as a set of programs that allow for the storage and retrieval of data. It then discusses the key components of a DBMS including the physical, logical, and view levels of abstraction, data models, data independence, data definition and manipulation languages like SQL, and the roles of database administrators and users. The document provides an overview of the architecture and design of database systems.
*What is DBMS
*Database System Applications
*The Evolution of a Database
*Drawbacks of File Management System / Purpose of Database Systems
*Advantages of DBMS
*Disadvantages of DBMS
*DBMS Architecture
*types of modules
*Three-Tier and n-Tier Architectures for Web Applications
*different level and types
*Data Abstraction
*Data Independence
*Database State or Snapshot
*Database Schema vs. Database State
*Categories of data models
*Different Users
*Database Languages
*Relational Model
*ER Model
*Object-based model
*Semi-structured data model
The document discusses a database systems course, including its objectives, importance, outlines, and lecture overview. The lecture overview introduces basic concepts of databases, including definitions of databases and comparisons to prior data processing approaches. It also discusses the components of a database environment and the evolution of database systems from flat files to modern relational, object-oriented, and web-enabled systems.
This document provides an overview of data management and IT infrastructure. It discusses data versus information, basic concepts of data, databases, and database management systems. It covers database models including hierarchical, network, relational, and object-oriented. It also discusses database applications, benefits of a database approach, centralized versus distributed databases, relational databases, data warehouses, and data mining. Finally, it provides an introduction to IT infrastructure and discusses the evolution of IT infrastructure from the 1950s to present.
The document discusses databases and database management systems. It provides examples of common database applications like banking, universities, sales, and airlines. It defines what a database is, the role of a database management system, and examples of DBMS software. It also compares the advantages and disadvantages of using a database system versus a traditional file system to store data. Key benefits of a DBMS include supporting complex queries, controlling redundancy and consistency, handling concurrent access from multiple users, and providing security and data recovery.
Data:
– Raw facts; building blocks of information
– Unprocessed information
Information:
– Data processed to reveal meaning
• Accurate, relevant, and timely information is key
to good decision making.
Management information system database managementOnline
The document discusses database management and related concepts. It defines database management as applying information systems technologies to manage an organization's data resources to meet business needs. It describes different database structures like hierarchical, network, relational, and object-oriented. It also discusses database development processes like conceptual design, entity-relationship modeling, normalization, and implementation. Data warehousing and data mining are also summarized.
This document provides an introduction to database management systems (DBMS). It discusses the disadvantages of traditional file-based data management approaches, such as data redundancy and lack of data integrity. It then describes the key components of a database system, including the database itself, DBMS software, users, and administrators. Challenges of DBMS include security, data quality, and data integrity issues that must be addressed. The overall system structure partitions responsibilities between query processing and storage management components.
1. A DBMS is a collection of programs that enables users to store, modify, and extract information from a database. It provides an interface between the database and users or other application programs.
2. The traditional file-based approach has disadvantages like data redundancy, lack of data integrity, lengthy development time and limited data sharing between applications.
3. The database approach organizes data into logical relationships and provides a centralized pool of shared data that can be accessed by multiple applications. This improves data integrity, reduces redundancy and provides easier data access and sharing.
This document provides definitions and summaries of different types of databases:
- It defines databases, data, and database management systems. It also defines flat file databases, relational databases, document-oriented databases, embedded databases, hypertext databases, operational databases, and distributed databases.
- Relational databases organize data into formally described tables that can be accessed in many ways without reorganizing tables. Document databases are designed for storing and managing document-oriented information. Embedded databases are integrated with application software. Operational databases contain reference and event data for transaction systems. Distributed databases consist of data files located across network sites.
Unit 1: Introduction to DBMS Unit 1 CompleteRaj vardhan
This document discusses database management systems (DBMS) and their advantages over traditional file-based data storage. It describes the key components of a DBMS, including the hardware, software, data, procedures, and users. It also explains the three levels of abstraction in a DBMS - the physical level, logical level, and view level - and how they provide data independence. Finally, it provides an overview of different data models like hierarchical, network, and relational models.
The document provides an overview of database systems and their components. It discusses the purpose of database systems, database languages, data models, database internals including storage management, query processing and transaction management. It also describes different types of database users and the role of the database administrator.
This document provides an overview of a database systems course. It introduces key concepts like database management systems (DBMS), data modeling, normalization, SQL, and database design. The course objectives are to teach students how to design logical and physical database models, implement them using a DBMS, write SQL queries, and apply normalization techniques. It also discusses the roles of database administrators, designers, developers and end users in working with databases. Overall, the document outlines what students will learn about databases and how they are used in applications.
A DBMS is a software package that controls the creation, organization, storage, retrieval, sharing, and security of data in a database. It allows for multi-user access and uses query languages to search, sort, and retrieve data. There are several data models including hierarchical, network, relational, multidimensional, and object models. A DBMS is used in many applications such as banking, airlines, universities, sales, manufacturing, and more. It provides advantages like representing complex relationships, controlling redundancy, and sharing data across applications but also has disadvantages such as complex design, high costs, and required training.
CP 121 introduces database systems. The lecture covers file-based systems, the database approach, common database uses, users, DBMS components and functions, and advantages and disadvantages of databases. Key points include: File-based systems are limited but the database approach offers data sharing and consistency. A DBMS manages data storage, transactions, integrity, security and more. Database users include administrators, designers, developers and end users who access data through applications.
CS3270 - DATABASE SYSTEM - Lecture (1)Dilawar Khan
This document outlines the key topics to be covered in a database course, including: understanding database concepts and the relational model, learning SQL for data manipulation and definition, database design techniques like entity-relationship modeling and normalization, and hands-on experience with Microsoft SQL Server. The course objectives are to help students understand databases and DBMS systems, apply relational concepts and SQL, and be able to design database applications. The document also provides an introduction to databases by comparing traditional file-based systems with the database approach.
1. File Processing Systems
Billing Purchasing
Program Program
Accounts Buyer Inventory Vendor
Customer
receivable file file file
file
file
Accounts_Payable Sales Order Processing Payroll
Program Program Program
Inventory Employee
Vendor Invoice Customer
file file
file file file
2. Database Approach
Order Dept. Accounting Payroll
Dept. Dept.
Program Program Program
A B C
Ordering
Invoicing Payroll
filing
System System
System
Back Inventory Customer Inventory Employee
Orders Master Master Pricing Master
file file file file file
3. Database vs. File-based
• Miniworld as data source
– Universe of Discourse (UOD)
• Logically integrated files
• Intended users and applications
• Shared and Self-describing
Compared with file-based approach:
- program-data independence
- multiple view of data
- multi-user transaction processing
4. Types of Databases and
Database Applications
• Numeric and Textual Databases (e.g. IRS
CADE)
• Multimedia Databases (e.g. Cortina)
• Geographic Information Systems (GIS)
• Data Warehouses
• Real-time and Active Databases
5. Basic Definitions
• Database: A collection of related data.
• Data: Known facts that can be recorded and
have an implicit meaning.
• Mini-world: Some part of the real world about
which data is stored in a database. For example,
student grades and transcripts at a university.
• Database Management System (DBMS): A
collection of software to facilitate the creation
and maintenance of a DB.
• Database System: The DBMS software
together with the data. Sometimes, applications
are also included.
6. Database System Environment
Users/Programmers
Application Programs/Queries
DBMS
Software Software to Process Queries/Programs
Software to Access Stored Data
Stored DB
Stored
Definition
Database
(Meta-Data)
7. Why the Database Approach?
• Application needs constantly changing
• Ad hoc questions need rapid answers
• Need to reduce long lead times and high
cost in new application development
• Lots of data shared throughout the
organization
• Need to improve data consistency and
control access to data
• Substantial dedicated programming
assistance typically not available
8. Core DB Technology Trend
• Relational Database
• Distributed Database
• Multi-dimensional databases
• Object Relational Database
• Object-Oriented Database
• Multimedia Database
• Intelligent Database
• Data warehousing, data marts, data mining
• Web-based Databases
9. DB Time Line Web-based
Data Warehousing
Client-server
multimedia
heterogeneous
Data Management object-oriented
expert, distributed
Capability
SQL Standard
commercial DBMS
PC DBMS
ER model
network model
Relational Model: Codd
Hierarchical: IMS
file management
magnetic tape
1945 1961 1970 1976 1980 1985 1990 2000
10. DBMS
• A collection of software
– manage different applications for a multi-user
database system
– enable users to define/create and manipulate
data
• Basic functions:
– multiple user interfaces
– controlled redundancy
– integrity control
– security: authorization & protection
– concurrency & recovery control
11. Example Database (with
Conceptual Data Model)
• Mini-world for the example: Part of a
UNIVERSITY environment.
• Some mini-world entities:
– STUDENTs
– COURSEs
– SECTIONs (of COURSEs)
– (academic) DEPARTMENTs
– INSTRUCTORs
Note: The above could be expressed in the
ENTITY-RELATIONSHIP data model.
12. Example Database (with
Conceptual Data Model) – 2.
• Some mini-world relationships:
– SECTIONs are of specific COURSEs
– STUDENTs take SECTIONs
– COURSEs have prerequisite COURSEs
– INSTRUCTORs teach SECTIONs
– COURSEs are offered by DEPARTMENTs
– STUDENTs major in DEPARTMENTs
Note: The above could be expressed in the
ENTITY-RELATIONSHIP data model.
17. Features of the E-R Model
• Relationships are just as important as entities—
they are data that need to be stored in the DB
• Most relationships are binary, but they may be
ternary (or more!) as well
• Questions:
– What is the relationship between three binary
relationships and a ternary relationship?
– Why are there two relationships between projects
and employees?
18. Main Characteristics of the
Database Approach
• Self-describing nature of a database system:
A DBMS catalog stores the description of
the database. The description is called meta-
data). This allows the DBMS software to
work with different databases.
• Insulation between programs and data:
Called program-data independence. Allows
changing data storage structures and
operations without having to change the
DBMS access programs.
19. Main Characteristics of the
Database Approach – 2
• Data Abstraction: A data model is used to
hide storage details and present the users
with a conceptual view of the database.
• Support of multiple views of the data: Each
user may see a different view of the
database, which describes only the data of
interest to that user.
20. Main Characteristics of the
Database Approach – 3.
• Sharing of data and multi-user transaction
processing: allowing a set of concurrent users to
retrieve and to update the database.
• Concurrency control within the DBMS
guarantees that each transaction is correctly
executed or completely aborted.
• OLTP (Online Transaction Processing) is a
major part of database applications.
21. Database Users
Users may be divided into:
• those who actually use and control the
content (called “Actors on the Scene”)
• those who enable the database to be
developed and the DBMS software to be
designed and implemented (called
“Workers Behind the Scene”).
22. Database Users – 2.
• Actors
– Database administrators: responsible for
access to the database, for coordinating and
monitoring its use, acquiring
software/hardware resources, controlling its
use and monitoring run-time performance.
– Database Designers: responsible to define
the content, structure, constraints, and
functions or transactions against the database.
They communicate with the end-users and
understand their needs.
– End-users: use the data for queries, reports
and some even update database content.
23. Other DBS Personnel
• System analysts and application
programmers
• Operators and maintenance personnel
• Tool developers
• DBMS Designers and Programmers
24. Advantages of Using the
Database Approach
• More information from given data
• Ad hoc queries can be performed
• Redundancy can be reduced
• Inconsistency can be avoided
• Security restriction can be applied
• Data independence
– more cost-effective: reduced development
time, flexibility, economies of scale
25. Advantages of Using the
Database Approach - 2
• Controlling redundancy in data storage
and in development and maintenance.
• Sharing of data among multiple users.
• Providing persistent storage for program
objects (in Object-oriented DBMS’s – see
Chs. 20-22)
• Providing storage structures for efficient
query processing
26. Advantages of Using the
Database Approach – 3.
• Providing backup and recovery services.
• Providing multiple interfaces to different
classes of users.
• Representing complex relationships
among data.
• Enforcing integrity constraints on the
database.
• Drawing Inferences and Actions using
rules
27. Disadvantages of Using the
Database Approach
• Expensive
– hardware, software, personnel, processing
overhead, operating cost , etc.
• DBMS generality & overhead
=> performance issue
• Increased vulnerability to failure
• Recovery is more complex
When should you not use a DBMS????
28. Additional Implications of the
Database Approach
• Potential for enforcing standards:
– crucial for the success of database applications
in large organizations
– standards refer to data item names, display
formats, screens, report structures, meta-data
(description of data) etc.
• Reduced application development time:
– incremental time to add each new application is
reduced.
29. Additional Implications of the
Database Approach – 2.
• Flexibility to change data structures:
database structure may evolve as new
requirements are defined.
• Availability of up-to-date information: very
important for on-line transaction systems
such as airline, hotel, car reservations.
• Economies of scale: by consolidating data
and applications across departments
wasteful overlap of resources and
personnel can be avoided.
30. Historical Development of
Database Technology
• Early Database Applications:
Hierarchical and Network Models were
introduced in mid 1960s and dominated
the 70s. A bulk of the worldwide database
processing still uses these models.
• Relational Model based systems:
originally introduced in 1970 this model
was heavily researched and experimented
with in IBM and universities. Relational
DBMS products emerged in the 1980s.
31. Historical Development of
Database Technology – 2.
• Object-oriented applications:
OODBMSs were introduced in late 1980s
and early 1990s to cater to the need of
complex data processing in CAD and
other applications. Their use is not large.
• Data on the Web and E-commerce
Applications: Web contains data in
HTML with links among pages. E-
commerce is using standards like XML
(eXtended Markup Language).
32. Extending Database
Capabilities
• New functionality is being added to DBMSs in
the following areas:
– Scientific Applications
– Image Storage and Management
– Audio and Video data management
– Data Mining
– Spatial data management
– Time Series and Historical Data Management
• The above gives rise to new research and
development in incorporating new data types,
complex data structures, new operations and
indexing schemes in database systems.
33. When NOT to use a DBMS
• Main inhibitors (costs) of using a DBMS:
– High initial investment and possible need for
additional hardware.
– Overhead for providing generality, security,
concurrency control, recovery, and integrity
functions.
• When a DBMS may be unnecessary:
– If the database and applications are simple, well
defined, and not expected to change.
– If there are stringent real-time requirements that
may not be met because of DBMS overhead.
– If access to data by multiple users is not
required.
34. When NOT to use a DBMS – 2.
• When no DBMS may suffice:
– If the database system is not able to handle
the complexity of data because of modeling
limitations
– If the database users need special operations
not supported by the DBMS.
35. System Overview
OLCP
On-Line Complex Processing EIS
OLAP
data mining & On-Line Analytical Processing
knowledge discovery Data Warehousing
Data Marts
DSS
DP
OLTP
On-line Transaction Processing
Operational databases
Legacy systems