Data warehousing, performance management and business intelligence (BI) are top priorities for enterprise CIOs...
looking to improve business operations, access timely data and meet compliance regulations. This month's Executive Guide offers CIOs information and advice on the various tools and strategies necessary to implement and manage a data warehouse in the enterprise.
This guide is part of the SearchCIO.com Executive Guide series, which is designed to give IT leaders strategic guidance and advice that addresses the management and decision-making aspects of timely topics. For a complete list of topics covered to date, visit the Executive Guide section.
Data warehouse disaster recovery: What's the plan?
[James M. Connolly, Contributor]
It used to be that when you had a data warehouse, an analyst would run a bunch of queries against an offline copy of two years' worth of data, analyze it, and if disaster struck the data warehouse, it would simply be repopulated on a new system.
Not anymore. With data warehousing and BI increasingly tied to mission-critical applications, it's not always certain that a disaster recovery (DR) plan accounts for your data warehouse.
"Data warehousing and business intelligence did start out as being not mission critical," said Claudia Imhoff, president and founder of Intelligent Solutions Inc., a consultancy in Boulder, Colo. "People would extract data out of the operational system and run away into their own environment, completely separated from operations. But in the past 10 years, analytics have become quite critical."
Imhoff said businesses today directly tie data warehouses to key applications, such as stock price analysis, fraud detection and inventory planning. Not only are companies more dependent on BI, but the systems are also serving new, less technology-savvy audiences than when BI was used largely by analysts, Imhoff said. "If something goes wrong, they don't know how to fix it, and it really does cripple them in terms of making good business decisions.''
Learn more in "Data warehouse disaster recovery: What's the plan?." Also:
- Disaster recovery planning for CIOs (SearchCIO.com)
This Executive Guide lays out the foundation for a solid DR plan.
- Disaster recovery -- It's all about the data! (Bitpipe.com)
In this webcast, learn about best practices in the area of disaster recovery that will either help you kick-start a new DR plan, or help validate your current plan.
Data warehousing: ETL vs. ELT
[Info-Tech Research Group, Special to SearchCIO.com]
Extract, transform and load (ETL) was considered the most effective way to load information into a data warehouse. Early data warehouses were not viewed as being capable of handling the extensive processing required to perform the complex transformations involved in the warehouse load process. Instead, third-party tools like IBM's WebSphere DataStage and Informatica Corp. were leveraged to orchestrate data movement between source systems and the data warehouse. With the advancement in both hardware and data warehouse software technology, warehouse designers can now consider extract, load and transform (ELT) a viable option.
Loading a data warehouse
Loading a data warehouse can be extremely intensive from a system resource perspective. In companies with data sets greater than 5 terabytes, load time can take as much as eight hours depending on the complexity of the transformation rules. Most data warehousing teams schedule load jobs to start after working hours so as not to affect performance when a user query is being executed. However, as data volumes and warehouse subject areas increase, load times can increase even further and spill over into regular working hours.
Find out more in "Data Warehousing: ETL vs. ELT." Also:
- Definition: extract, transform, load (ETL) (SearchDataManagement.com)
In managing databases, extract, transform, load (ETL) refers to three separate functions combined into a single programming tool.
- ETL tools: What you do and don't want (SearchDataManagement.com)
Here are some core functions that most ETL tool vendors offer.
Data warehouse mergers: Best practices for CIOs
Data warehouse mergers and acquisitions, whether through vendor consolidation or other company mergers, require a solid, long-term plan. Forrester Research Inc.'s James Kobielus offers advice and guidelines for CIOs experiencing a data warehouse merger or acquisition.
Learn more about "Data warehouse mergers: Best practices for CIOs (A SearchCIO.com podcast)."
Gartner data warehouse DBMS Magic Quadrant 2007
[Hannah Smalltree, Site Editor, SearchDatamanagement.com]
Gartner's 2007 data warehouse DBMS Magic Quadrant found that the market is returning to tried-and-true IT mantras.
This year is notably different from a few years ago, when the data warehousing market was experiencing an unusual trend for the IT industry, according to Mark Beyer, research director with the Stamford, Conn.-based analyst firm and co-author of the study. Companies were willing to spend significant money, time and effort on data warehousing in order to achieve ideal implementations, Beyer said. This year, he found that companies are going back to IT basics, wanting to "do better with less." That is, they want to spend less money and time but achieve better results.
That's due in part to a maturing market, he explained. Data warehousing has been around for about 18 years now, and customers expect that software vendors have successfully and cost-effectively solved problems with data warehouse physics, mixed workloads and hardware platforms -- issues Beyer discussed in last year's study. There's another reason customers are less forgiving than in years past.
Learn more in "Gartner data warehouse DBMS Magic Quadrant 2007: New tools, old mantras." Also:
- Why you should build a data warehouse (SearchDataManagement.com)
Site expert Rick Sherman offers advice on how and why you should deploy data warehousing.
- Algorithms boost airtime (and profits) - (on the job) (CIO Decisions)
XOJet uses a data warehouse of trip information to plan flight times and maintenance schedules.
BI projects fail without C-level ownership
[Shamus McGillicuddy, News Writer]
When BI software projects fail, IT is often blamed. But the failure can usually be traced to lack of leadership, not technology.
In fact, a new survey finds that a lack of ownership by the right executive often leads to a disconnect between the vision of senior management and the way a project gets done.
"The core issue with business intelligence [not succeeding] isn't a technical issue," said Betsy Burton, vice president and distinguished analyst at Stamford, Conn.-based Gartner Inc. Rather, she said, it's the failure on the part of business leaders to make sure the organization gets the information it needs and leverages it in a way that makes sense with the business objectives.
"It's interesting," Burton said. "The symptom that people see is a lack of vision, a lack of strategy, a lack of linking supportive business intelligence back to systems. It's very easy for managers to say, 'Hey the data is wrong,' rather than take an introspective look. They should ask 'Have I given the organization a clear sense of what we're trying to get out of business intelligence? Am I really arming my people within my organization with a sense of the importance and the metrics so that they can deliver valuable information?' It's easier to point at the numbers and say, 'The numbers are wrong. Fix them.'"
Find out more in "Business intelligence projects fail without C-level ownership." Also:
- Real estate management pain points an IT issue (SearchCIO.com)
Managing 6,300 stores would have driven a lesser man to the edge. But when one CIO automated the process, it gave way for continued growth -- as well as cost savings.
- Creating successful business intelligence dashboards (expert webcast) (SearchCIO.com)
View this expert webcast to learn the secrets of successful BI dashboards. Find out more about recent design trends, success stories and new technologies that can enhance dashboard projects.