MIS 563 COURSE PROJECT
Table of Contents
Findings…………………………………………………………… 2
Issues………………………………………………………………. 2
Opportunities………………………………………………….. 3
Recommendations………………………………………….. 3
Next Steps………………………………………………………. 3
Project Schedule…………………………………………….. 4
Database Design…………………………………………….. 4
Data Modeling & Data Marts…………………………. 4
Database Selection…………………………………………. 5
ETL Selection………………………………………………….. 5
Data Mining…………………………………………………… 6
Conclusions………….………………………………………… 8
References…………………………………………………….. 10
Findings:
ABC University has several departmental databases that perform specific functions for each department. Within these databases are several items that can be considered cross functional data among the different databases such as name and address. These items may or may not match each other in each database. This finding has ABC University seeking a streamlined way to manage their data and for users to access the data that is clean. With this, the University has proposed the creation and implementation of a data warehouse to house all the data from each one of these operational databases into one central location where all students, staff and faculty can access the data using a self service tool such as a report or a data connection to Microsoft Excel to pull data into pivot tables.
Issues: Listed below are some of the issues that are seen with the current process:
Redundant data across multiple platforms (i.e. Name, address, etc.), which can cause data validation and data quality issues.
Data normalization – how complex will this process be? Is every database from every department different and contain different data across different platforms?
A warehouse is needed to pull from these departmental databases via ETL. What are the performance issues that may come along with that pull?
What is the overall data integrity of these departmental databases? Who validates any of the data to ensure it is correct. How
Findings…………………………………………………………… 2
Issues………………………………………………………………. 2
Opportunities………………………………………………….. 3
Recommendations………………………………………….. 3
Next Steps………………………………………………………. 3
Project Schedule…………………………………………….. 4
Database Design…………………………………………….. 4
Data Modeling & Data Marts…………………………. 4
Database Selection…………………………………………. 5
ETL Selection………………………………………………….. 5
Data Mining…………………………………………………… 6
Conclusions………….………………………………………… 8
References…………………………………………………….. 10
Findings:
ABC University has several departmental databases that perform specific functions for each department. Within these databases are several items that can be considered cross functional data among the different databases such as name and address. These items may or may not match each other in each database. This finding has ABC University seeking a streamlined way to manage their data and for users to access the data that is clean. With this, the University has proposed the creation and implementation of a data warehouse to house all the data from each one of these operational databases into one central location where all students, staff and faculty can access the data using a self service tool such as a report or a data connection to Microsoft Excel to pull data into pivot tables.
Issues: Listed below are some of the issues that are seen with the current process:
Redundant data across multiple platforms (i.e. Name, address, etc.), which can cause data validation and data quality issues.
Data normalization – how complex will this process be? Is every database from every department different and contain different data across different platforms?
A warehouse is needed to pull from these departmental databases via ETL. What are the performance issues that may come along with that pull?
What is the overall data integrity of these departmental databases? Who validates any of the data to ensure it is correct. How
References: Integration Services (SSIS) Packages. (n.d.). Integration Services (SSIS) Packages. Retrieved February 6, 2014, from http://technet.microsoft.com/en-us/library/ms141134.aspx Integration Services | Microsoft SQL Server 2012 SQL Server Integration Services. (n.d.). SQL Server Integration Services. Retrieved February 6, 2014, from http://technet.microsoft.com/en-us/library/ms141026.aspx SQL Server Integration Services SSIS Tutorial: Creating a Simple ETL Package. (n.d.). SSIS Tutorial: Creating a Simple ETL Package. Retrieved February 6, 2014, from http://technet.microsoft.com/en-us/library/ms169917.aspx "Introduction to the Report Center." - SharePoint Server "Reporting Services (SSRS)." Reporting Services (SSRS). N.p., n.d. Web. 13 Feb. 2014. http://technet.microsoft.com/en-us/library/ms159106.aspx "Reporting | Microsoft SQL Server." Reporting | Microsoft SQL Server "Introduction to the Report Center." - SharePoint Server. N.p., n.d. Web. 13 Feb. 2014. http://office.microsoft.com/en-us/sharepoint-server-help/introduction-to-the-report-center-HA010174199.aspx "Reporting Services (SSRS)." Reporting Services (SSRS) "Reporting | Microsoft SQL Server." Reporting | Microsoft SQL Server. N.p., n.d. Web. 13 Feb. 2014. http://www.microsoft.com/en-us/sqlserver/solutions-technologies/business-intelligence/reporting.aspx