90 likes | 239 Views
Goals. Deploy a BI foundation that meets scaling requirements, offers speed, flexibility and simplicity to delivery requirements Provide users and customers with a self-service model enabling ad-hoc analysis, dashboards, canned reporting, and analytics
E N D
Goals • Deploy a BI foundation that meets scaling requirements, offers speed, flexibility and simplicity to delivery requirements • Provide users and customers with a self-service model enabling ad-hoc analysis, dashboards, canned reporting, and analytics • Provide a 3-5 year scalable architecture that accommodates 50-100 terabytes • Maintain a high performance in a large, mixed user environment • Make data management more efficient, less expensive, and very predictable • Reduce TCO relating to system upgrades and support
Why Netezza First • Presentations, contacts with customers, and discussions took place with both Teradata and Netezza • We carefully reviewed what was presented and proposed to our company • Even if the idea was at one point to have both vendors on site for concurrent POCs, the Netezza representation had far more appeal and we decided that the most appropriate sequence was to start with this vendor
Identification of Key Evaluation Criteria • “Game-changing” ad hoc query and analytical SQL performance of at least 30X current • Ability to load huge volumes of site traffic data within acceptable load windows and SLAs (at least 10X current) • Data compression of at least 2:1 with zero negative impact to performance • Enterprise-class administration and backup/recovery capabilities • Ease of administration and quality vendor support
Identify the Tests to be Performed • Various MicroStrategy reports from the CPOR application run on Netezza and current Production environment • Run individually and in various levels of concurrency • Analytical SQL run against Site Traffic data in both environments • Actual queries analysts struggle with in Production due to performance issues • Informatica ETL workflows for loading Site Traffic data • Includes hourly loads and post-processing (sessionizing) • Various administrative scenarios and routine maintenance • User administration, component failover, backup and recovery
Next Steps • Fix the network surrounding the platforms • Provide training to Delivery side of the teams • Partition of the Toaster (QA/Dev/Prod) • Finalize SLA with Ops (who owns what) • Transition to Ops • Provide “playground” to the Delivery teams • New focus for each of the BIT3 members to provide guidance, mentorship, and standards to Delivery teams across the company