Database Reference
In-Depth Information
Many times, analytic sandboxes enable high-performance computing using
in-database processing—the analytics occur within the database itself. The idea
is that performance of the analysis will be better if the analytics are run in the
database itself, rather than bringing the data to an analytical tool that resides
somewhere else. In-database analytics, discussed further in Chapter 11, “Advanced
Analytics—Technology and Tools: In-Database Analytics,” creates relationships
to multiple data sources within an organization and saves time spent creating
these data feeds on an individual basis. In-database processing for deep analytics
enables faster turnaround time for developing and executing new analytic models,
while reducing, though not eliminating, the cost associated with data stored in
local, “shadow” file systems. In addition, rather than the typical structured data
in the EDW, analytic sandboxes can house a greater variety of data, such as raw
data, textual data, and other kinds of unstructured data, without interfering with
critical production databases.
Table 1.1
summarizes the characteristics of the data
repositories mentioned in this section.
Table 1.1
Types of Data Repositories, from an Analyst Perspective
Data
Repository
Characteristics
Spreadsheets
and data marts
(“spreadmarts”)
Spreadsheets and low-volume databases for recordkeeping
Analyst depends on data extracts.
Data
Warehouses
Centralized data containers in a purpose-built space
Supports BI and reporting, but restricts robust analyses
Analyst dependent on IT and DBAs for data access and schema
changes
Analysts must spend significant time to get aggregated and
disaggregated data extracts from multiple sources.
Analytic
Sandbox
(workspaces)
Data assets gathered from multiple sources and technologies
for analysis
Enables flexible, high-performance analysis in a
nonproduction environment; can leverage in-database
processing
Reduces costs and risks associated with data replication into
“shadow” file systems
“Analyst owned” rather than “DBA owned”
