• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Relational Database and mysql insight
 

Relational Database and mysql insight

on

  • 171 views

 

Statistics

Views

Total Views
171
Views on SlideShare
171
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • This presentation demonstrates the new capabilities of PowerPoint and it is best viewed in Slide Show. These slides are designed to give you great ideas for the presentations you’ll create in PowerPoint 2011!For more sample templates, click the File menu, and then click New From Template. Under Templates, click Presentations.

Relational Database and mysql insight Relational Database and mysql insight Presentation Transcript

  • RELATIONAL DB AND MYSQL INSIGHT
  • Outline Relational DB Database requirement MySQL We have features for every step of the way
  • Relational database management system 1. Purpose 2. Normalization
  • History ● Wikipedia : A relational database management system (RDBMS) is a database management system (DDMS) that is based on the relational model as introduced by E. F. Codd, of IBM's San Jose Research Laboratory. Many popular databases currently in use are based on the relational database model. ● Relational database theory uses mathematical terminology, which are roughly equivalent to that of Normalization: RDBMS ~ NORMALIZATION
  • NORMALIZATION • Normalization was first proposed by Codd as an integral part of the relational model. • It encompasses a set of procedures designed to eliminate nonsimple domains (non-atomic values) and the redundancy (duplication) of data, which in turn prevents data manipulation anomalies and loss of data integrity.
  • NORMALIZATION PROCESS
  • Normal Form
  • Database Requirement Stylize, edit, and animate your media
  • Requirement? • Much depends on the application  However we can think of something like – In application level: • Speed (performance) • Availability • Scalability – In transaction level: • ACID (atomicity, consistency, isolation, durability) – Something else?: • Compression , etc ….
  • Just clarify the ACID • Atomicity: – All or nothing – One part of the transaction fails (for failures, errors, crashes), the entire transaction fails • Consistency: – Bring database from a valid state to another • Isolation: – The effect of an incomplete transaction might be or might not be visible to another • Durability: – The effect of a completed transaction must be stored permanently.
  • MYSQL View your slides from anywhere!
  • Logical architecture
  • How does MySQL handle queries? • Concurrency control – Locking (READ, WRITE) – Table lock and row lock • Concurrency control – Locking (READ, WRITE) – Table lock and row lock • Transaction – Isolation level (remember ACID?)
  • Performance • Depends on: – Table design • Schema • Index – Query • Some query beats all index • Query covered index – Storage engine • Sometimes affect performance much more than hard ware – Locking strategy – Etc, … – Hardware • RAM (should be enough to store index) • Hardrive, etc…
  • Availability
  • GLHF