Please enable JavaScript.

Coggle requires JavaScript to display documents.

Database Systems, COURSE - Coggle Diagram

- - - - SQL
  - - - XML
      - HTML
  - - - Document Stores
        
        Mongo DB
        
        Amazon Dynamo DB
      - Column Stores
        
        Cloudera
        
        Cassandra
        
        HBase (Hadoop based)
      - Key-value Stores
        
        Riak
        
        Berkeley DB
        
        Aerospike
      - Graph Data Stores
        
        Neo4j
        
        GraphBase
        
        Titan
- - - - Create and Modify the structure of the data
      - Manipulate data records and Perform CRUD tasks
    - - GUI
      - SQL
    - - Relations (Tables)
      - Domains (Columns, Fields, or Attributes)
      - Tuples (Records, or Rows)
  - - - Database Diagram (Entity Relationship)
        
        Primary Keys-Surrogat
        
        Design Table Using QuickDBD
        
        Data Type
      - Constraint
        
        Unique value
        
        Null vs Not Null
        
        Default Value
        
        Indexes
        
        Check Constraint (Price>0)
    - - Foreign Key
      - Optionality (Null or Not Null)
      - Cardinality (Unique or Not)
      - One to Many Relationships
      - One to One Relationships
      - Many to Many Relationships
      - Self Joins or Recursive Relationship
      - Cascade Changes
    - - Data Definition queries
      - Data Manipulation queries
      - DB View
  - - - Columns Only Store a Single Piece of Data. It can have composite primary key. but no two values are stored in single cell.
    - - Table use only a single column as their PK. No attribute excpet the key should determine the other attribute:FD. If the key is composite then the whole composite key should determine other attributes in the table, not the partial key. We should divide into other tables such that only key dtermines the attributes not partial keys. All non key attributes are fully functional dependent on primary key not just partially dependent on the primary key . We can correct it by having seperate table for every funvtional dependent attributes. Which means remove right hand side attributes of if then logic expression.
    - - All of the nonkey fields are independent from any other non key field. None of the attributes should determine other asttributes.. Almost similar ot 2NF which states only primary keys should determine other attributes, but in this case Only primary key should determine others attributes and also none of the other attributes should determine anyother attributes in the table.. Which means no Transitive dependency.
- - - - Conceptual (high-level, semantic) data models. Ex: ER Model
      - Physical (low-level, internal) data models
      - Implementation (representational) data models
      - Self-Describing Data Models.
        Ex: XML, some NOSQL systems etc.
  - - - 1. The external schemas for end users
      - 2. The conceptual schemas at the conceptual level representing the whole database
      - 3. The internal schemas at the internal level which describe physical storage structures and access paths of the database
  - - - The DDL is used to define both the conceptual (e.g., relational) and external (e.g., views) schemas.
      - SQL is used in the relational model for the DDL tasks
        
        Three subtasks for each of the three levels
        
        Physical (as storage definition language-SDL done by DBA)
        
        Conceptual (DDL)
        
        External (as view definition language –VDL)
  - - - DBMS software, hardware, application programs, user interface processing software
    - - Print server, File server, DBMS server, Web server, Email server
- - - - Requirements analysis
        
        Conceptual database schema design
        
        Logical Design - Implementation with a commercial DBMS
        
        Physical database design
        
        Methodologies
        
        Entity Relationship (ER) Diagrams
        
        Enhanced Entity Relationship (EER) Diagrams
        
        Use of Design Tools in industry
        
        The UML (Unified Modeling Language) Class Diagrams
    - - Functional Analysis
        
        Application program design
        
        Transaction implementation
        
        Application Programs
  - - - Entities: Entities are specific things or
        objects in the mini-world that are represented in the database
      - Attributes are properties used to describe an entity.
        
        Types
        
        Simple: Each entity has a single atomic value for the attribute. Ex: Sex
        
        Composite: The attribute may be composed of several components. Ex: Address
        
        Multi-Valued: An entity may have multiple values for that attribute. Ex: Colors
    - - Entities with the same basic attributes are grouped or typed into an Entity type.
      - An attribute of an entity type for which each entity must have a unique value is called a key attribute of the entitype.