two 200 word response to the attachments. APA format. No Plagiarism.

Dis_1_sri_kol.docx

Home >Business & Finance homework help >Management homework help >two 200 word response to the attachments. APA format. No Plagiarism.

Running Head: DISCUSSION 1

Discussion 1

The role of a database is to store and retrieve data. A properly implemented database has to do it in a most efficient manner. Since data is becoming more ubiquitous and complex, a good design and implementation of a database is crucial. Poor databases can not only be slow and inefficient but also result in data loss. (Harrington, 2016)

I’ll talk about things that make a poorly designed database that I’ve encountered while working in a startup. I’ll also include few bad database examples that I’ve read in various articles.

Application specific database:

Every application is unique in its own way. Knowing the data well and choosing the right data structures and record sizes will ensure that the database works well with the real data. This requires a good understanding of the real-world data and various possibilities of data ranges and sizes have to be analyzed. Any failure to do so might result in database not working with real data. (Bancilhon et al., 1992)

Primary keys:

Primary keys should never be changed. Primary keys are often used in other indexes and as foreign keys changing them will create complexities. Primary keys have to be as small as possible and integer value instead of character. This is because integers take up less space than characters. Smaller keys will result in smaller index and less pages will be used in cache. (Bancilhon et al., 1992)

Frequently accessed data is scattered across various tables:

When data that has to be collectively retrieved frequently is scattered across various tables, it makes things unnecessarily complex. Instead such data can be stored in the same table. This makes accessing the data much simpler. (Ferreira, 2011)

Inflexible and hard to extend:

With the ever-increasing amount of data, quite frequently new kinds of data have to be collected and updated with the existing database. In such a scenario, the database has to be flexible and easily updatable. Trying to fix everything with code instead of optimizing the database can accomplish the short-term goal but can make things complicated for future updation. (Ferreira, 2011)

References

Harrington, J. L. (2016). Relational database design and implementation. Morgan Kaufmann.

F. Bancilhon, P Kanellakis. Building an Object-Oriented Database System: The Story of 02.Morgan Kaufmann Publishers, 1992.

Ferreira, D. F. (2011). Sisvar: a computer statistical analysis system. Ciência e agrotecnologia, 35(6), 1039-1042.