Scribd
Upload
23 views

Chap 2

This document provides an overview of data models, including their structure, constraints, and operations, as well as various categories such as conceptual, physical, and logical data models. It discusses DBMS architecture types, data independence, and the languages used for database management, alongside user-friendly interfaces and system utilities. Additionally, it classifies DBMS based on data models and usage scenarios.

Uploaded by

khaniraj201
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
23 views

Chap 2

This document provides an overview of data models, including their structure, constraints, and operations, as well as various categories such as conceptual, physical, and logical data models. It discusses DBMS architecture types, data independence, and the languages used for database management, alongside user-friendly interfaces and system utilities. Additionally, it classifies DBMS based on data models and usage scenarios.

Uploaded by

khaniraj201
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Chap 2

Describe data models?


Data Model:
A set of ideas to describe how a database is structured, how to manage data, and
the rules it must follow.
Data Model Structure and Constraints:
Structure: Defines elements (like tables and records) and their relationships.
Constraints: Rules that ensure data stays correct and valid.
Data Model Operations:
Used to retrieve and update data using the data model’s structure.
 Basic operations: Insert, delete, update.
 User-defined operations: Custom tasks like calculating GPA or updating
inventory.
Categories of Data Models:
 Conceptual (High-Level): Shows data as users see it (e.g., entity-based,
object-based models).
1. Conceptual models give a high-level view of data.
2. They define entities, attributes, and relationships without technical
details.
3. Used in the early design phase to outline data structure.
 Physical (Low-Level): Describes how data is stored on a computer.

1. Physical data models describe how data is stored in a specific DBMS.


2. They include storage structures, indexing, and optimization techniques.
3. Tailored to the constraints of systems like MySQL, Oracle, or SQL Server.

 Implementation (Representational): Falls between conceptual and


physical, used in commercial DBMS (e.g., relational models).
 Self-Describing: Stores both data and its description (e.g., XML, key-value
stores, NoSQL).

 Logical data models are more detailed than conceptual ones.

1. They define data structure without depending on a specific DBMS.


2. Include tables, columns, data types, and relationships.
3. Act as a bridge between conceptual design and physical implementation.

Q. schemas versus instances

1. Database Schema: Describes the database structure, data types, and constraints.
2. Schema Diagram: A visual representation of the schema.
3. Schema Construct: A component of the schema, like STUDENT or COURSE.
4. Database State: The actual data in the database at a specific time, also called an
instance or snapshot

Q. DBMS architecture

DBMS design is based on its architecture.

Client/server architecture connects multiple PCs, web servers, and database servers over a
network.

It includes many PCs and workstations linked together.

DBMS architecture defines how users access the database.

Types:

 Database architecture can be seen as a single tier or multi-tier.


 But logically, database architecture is of two types like: 2-tier architecture and 3-tier
architecture.
1. 1-tier architecture:
In this architecture, the database is directly available to the user.
1-Tier architecture is used for development of the local application, where programmers
can directly communicate with the database for the quick response.
2. 2-tier architecture:
2-Tier architecture follows a client-server model.
Clients communicate directly with the database using APIs like ODBC and JDBC.
The client side handles user interfaces and applications.
The server manages queries and transactions.

3. 3-tier architecture:
3-Tier architecture adds a middle layer between client and server.
The client interacts with an application server, which then communicates with the database.
Commonly used for large web applications.
Q: Three schema architecture.

1. Internal Schema: Defines physical storage and access paths (e.g., indexes) using a
physical data model.
2. Conceptual Schema: Describes the overall database structure and constraints using a
conceptual or implementation data model.
3. External Schemas: Represents different user views, usually following the conceptual
schema's data model.

Q: Data independence.

 Logical Data Independence: Allows changes to the conceptual schema without affecting
external schemas or application programs.
 Physical Data Independence: Enables changes to the internal schema (e.g., file structures,
indexes) without altering the conceptual schema.

Q: DBMS language.

 DDL(data duplication): Used by DBAs and designers to define the database structure,
including internal and external schemas.
 DML(Data Manipulation Language): Used to retrieve and update data, often embedded in
languages like COBOL, C, C++, or Java.
 DBMS Library: Provides functions for database access from programming languages.

Types of dbms:
 High-Level (Non-Procedural) Languages: Includes SQL, used standalone or embedded in
programs.
 Low-Level (Procedural) Languages: Must be embedded in a programming language for
execution.

Q:dbms interface

 Stand-alone Query Interfaces: Directly enter SQL commands (e.g., SQL in Oracle).
 Programmer Interfaces: Embed DML in programming languages.
 User-Friendly Interfaces: Menu-based, forms-based, and graphical interfaces.
 Mobile Interfaces: Allow transactions via mobile apps.

Q. DBMS programming language interface.

 Embedded Approach: Uses embedded SQL (e.g., SQLJ for Java, SQL for C, C++).
 Procedure Call Approach: Uses APIs like JDBC (Java) and ODBC (other languages)
for database access.
 Database Programming Languages: Examples include PL/SQL in Oracle, which
extends SQL.
 Scripting Languages: PHP (client-side) and Python (server-side) for database
programming.

Q: user friendly dbms.

 Menu-Based (Web-Based): Common for web browsing.


 Forms-Based: Ideal for users filling out forms.
 Graphics-Based: Uses point-and-click or drag-and-drop actions.
 Schema Diagram Queries: Select data visually.
 Natural Language: Uses written English for queries.
 Combined Interfaces: Menus and forms often used together in web databases.

Q: dbms system utilities

 Data Loading: Import data from files, including conversion tools.


 Backup: Periodically save the database on tape.
 Reorganization: Modify database file structures.
 Performance Monitoring: Track and optimize performance.
 Report Generation: Create reports from data.
 Other Utilities: Sorting, user monitoring, data compression, etc.

Q: other tools
 Data Dictionary/Repository: Stores schema details, design decisions, user info, and
standards.
 Active Data Dictionary: Used by both DBMS software and users/DBAs.
 Passive Data Dictionary: Only accessed by users/DBAs.
 Application Development Tools: Help in database application creation.
 Examples:
o PowerBuilder (Sybase)
o JBuilder (Borland)
o JDeveloper 10G (Oracle)

Q: Classification of dbms

 Based on Data Model:


o Legacy: Network, Hierarchical.
o Current: Relational, Object-Oriented, Object-Relational.
o Recent: NOSQL (document, column, graph, key-value), Native XML DBMSs.
 Other Classifications:
o Single-User: Used on personal computers.
o Multi-User: Used in most DBMSs.
o Centralized: One database on a single computer.
o Distributed: Multiple databases across multiple computers.

You might also like