What should not be in a database?
- Which is not the feature of database?
- When should you not use a database?
- What should be stored in a database?
- What constitutes a bad database design?
Which is not the feature of database?
Which is not the feature of database: Data redundancy.
When should you not use a database?
When Not to Use a DBMSHigh initial investment in hardware, software, and training.The generality that a DBMS provides for defining and processing data.Overhead for providing security, concurrency control, recovery, and integrity functions.Simple, well-defined database applications that are not expected to change at all.
What should be stored in a database?
The purpose of every database is to store information, texts, images, even media files. All dynamic modern websites rely on one or more databases for storing articles and other published content, information about the users, contact information, connections to other websites, ads, etc.
What constitutes a bad database design?
A badly designed database has the following problems: Related data is scattered over various tables. A change must be updated at many places. It's possible that the information is only half present, it's there in one table, but missing in another one.
Related Questions
-
Anonymous2 weeks ago
Expert answer2 weeks ago -
Anonymous2 weeks ago
Expert answer2 weeks ago -
Anonymous2 weeks ago
Expert answer2 weeks ago -
Anonymous2 weeks ago
Expert answer2 weeks ago -
Anonymous2 weeks ago
Expert answer2 weeks ago -
Anonymous2 weeks ago
Expert answer2 weeks ago -
Anonymous2 weeks ago
Expert answer2 weeks ago