Tags

0NF (Zero Normal Form)

• 2NF: The Missing Use Case
• 5NF: The Missing Use Case

1nf

• 2NF: The Missing Use Case

2NF (2nd Normal Form)

• 2NF: The Missing Use Case
• 5NF: The Missing Use Case
• What's in a Name? Assume: Nothing!

3NF (3rd Normal Form)

• Normalize for Better Performance

4NF (4th Normal Form)

• 2NF: The Missing Use Case
• 3-Tier 3/3: Implications of Changing the Application-Data Relationship
• Normalize for Better Performance
• What's in a Name? Assume: Nothing!
• 4NF: We Do It All the Time
• The Anti-Normalization Myths

5NF (5th Normal Form)

• 5NF: The Missing Use Case

Auditability

• 3-Tier 3/3: Implications of Changing the Application-Data Relationship

Burroughs DMSII

• 3-Tier 3/3: Implications of Changing the Application-Data Relationship
• 3-Tier 1/3: The Expanding Attack Surface of 3-Tier Architecture

Candidate Key

• 5NF: The Missing Use Case

Data Confidentiality

• 3-Tier 3/3: Implications of Changing the Application-Data Relationship
• 3-Tier 2/3: Change the Application-Data Relationship with Stored Procedures

Data Definition

• 2NF: The Missing Use Case
• 5NF: The Missing Use Case
• What's in a Name? Assume: Nothing!
• The Anti-Normalization Myths

Data Integrity

• 3-Tier 3/3: Implications of Changing the Application-Data Relationship
• 3-Tier 2/3: Change the Application-Data Relationship with Stored Procedures

Data Security

• 3-Tier 3/3: Implications of Changing the Application-Data Relationship
• 3-Tier 2/3: Change the Application-Data Relationship with Stored Procedures
• 3-Tier 1/3: The Expanding Attack Surface of 3-Tier Architecture

Denormalization

• The Case Against Denormalization

ERD (Entity-Relation Diagram)

• 5NF: The Missing Use Case

FK (Foreign Key)

• What's in a Name? Assume: Nothing!

Normalization

• 2NF: The Missing Use Case
• 5NF: The Missing Use Case
• 3-Tier 3/3: Implications of Changing the Application-Data Relationship
• Normalize for Better Code
• Normalize for Better Performance
• The Anti-Normalization Myths

Oracle

• 3-Tier 3/3: Implications of Changing the Application-Data Relationship
• 3-Tier 2/3: Change the Application-Data Relationship with Stored Procedures
• 3-Tier 1/3: The Expanding Attack Surface of 3-Tier Architecture

Performance

• Normalize for Better Performance

PK (Primary Key)

• What's in a Name? Assume: Nothing!

PostgreSQL

• 3-Tier 3/3: Implications of Changing the Application-Data Relationship
• 3-Tier 2/3: Change the Application-Data Relationship with Stored Procedures

Presentation

• 3-Tier 3/3: Implications of Changing the Application-Data Relationship

Programming

• 3-Tier 3/3: Implications of Changing the Application-Data Relationship
• 3-Tier 2/3: Change the Application-Data Relationship with Stored Procedures
• 3-Tier 1/3: The Expanding Attack Surface of 3-Tier Architecture
• Normalize for Better Code

Schema Updates

• 3-Tier 3/3: Implications of Changing the Application-Data Relationship

SQL Standards

• 3-Tier 3/3: Implications of Changing the Application-Data Relationship

WebRTC

• Wishlist: Personal WebRTC Server