Difference between revisions of "Database Terminology"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
==Database Basics== | ==Database Basics== | ||
=== Conceptual Model === | |||
* Captures the functional and informational needs of a business | |||
* Is based on current needs but may reflect future needs | |||
* addresses the needs of a business(what is conceptually ideal), but does not address its implementation (what is physically possible) | |||
===RDBMS - Relational Database Management System=== | ===RDBMS - Relational Database Management System=== | ||
===Schema - Set of db objects representing part or all of a business enterprise | ===Schema - Set of db objects representing part or all of a business enterprise | ||
Revision as of 21:04, 20 September 2017
Database Basics
Conceptual Model
- Captures the functional and informational needs of a business
- Is based on current needs but may reflect future needs
- addresses the needs of a business(what is conceptually ideal), but does not address its implementation (what is physically possible)
RDBMS - Relational Database Management System
===Schema - Set of db objects representing part or all of a business enterprise
- A character is the basic unit of data, and it can be a letter, number or special symbol
- A group of related characters (for example, the characters that make up a customer's name) is called a field)
- A field represents one attribute or characteristic (the name, for instance) of the customer.
- A collection of fields about one customer (for example, name, address, city, state, and zip) is called a record
- A group of records about the same type of entity (such as customers or inventory items) is stored in a file.
- A collection of interrelated files-such as those relating to customers, their purchases, and their payments- is stored in a database.
Database Design System Development Life Cycle (SDLC)