Database and data warehousing design business plan examples

Introduction2

Design process3
Design best practices3
Business support schema5
Entity Relationship5

Reference9

Introduction
Businesses tend to utilize data at their disposal to influence the strategic competitive edge. This calls for database systems that transform raw data into meaningful information. Many organizations employ the use of relational databases in spite of enormous volumes and sources of data to be analyzed. Acting in the capacity of a CIO of Terabyte Ltd, I intend to come up with a database that collects data by use of the following mechanism (Stephens, 2010);
Web Analytics
Operational analysis.
Data warehousing is a process of storing the entire company’s data in a big repository meant to provide seamless integration and guide in the process of decision making. In a data warehouse, operational data needed for business operations are continuously changed. Tables in this database are continually refreshed by removing old data. On the contrary, patches of old data are still available and their accumulation leads to voluminous amounts ranging in terabytes. This distinct feature has enabled many organizations to utilize the massive storage capabilities of warehouses to realize remarkable benefits in the way they handle their data (Ponniah, 2011).
The process of analyzing data for decision making purposes in the business becomes simplified due to the decision support tools associated with the warehouse. Thus generally, data warehousing is proven to be superior than and more useful than executive information systems and decision support systems.
Design process
The process of designing a database is not exceptionally different from the standard software development process. The stages include,
– Problem definition.
– Analysis and requirement.
– Data modeling.
– Design and prototyping.
– Development and documentation.
– Test, review and operation.
Design best practices
In the design process, the design team comprising of programmers, database administrators and information security experts should critically evaluate each an every phase to come up with a standard warehouse that satisfies the organization’s objectives (Sam S. Lightstone, 2010).
Among the best practice considerations include;
The data house is structured into functional groups or specialty areas such as employee details, departments or project characteristics. Using an entity relationship data model, abstract schemas are designed and denoted with various entities. Likewise, in object-oriented data model, objects are denoted with different classes with a provision that segregate functional primary data from processes that are involved in creation modification of such data. The functional areas are primarily mapped out during the problem definition stage and should be independent of other processes (Stephens, 2010). This is one crucial stage that should not be overlooked by the design team in order to produce a functional database.
Terabyte desires a database that can be easily integrated. The design team should therefore standardize common data presentation to allow mapping.
A data warehouse that supports both distributed and centralized data is beneficial for a growing business such as Terabyte. Data distributed over the network should be readily supported by the system.
The primary objective of any design is to achieve usability. Data warehousing is no exception. The user interface should be designed in a way to deliver better user interaction as well as effective system usage. SQL is the most preferred interface for a data warehouse system because of its unique interface and multidimensional view of relational data. In addition it provides the options for retrieving, analyzing and formatting data.
Another important characteristic of a well-organized warehouse is history rewriting capabilities. The design team should concentrate on designing and implementing the if analysis to achieve successful data rollback. To achieve this, designers should consider introducing data in appropriate granularity level to permit administrators to update the rights of historical data.
Lastly, the warehouse should be designed in a way that allows flexibility. Considering the rapid growth of the company, data schemas should always have the capacity to accommodate new incoming data. Terabyte is continually craving for faster data retrieval mechanisms, thus granularity and the sort of the data should be critically well thought-out.
Business support schema
Entity Relationship
In order to develop an entity relationship diagram, different aspects are put in place. To start with, we define the major business that needs to be automated. This forms the entities. Attributes are defined by the various storage fields and tables in the database. In the case of Terabyte we are going to implement a data warehouse that bears the resemblance to a relational database system (Sam S. Lightstone, 2010).
Data Inputs And Outputs
The process will involve the translation of ideas into sophisticated plan that will permit the development team to put together a relational data warehouse schema in lieu of the key functionality of the warehouse.
Data is transferred from various databases to the new created warehouse where cleaning, verification and validation is conducted before it is finally stored in designated marts. The various sources of data represent sources such as manufacturer’s, customers, suppliers, the management and other third party conduct. For instance the employee table link to the particular data marts (Ponniah, 2011).
Conclusion
We can conclude that the data warehouse in an organization such as Terabyte is equipped with tools that ensure that data is organized and scalable at any given moment to put up with the dynamic operational data. Operational data systems try to minimize their tables as much as possible by scrubbing out old data. However, the warehouse accommodates patches of data which swell with time to reach trillions of bytes. The massive storage capabilities in a warehouse can easily accommodate this amounts of data (Ponniah, 2011).
Reference
Ponniah, P. (2011). Data Warehousing Fundamentals for IT Professionals. Paulraj Ponniah.
Sam S. Lightstone, T. J. (2010). Physical Database Design: the database professional’s guide to exploiting indexes, views, storage, and more. Morgan Kaufmann.
Stephens, R. (2010). Beginning Database Design Solutions. John Wiley & Sons.