数据仓库及应用数据仓库无锡学习教案

1、会计学1数据仓库及应用数据仓库及应用(yngyng)数据仓库无锡数据仓库无锡第一页，共37页。第1页/共37页第二页，共37页。第2页/共37页第三页，共37页。第3页/共37页第四页，共37页。第4页/共37页第五页，共37页。第5页/共37页第六页，共37页。第6页/共37页第七页，共37页。网管系统财务管理系统市场分析决策系统Telcom DWSystem分析型大客户CRM系统信用度管理客服系统( C a l l C e n t e r 1000/180/112/170）系统其它电信专业网业务系统“九七工程”之营业管理生产调度系统（配线/配号/开通）112故障查修系统资源管理系统170/

2、催缴系统营业系统本地公司/IC卡/磁卡管理系统网上营业系统商务管理层省级计费结算计费帐务系统中心业务管理层网络及网元管理层电信网网元第7页/共37页第八页，共37页。第8页/共37页第九页，共37页。第9页/共37页第十页，共37页。第10页/共37页第十一页，共37页。PropertyOperationalData WarehouseResponse TimeSub-second to secondsSeconds to hoursData OperationDMLPrimarily read onlyNature of Data30-60 daysSnapshots over timeDa

3、ta OrganizationApplicationSubject, TimeSizeSmall to largeLarge to very largeData SourcesOperational, InternalOperational, Internal, ExternalActivitiesProcessesAnalysis第11页/共37页第十二页，共37页。第12页/共37页第十三页，共37页。第13页/共37页第十四页，共37页。第14页/共37页第十五页，共37页。第15页/共37页第十六页，共37页。ApplicationAdministrationStorage Manag

4、ementAnalysisData ManagementData ModelingData AcquisitionData Warehouse第16页/共37页第十七页，共37页。第17页/共37页第十八页，共37页。a specific department.第18页/共37页第十九页，共37页。PropertyData WarehouseData MartScopeEnterpriseDepartmentSubjectsMultipleSingle-subjectData SourceManyFewSize (Typical) TB TBImplement Time Months to y

5、earsMonths第19页/共37页第二十页，共37页。第20页/共37页第二十一页，共37页。Control: A department can completely control the data and processing that occurs inside a data mart.Cost: The cost of storage and processing is less, because the data marts machine is smaller than DWsCustomization: The data marts data is customized to

6、 suit the peculiar needs of the department.第21页/共37页第二十二页，共37页。第22页/共37页第二十三页，共37页。第23页/共37页第二十四页，共37页。Dependent Data Mart: The source is the data warehouse. The extraction, transformation, and loading process is easy. The data mart is part of the enterprise plan.Independent Data Mart: The source ar

7、e operational system external source. The extraction, transformation, and loading process is difficult. The data mart is built to satisfy analytical needs.第24页/共37页第二十五页，共37页。第25页/共37页第二十六页，共37页。第26页/共37页第二十七页，共37页。ODS looks very much like a data warehouse, such as subject-oriented, and integration.

8、 However, the remaining characteristics of an ODS are quite different from a data warehouse:Volatile: An ODS can be updated as a normal part of processing.Current-Values: An ODS typically contains daily, weekly, or even monthly data, but the data ages very quickly.Detailed Data: An ODS contains deta

9、iled data only.第27页/共37页第二十八页，共37页。Class I: A synchronous interface in which a very, very small amount of time lapses between an applications transaction and the reflection of the transaction in the ODS.Class II: If an hour or two passes from the time a transaction is created and interacted in the a

10、pplication environment until that transaction is reflected in the ODS.Class III: There may be a time lag between 12 hours and a day as transaction data is collected in the I&T interface.Class IV: The data is fed into the ODS directly from the data warehouse.第28页/共37页第二十九页，共37页。第29页/共37页第三十页，共37页

11、。Data WarehouseOperational Data Store ODSOperational Data Store ODSLegacy System Legacy System Legacy System Legacy System Call CenterWebEmailATMSFASupport Operational CRMSupport Analytical CRM第30页/共37页第三十一页，共37页。Identification Name Address Phone E-mailPreferences Opt in/out Medium Data sharingTransactions Purchases Cancellations ReturnsHH/Company AffiliationEvents Complaints Pre-approvals Inquiries Sales callsCustomer