Skip to content
- How do you decide on which normal form is appropriate for our project?
- How does the crow’s foot notation show transitivity among different objects?
- Would a software engineer need to change their technique for database design if there is an extremely large amount of data as opposed to a very small amount?
- When would it be necessary to store binary data in a table for database design?
- In what scenario does it make sense to not conform the data set to the next normal form?
- Why do we need alternate keys when the primary key is always present?
- What are some circumstances under which normalization might make storage more difficult, if there are any?
- What are data structures are used in databases? Is a linked list structure used? Arrays? Does it matter?
- don’t get the column indexing thing. What exactly is column indexing and how does it make selections more efficient?
- Are terms like “third normal form” used often in discussions about databases, or is there just an assumption that the best practice when building a database is to put in 3NF? How common is it to move between normal forms?
- How are some ways that crowfoot notation can be used in software engineering?
- Relationships between two entities can be easy to understand, but how do charts with relationships between many entities work?
- What are consequences of not creating UML design?
- What is the common mistake when creating a UML design?
- What can be the uses of relational databases in a classroom at Kenyon? Discuss how the user can make classroom management more efficient and effective?
- What are examples of data normalization?
- What are some examples of entry relationships?
- Why is it best to start with a theoretical functioning of the database before actually constructing it?
- Is it absolutely vital for companies that are scaling to go up to 5NF?
- When do programmers usually use crow’s feet notation? Is it used often and only for representing relationships in databases? Are there more complex notations available?
- Is database normalization something that should be done in consultation with the database generator? What are the dangers of not doing this consultation?
- How can the normalization of databases prevent data redundancy?
- Why do we need a “bridge table” in a many-to-many relationship?
- Why is database important in a lot of software and system Design?
- Is that necessary to normalize a database?
- In practice, what are the conditions that would cause the developer to create a child table of the original database? Please give example
- Why is data redundancy so important to eliminate?
