Add second year
This commit is contained in:
@ -0,0 +1,108 @@
|
||||
- #[[CT230 - Database Systems I]]
|
||||
- No previous topic
|
||||
- **Next Topic:** [[The Relational Model]]
|
||||
- **Relevant Slides:** 
|
||||
-
|
||||
- What is a **database**? #card
|
||||
card-last-interval:: 10.24
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.56
|
||||
card-next-schedule:: 2022-10-10T17:12:15.766Z
|
||||
card-last-reviewed:: 2022-09-30T12:12:15.767Z
|
||||
card-last-score:: 3
|
||||
- A **database** is ^^a collection of related data.^^
|
||||
-
|
||||
- What is the **Database Approach**? #card
|
||||
card-last-interval:: 4
|
||||
card-repeats:: 2
|
||||
card-ease-factor:: 2.08
|
||||
card-next-schedule:: 2022-10-11T10:35:42.411Z
|
||||
card-last-reviewed:: 2022-10-07T10:35:42.412Z
|
||||
card-last-score:: 3
|
||||
- A **single repository** of data (which may be distributed) is maintained that is **defined once** and then accessed by various users via a **DBMS**.
|
||||
- ## Database Management Systems
|
||||
- What is a **DBMS**? #card
|
||||
card-last-interval:: 8.32
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.08
|
||||
card-next-schedule:: 2022-10-11T18:42:02.196Z
|
||||
card-last-reviewed:: 2022-10-03T11:42:02.196Z
|
||||
card-last-score:: 3
|
||||
- The **DataBase Management System (DBMS)** is a collection of programs that facilitates the process of ^^defining, constructing, & manipulating^^ databases for various applications.
|
||||
- ### DBMS Capabilities #card
|
||||
card-last-interval:: 9.28
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.32
|
||||
card-next-schedule:: 2022-10-12T20:27:57.126Z
|
||||
card-last-reviewed:: 2022-10-03T14:27:57.127Z
|
||||
card-last-score:: 3
|
||||
- 1. **Define** database (DDL)
|
||||
2. **Manipulate** database (SQL)
|
||||
3. **Control** redundancy
|
||||
4. **Restrict** unauthorised access
|
||||
5. **Enforce** integrity constraints
|
||||
6. Provide multiple user interfaces / **views**
|
||||
7. Provide **concurrent access**
|
||||
8. Provide mechanism for **recovery**
|
||||
9. Provide **back-up**
|
||||
10. Allows representation of complex relationships between data (For efficiency & optimisation reasons)
|
||||
-
|
||||
- ### Disadvantages of DBMS approach #card
|
||||
card-last-interval:: 10.24
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.56
|
||||
card-next-schedule:: 2022-10-11T18:17:45.706Z
|
||||
card-last-reviewed:: 2022-10-01T13:17:45.707Z
|
||||
card-last-score:: 5
|
||||
- Strict schema & multiple tables / relations
|
||||
- Complexity
|
||||
- Size
|
||||
- Cost of DBMS
|
||||
- Additional hardware costs
|
||||
- Cost of conversion
|
||||
- Performance
|
||||
- Higher impact of failure
|
||||
- ### DBMS Users #card
|
||||
card-last-interval:: 4
|
||||
card-repeats:: 2
|
||||
card-ease-factor:: 2.08
|
||||
card-next-schedule:: 2022-10-11T10:38:38.838Z
|
||||
card-last-reviewed:: 2022-10-07T10:38:38.839Z
|
||||
card-last-score:: 3
|
||||
- **Administrators (DBA)** - accounts, passwords, privileges. Requiring constant vigilance
|
||||
- **System Analysts** - "What's required to solve a problem? What does the business need?"
|
||||
- **Designers** - ER diagrams, mapping ER diagrams to tables
|
||||
- **Application Programmers** - creating tables, adding data, creating queries
|
||||
- **End users**
|
||||
-
|
||||
- What is **Database Abstraction**? #card
|
||||
card-last-interval:: 9.28
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.32
|
||||
card-next-schedule:: 2022-10-10T19:18:04.573Z
|
||||
card-last-reviewed:: 2022-10-01T13:18:04.573Z
|
||||
card-last-score:: 3
|
||||
- **Database Abstraction** refers to the hiding of the details of data storage that are not needed by most database users.
|
||||
- The aim is to separate user's views of the database from the way that it is "physically" represented.
|
||||
- 3 ways in which data can be described:
|
||||
- **External:** user's view
|
||||
- **Conceptual:** logical structure as seen by DBA
|
||||
- **Internal:** DBMS and OS view of data
|
||||
- What is the database **schema**? #card
|
||||
card-last-interval:: 9.28
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.32
|
||||
card-next-schedule:: 2022-10-09T18:10:33.547Z
|
||||
card-last-reviewed:: 2022-09-30T12:10:33.548Z
|
||||
card-last-score:: 3
|
||||
- The database **schema** is the ^^logical structure of the database.^^
|
||||
- What is the database **instance**? #card
|
||||
card-last-interval:: 11.2
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.8
|
||||
card-next-schedule:: 2022-10-14T18:29:01.333Z
|
||||
card-last-reviewed:: 2022-10-03T14:29:01.333Z
|
||||
card-last-score:: 5
|
||||
- The database **instance** is ^^the actual content of the database at some point in time.^^
|
||||
-
|
||||
-
|
@ -0,0 +1,108 @@
|
||||
- #[[CT230 - Database Systems I]]
|
||||
- No previous topic
|
||||
- **Next Topic:** [[The Relational Model]]
|
||||
- **Relevant Slides:** 
|
||||
-
|
||||
- What is a **database**? #card
|
||||
card-last-interval:: 10.24
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.56
|
||||
card-next-schedule:: 2022-10-10T17:12:15.766Z
|
||||
card-last-reviewed:: 2022-09-30T12:12:15.767Z
|
||||
card-last-score:: 3
|
||||
- A **database** is ^^a collection of related data.^^
|
||||
-
|
||||
- What is the **Database Approach**? #card
|
||||
card-last-interval:: 4
|
||||
card-repeats:: 2
|
||||
card-ease-factor:: 2.08
|
||||
card-next-schedule:: 2022-10-11T10:35:42.411Z
|
||||
card-last-reviewed:: 2022-10-07T10:35:42.412Z
|
||||
card-last-score:: 3
|
||||
- A **single repository** of data (which may be distributed) is maintained that is **defined once** and then accessed by various users via a **DBMS**.
|
||||
- ## Database Management Systems
|
||||
- What is a **DBMS**? #card
|
||||
card-last-interval:: 8.32
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.08
|
||||
card-next-schedule:: 2022-10-11T18:42:02.196Z
|
||||
card-last-reviewed:: 2022-10-03T11:42:02.196Z
|
||||
card-last-score:: 3
|
||||
- The **DataBase Management System (DBMS)** is a collection of programs that facilitates the process of ^^defining, constructing, & manipulating^^ databases for various applications.
|
||||
- ### DBMS Capabilities #card
|
||||
card-last-interval:: 9.28
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.32
|
||||
card-next-schedule:: 2022-10-12T20:27:57.126Z
|
||||
card-last-reviewed:: 2022-10-03T14:27:57.127Z
|
||||
card-last-score:: 3
|
||||
- 1. **Define** database (DDL)
|
||||
2. **Manipulate** database (SQL)
|
||||
3. **Control** redundancy
|
||||
4. **Restrict** unauthorised access
|
||||
5. **Enforce** integrity constraints
|
||||
6. Provide multiple user interfaces / **views**
|
||||
7. Provide **concurrent access**
|
||||
8. Provide mechanism for **recovery**
|
||||
9. Provide **back-up**
|
||||
10. Allows representation of complex relationships between data (For efficiency & optimisation reasons)
|
||||
-
|
||||
- ### Disadvantages of DBMS approach #card
|
||||
card-last-interval:: 10.24
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.56
|
||||
card-next-schedule:: 2022-10-11T18:17:45.706Z
|
||||
card-last-reviewed:: 2022-10-01T13:17:45.707Z
|
||||
card-last-score:: 5
|
||||
- Strict schema & multiple tables / relations
|
||||
- Complexity
|
||||
- Size
|
||||
- Cost of DBMS
|
||||
- Additional hardware costs
|
||||
- Cost of conversion
|
||||
- Performance
|
||||
- Higher impact of failure
|
||||
- ### DBMS Users #card
|
||||
card-last-interval:: 4
|
||||
card-repeats:: 2
|
||||
card-ease-factor:: 2.08
|
||||
card-next-schedule:: 2022-10-11T10:38:38.838Z
|
||||
card-last-reviewed:: 2022-10-07T10:38:38.839Z
|
||||
card-last-score:: 3
|
||||
- **Administrators (DBA)** - accounts, passwords, privileges. Requiring constant vigilance
|
||||
- **System Analysts** - "What's required to solve a problem? What does the business need?"
|
||||
- **Designers** - ER diagrams, mapping ER diagrams to tables
|
||||
- **Application Programmers** - creating tables, adding data, creating queries
|
||||
- **End users**
|
||||
-
|
||||
- What is **Database Abstraction**? #card
|
||||
card-last-interval:: 9.28
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.32
|
||||
card-next-schedule:: 2022-10-10T19:18:04.573Z
|
||||
card-last-reviewed:: 2022-10-01T13:18:04.573Z
|
||||
card-last-score:: 3
|
||||
- **Database Abstraction** refers to the hiding of the details of data storage that are not needed by most database users.
|
||||
- The aim is to separate user's views of the database from the way that it is "physically" represented.
|
||||
- 3 ways in which data can be described:
|
||||
- **External:** user's view
|
||||
- **Conceptual:** logical structure as seen by DBA
|
||||
- **Internal:** DBMS and OS view of data
|
||||
- What is the database **schema**? #card
|
||||
card-last-interval:: 23.43
|
||||
card-repeats:: 4
|
||||
card-ease-factor:: 2.42
|
||||
card-next-schedule:: 2022-11-02T21:44:54.610Z
|
||||
card-last-reviewed:: 2022-10-10T11:44:54.610Z
|
||||
card-last-score:: 5
|
||||
- The database **schema** is the ^^logical structure of the database.^^
|
||||
- What is the database **instance**? #card
|
||||
card-last-interval:: 11.2
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.8
|
||||
card-next-schedule:: 2022-10-14T18:29:01.333Z
|
||||
card-last-reviewed:: 2022-10-03T14:29:01.333Z
|
||||
card-last-score:: 5
|
||||
- The database **instance** is ^^the actual content of the database at some point in time.^^
|
||||
-
|
||||
-
|
@ -0,0 +1,108 @@
|
||||
- #[[CT230 - Database Systems I]]
|
||||
- No previous topic
|
||||
- **Next Topic:** [[The Relational Model]]
|
||||
- **Relevant Slides:** 
|
||||
-
|
||||
- What is a **database**? #card
|
||||
card-last-interval:: 23.43
|
||||
card-repeats:: 4
|
||||
card-ease-factor:: 2.42
|
||||
card-next-schedule:: 2022-11-12T18:33:52.240Z
|
||||
card-last-reviewed:: 2022-10-20T08:33:52.241Z
|
||||
card-last-score:: 3
|
||||
- A **database** is ^^a collection of related data.^^
|
||||
-
|
||||
- What is the **Database Approach**? #card
|
||||
card-last-interval:: 4
|
||||
card-repeats:: 2
|
||||
card-ease-factor:: 2.08
|
||||
card-next-schedule:: 2022-10-11T10:35:42.411Z
|
||||
card-last-reviewed:: 2022-10-07T10:35:42.412Z
|
||||
card-last-score:: 3
|
||||
- A **single repository** of data (which may be distributed) is maintained that is **defined once** and then accessed by various users via a **DBMS**.
|
||||
- ## Database Management Systems
|
||||
- What is a **DBMS**? #card
|
||||
card-last-interval:: 8.32
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.08
|
||||
card-next-schedule:: 2022-10-11T18:42:02.196Z
|
||||
card-last-reviewed:: 2022-10-03T11:42:02.196Z
|
||||
card-last-score:: 3
|
||||
- The **DataBase Management System (DBMS)** is a collection of programs that facilitates the process of ^^defining, constructing, & manipulating^^ databases for various applications.
|
||||
- ### DBMS Capabilities #card
|
||||
card-last-interval:: 9.28
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.32
|
||||
card-next-schedule:: 2022-10-12T20:27:57.126Z
|
||||
card-last-reviewed:: 2022-10-03T14:27:57.127Z
|
||||
card-last-score:: 3
|
||||
- 1. **Define** database (DDL)
|
||||
2. **Manipulate** database (SQL)
|
||||
3. **Control** redundancy
|
||||
4. **Restrict** unauthorised access
|
||||
5. **Enforce** integrity constraints
|
||||
6. Provide multiple user interfaces / **views**
|
||||
7. Provide **concurrent access**
|
||||
8. Provide mechanism for **recovery**
|
||||
9. Provide **back-up**
|
||||
10. Allows representation of complex relationships between data (For efficiency & optimisation reasons)
|
||||
-
|
||||
- ### Disadvantages of DBMS approach #card
|
||||
card-last-interval:: 10.24
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.56
|
||||
card-next-schedule:: 2022-10-11T18:17:45.706Z
|
||||
card-last-reviewed:: 2022-10-01T13:17:45.707Z
|
||||
card-last-score:: 5
|
||||
- Strict schema & multiple tables / relations
|
||||
- Complexity
|
||||
- Size
|
||||
- Cost of DBMS
|
||||
- Additional hardware costs
|
||||
- Cost of conversion
|
||||
- Performance
|
||||
- Higher impact of failure
|
||||
- ### DBMS Users #card
|
||||
card-last-interval:: 4
|
||||
card-repeats:: 2
|
||||
card-ease-factor:: 2.08
|
||||
card-next-schedule:: 2022-10-11T10:38:38.838Z
|
||||
card-last-reviewed:: 2022-10-07T10:38:38.839Z
|
||||
card-last-score:: 3
|
||||
- **Administrators (DBA)** - accounts, passwords, privileges. Requiring constant vigilance
|
||||
- **System Analysts** - "What's required to solve a problem? What does the business need?"
|
||||
- **Designers** - ER diagrams, mapping ER diagrams to tables
|
||||
- **Application Programmers** - creating tables, adding data, creating queries
|
||||
- **End users**
|
||||
-
|
||||
- What is **Database Abstraction**? #card
|
||||
card-last-interval:: 19.01
|
||||
card-repeats:: 4
|
||||
card-ease-factor:: 2.18
|
||||
card-next-schedule:: 2022-11-08T08:37:10.629Z
|
||||
card-last-reviewed:: 2022-10-20T08:37:10.629Z
|
||||
card-last-score:: 3
|
||||
- **Database Abstraction** refers to the hiding of the details of data storage that are not needed by most database users.
|
||||
- The aim is to separate user's views of the database from the way that it is "physically" represented.
|
||||
- 3 ways in which data can be described:
|
||||
- **External:** user's view
|
||||
- **Conceptual:** logical structure as seen by DBA
|
||||
- **Internal:** DBMS and OS view of data
|
||||
- What is the database **schema**? #card
|
||||
card-last-interval:: 23.43
|
||||
card-repeats:: 4
|
||||
card-ease-factor:: 2.42
|
||||
card-next-schedule:: 2022-11-02T21:44:54.610Z
|
||||
card-last-reviewed:: 2022-10-10T11:44:54.610Z
|
||||
card-last-score:: 5
|
||||
- The database **schema** is the ^^logical structure of the database.^^
|
||||
- What is the database **instance**? #card
|
||||
card-last-interval:: 11.2
|
||||
card-repeats:: 3
|
||||
card-ease-factor:: 2.8
|
||||
card-next-schedule:: 2022-10-14T18:29:01.333Z
|
||||
card-last-reviewed:: 2022-10-03T14:29:01.333Z
|
||||
card-last-score:: 5
|
||||
- The database **instance** is ^^the actual content of the database at some point in time.^^
|
||||
-
|
||||
-
|
Reference in New Issue
Block a user