Discussion of Data Storage and Database Management
This is an excerpt from the paper...
Too much data can be a problem with database storage. When there is too much data, the data becomes an impediment that stands in the way of seeing and understanding the data that is important to the business. Thus, it is vital to keep data pared down to what is really usable and helpful. With too much data, information systems can become bogged down and system turnaround time can slow, there is a greater chance of the wrong data being used, and it is difficult and time-consuming-if not impossible-to sort through the data when needed to find a particular piece of data that is necessary for a task. Moreover, since companies must back up their data nightly and invest in data storage, situations similar to Southern Co.'s, where the company was "diligently backing up nightly...outdated or extraneous data, such as casual e-mail messages" can represent a substantial cost to the business without producing any business advantage (Jackson-Higgins, 2003, p. 1). As Calpine Corp. found out, it is important to "organize and analyze the data," not just capture it all; Calpine "nearly drowned in its own firewall event logs" (Jackson-Higgins, 2005, p. 1).
. . .
Some common words found in the essay are:
Southern Co, Calpine Corp, Retrieved July, , Southern Co's, October-December Enterprise, july 27 2008, 27 2008, retrieved july 27, References Bernard, data management, retrieved july, july 27, SETLabs Briefings, data storage, jackson-higgins 2003, data stored, organizational data, trends affecting organizational, affecting organizational data, jackson-higgins 2005, access data, organizational data storage,
Approximate Word count = 791
Approximate Pages = 3 (250 words per page)
More Essays on Discussion of Data Storage and Database Management
|