Um data warehouse (ou armazém de dados) armazena grandes quantidades de dados que foram coletados e integrados de várias fontes. Como as organizações dependem desses dados para aplicar analytics ou criar relatórios, eles precisam ser formatados consistentemente, além de facilmente acessíveis – duas qualidades que definem o uso de data warehouses e os torna essenciais para as empresas de hoje.
História dos data warehouses
Nos anos 1970 e 1980, os dados começaram a proliferar e as empresas precisaram encontrar uma maneira fácil para armazená-los e acessá-los. O cientista da computação Bill Inmon, que é considerado o pai do armazenamento de dados, começou a definir o conceito nos anos 1970 e é o responsável pela criação do termo “data warehouse”. Em 1992, ele publicou um livro intitulado Building the Data Warehouse, tido como uma fonte fundamental para a tecnologia de armazenamento de dados. A definição de Inmon de data warehouse utiliza uma abordagem “de cima para baixo”, em que um repositório central é estabelecido primeiro e, depois, data marts – que contêm subconjuntos específicos de dados – são criados dentro desse repositório.
Ralph Kimball, especialista em tecnologia que publicou The Data Warehouse Toolkit em meados dos anos 1990, aplicou uma tática um pouco diferente ao conceito de data warehouse com sua abordagem “de baixo para cima”, na qual data marts individuais são desenvolvidos primeiro e, depois, integrados para criar um armazém.
O armazenamento de dados continua relevante hoje, e está evoluindo conforme a indústria se transforma para acomodar armazenamento em nuvem e análises em tempo real. Uma ferramenta de banco de dados emergente, similar a um data warehouse, é um data lake, que foi criada por tecnologias disruptivas de baixo custo como o Apache Hadoop. Data lakes são comumente usados em conjunto com fluxos de dados e armazenamento, ambos sem restrições, sem esquemas de construção ou processamento.
E-commerce retailer enhances customer engagement with cloud-based analytics and AI
With a rapidly growing business and an increasingly dispersed workforce, 1-800-FLOWERS.COM turned to SAS® Viya® hosted on Azure to obtain a more flexible, scalable infrastructure. To get data ready for analytics, the company first consolidates its databases and feeds them into Snowflake, a cloud-based data warehouse.
Data warehousing in today’s world
A data warehouse often means the difference between informed decisions and data chaos. Learn how and why data warehouses and related technologies are being used in our world today.
What is a data catalog?
Searching for big data across the business can waste valuable time. A data catalog uses metadata to help users quickly search an organization’s entire data landscape.
Who's using data warehouses?
With multiple programs, we quickly found ourselves in a situation with data living in silos. To understand how we were doing as an institute, we needed to find a better, more efficient way to integrate and manage multiple data sources across the enterprise. Bonnie Chapman-Beers Director of Evaluation and Innovation Institute for Veterans & Military Families
How a data warehouse works
A data warehouse starts with the data itself, which is collected and integrated from both internal and external sources. Business users access this standardized data in a warehouse so they can use it for analytics and reporting. Business intelligence tools help them explore the data to make better-informed business decisions.
Data is typically stored in a data warehouse through an extract, transform and load (ETL) process. The information is extracted from the source, transformed into high-quality data and then loaded into the warehouse. Businesses perform this process on a regular basis to keep data updated and prepared for the next step.
When an organization is ready to use its data for analytics or reporting, the focus shifts from data warehousing to business intelligence (BI) tools. BI technologies like visual analytics and data exploration help organizations glean important insights from their business data. On the back end, it’s important to understand how the data warehouse architecture organizes data and how the database execution model optimizes queries – so developers can write data applications with reasonably high performance.
In addition to a traditional data warehouse and ETL process, many organizations use a variety of other methods, tools and techniques for their workloads. For example:
- Data pipelines can be used to populate cloud data warehouses, which can be fully managed by the organization or by the cloud provider.
- Continuously streaming data can be stored in a cloud data warehouse.
- A centralized data catalog is helpful in uniting metadata, making it easier to find data and track its lineage.
- Data warehouse automation tools get new data into warehouses faster.
- Data virtualization solutions create a logical data warehouse so users can view the data from their choice of tools.
- Online analytical processing (OLAP) is a way of representing data that has been summarized into multidimensional views and hierarchies. When used with an integrated ETL process, it allows business users to get reports without IT assistance.
- An operational data store (ODS) holds a subset of near-real-time data that’s used for operational reporting or notifications.
Why are data warehouses important?
Enterprise data warehouses are vital because they integrate and store – in a central database and standard format – all the valuable data organizations use for enterprise decisioning. In turn, organizations can avoid the unpredictable results of taking an ad hoc approach to data access and integration. Data warehouses:
- Maintain historical data records – storing months or even years’ worth of information.
- Keep data secure by storing it in a single location where only those who need specific data are granted access to it.
- Provide easy access to high-quality data, which enables faster, more-informed business decisions.
- Make big data available for basic reporting as well as for advanced analytics, like machine learning and natural language processing.
Comparison: Data warehouse, data mart and data lake
Data warehouse
- Purpose: Stores a large amount of enterprise data encompassing several subject areas across the business.
- Advantages: Is very large; holds vast amounts of data.
- Disadvantages: Can be difficult to build.
- Outcome: Data is structured and ready to use for analytics or reporting.
Data mart
- Purpose: Stores a smaller amount of data, typically covering a single subject area that’s used by one department (like marketing or sales).
- Advantages: Is faster and easier to build than a data warehouse.
- Disadvantages: Has limited memory – so it can’t store as much information as a data warehouse.
- Outcome: Data is structured and ready to extract for analytics or reporting.
Data lake
- Purpose: Stores a large amount of raw data in its native format – ideal for unstructured big data like tweets, images, voice and streaming data.
- Advantages: Rapidly ingests data and gives business users fast, self-service access, exploration and visualization capabilities.
- Disadvantages: Does not provide data that is standardized, unduplicated, quality-checked or transformed.
- Outcome: Data stays in its raw format and can be repurposed – multiple metadata tags can be assigned for the same data.
SAS® Data Management
Data stored in a data warehouse doesn’t deliver value unless it’s managed well. With data management technology from SAS, you can transform big data into big opportunities with data integration, data governance, event stream processing and data quality technologies.