0% found this document useful (0 votes)
42 views3 pages

Understanding Physical Data Models

The physical data model outlines how a database will be constructed, detailing table structures, column names, data types, and relationships through primary and foreign keys. It differs from the logical data model and varies across different RDBMS due to specific data type requirements. Additionally, the document discusses database languages, including Data Definition Language (DDL) for schema definitions and Data Manipulation Language (DML) for data operations, highlighting procedural and nonprocedural DML types.

Uploaded by

govindanm223
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
0% found this document useful (0 votes)
42 views3 pages

Understanding Physical Data Models

The physical data model outlines how a database will be constructed, detailing table structures, column names, data types, and relationships through primary and foreign keys. It differs from the logical data model and varies across different RDBMS due to specific data type requirements. Additionally, the document discusses database languages, including Data Definition Language (DDL) for schema definitions and Data Manipulation Language (DML) for data operations, highlighting procedural and nonprocedural DML types.

Uploaded by

govindanm223
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

Physical Data Model:-

Physical data model represents how the model will be built in the
database. A physical database model shows all table structures, including
column name, column data type, column constraints, primary key, foreign
key, and relationships between tables.
Features of a physical data model include:-
 Specification all tables and columns.
 Foreign keys are used to identify relationships between tables.
 De-normalization may occur based on user requirements.
 Physical considerations may cause the physical data model to be
quite different from the logical data model.
 Physical data model will be different for different RDBMS. For
example, data type for a column may be different between MySQL
and SQL Server.
The steps for physical data model design are as follows:-
 Convert entities into tables.
 Convert relationships into foreign keys.
 Convert attributes into columns.
 Modify the physical data model based on physical constraints /
requirements.

The figure below is an example of a physical data model.


Comparing the logical data model shown above with the logical data
model diagram, we see the main differences between the two:
 Entity names are now table names.
 Attributes are now column names.
 Data type for each column is specified. Data types can be different
depending on the actual database being used.

1.6 DATABASE LANGUAGES


Database System Provides Two Types Of Languages.

 Data Definition Language


 Data Manipulation Language
Data Definition Language:-
A database schema by a set of definitions expressed by a special
language called DDL .DDL stands for tables that is stored in a specified file
called Data Dictionary. Data Dictionary is a file that contains meta
data( i.e. data about data).
The storage and access methods specified by database system are
called data storage and definition language.
Example:
 Create, Alter, and drop table commands.
 Create table account(account-number char(10),balance integer(4));
Data Manipulation Language:-

Data Manipulation means,


 Retrieval of information stored in database.
 Insertion of new information into the database.
 The deletion of information from the database.
 Modification of information stored in database.
 A DML is a language that enables users to access or manipulate
data as organized by appropriate data model.
Two types of DML are:-
Procedural DMLs:-
It requires a user to specify what data are needed and how to get
those data.

Nonprocedural DMLs :-
It requires a user to specify what data are needed without specifying
how to get those data.
 It is also referred to as declarative DMLs.
 It is easy to [Link] component of SQL language is
nonprocedural.
 A query is a statement requesting the retrieval of information.
The portion of a DML that involves information retrieval is called
a query language.
Example: Select, insert, Update, and Delete commands
Select customer. Customer _ name
From Customer
Where customer. Customer_ id=192-83-7465
1.7 RELATIONAL DATABASE
 A relational database store data in a series of tables so that the data
models a mathematical theory of relations.
 The model allows for queries based on projection, selection and join,
among other operations, and connect the data in the tables by way
of keys. The queries are expressed in a standard syntax called SQL,
the Standard Query Language, which is common to all various
vendors of relational databases.
 The theory of relations states that data is arranged as various sets
of tuples, called relations, where a tuple is collection of values for
attributes. A relation states which attributes it collects.

You might also like