Teradata OLAP Connector User Guide - Teradata

Transcription

Teradata OLAP Connector
User Guide
Release 13.01
B035-4105-060A
June 2010
The product or products described in this book are licensed products of Teradata Corporation or its affiliates.
Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce,
SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You’ve Never Seen Your Business Like
This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates.
Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc.
AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.
BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc.
EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation.
GoldenGate is a trademark of GoldenGate Software, Inc.
Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company.
Intel, Pentium, and XEON are registered trademarks of Intel Corporation.
IBM, CICS, DB2, MVS, RACF, Tivoli, and VM are registered trademarks of International Business Machines Corporation.
Linux is a registered trademark of Linus Torvalds.
LSI and Engenio are registered trademarks of LSI Corporation.
Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United
States and other countries.
Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries.
QLogic and SANbox trademarks or registered trademarks of QLogic Corporation.
SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc.
SPARC is a registered trademarks of SPARC International, Inc.
Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other
countries.
Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States
and other countries.
Unicode is a collective membership mark and a service mark of Unicode, Inc.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other product and company names mentioned herein may be the trademarks of their respective owners.
THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN “AS-IS” BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION
MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL,
OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
The information contained in this document may contain references or cross-references to features, functions, products, or services that are
not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features,
functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions,
products, or services available in your country.
Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated
without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any
time without notice.
To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this
document. Please e-mail: teradata-books@lists.teradata.com
Any comments or materials (collectively referred to as “Feedback”) sent to Teradata Corporation will be deemed non-confidential. Teradata
Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform,
create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata
Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including
developing, manufacturing, or marketing products or services incorporating Feedback.
Copyright © 2010 by Teradata Corporation. All Rights Reserved.
Preface
Purpose
The book provides the following information about the Teradata OLAP Connector
component of the Teradata Business Intelligence Optimizer (Teradata BIO) solution:
•
Solution overview and how Teradata OLAP Connector participates
•
How to setup Teradata OLAP Connector with Excel
•
Working with multi-dimensional data in Excel
•
Testing Relational Online Analytical Processing (ROLAP) cubes
Audience
This book is intended for use by:
•
Business Intelligence (BI) users
•
OLAP Cube administrators
Supported Releases
This book supports the following releases:
•
Teradata Database versions 12.00 and 13.00
•
Teradata OLAP Connector 13.01.00
To locate detailed supported-release information:
1
Go to http://www.info.teradata.com/
2
Under Online Publications, click General Search
3
Click Search
Teradata OLAP Connector can connect to Teradata Database versions 12.00.02.36 or later, and
13.00.00.10 or later.
Cube administrators must ensure the ROLAP cubes are defined using a matching or
appropriate version of Teradata Schema Workbench. The administrator should refer to the
Teradata Schema Workbench release notes.
Teradata OLAP Connector User Guide
3
Preface
Prerequisites
Prerequisites
The following prerequisite knowledge is required for this product:
•
Familiarity with multidimensional models, such as OLAP cubes
•
Familiarity with BI concepts
•
Familiarity with Excel PivotTables
Changes to This Book
The following changes were made to this book in support of the current release. Changes are
marked with change bars. For a complete list of changes to the product, see the Teradata
Business Intelligence Optimizer Release Definition associated with this release.
Date and Release
Description
June 2010
13.01
Initial release
Additional Information
Additional information that supports Teradata Business Intelligence Optimizer is available at
the web sites listed in the table that follows. In the table, mmyx represents the publication date
of a manual, where mm is the month, y is the last digit of the year, and x is an internal
publication code. Match the mmy of a related publication to the date on the cover of this book.
This ensures that the publication selected supports the same release.
Type of Information
Description
Access to Information
Release overview
Use the Release Definition for the following
information:
1 Go to http://www.info.teradata.com/.
• Overview of all of the products in the
release
• Information received too late to be
included in the manuals
• Operating systems and Teradata
Database versions that are certified to
work with each product
• Version numbers of each product and
the documentation for each product
• Information about available training
and the support center
3 Type 4104 in the Publication Product ID box.
Late information
4
2 Click General Search under Online Publications.
4 Click Search.
5 Select the appropriate Release Definition from
the search results.
Preface
Type of Information
Description
Access to Information
Additional product
information
Use the Teradata Information Products web
site to view or download specific manuals
that supply related or additional
information to this manual.
2 Click Data Warehousing under Online
Publications, Browse by Category.
3 Do one of the following:
• For a list of Teradata Tools and Utilities
documents, click Teradata Tools and Utilities,
and then select an item under Releases or
Products.
• Select a link to any of the data warehousing
publications categories listed.
Specific books related to Teradata OLAP Connector
are as follows:
• ODBC Driver for Teradata User Guide
B035-2509-mmyx
• Teradata Aggregate Designer User Guide
B035-4103-mmyx
• Teradata Schema Workbench User Guide
B035-4106-mmyx
CD-ROM images
Ordering
information for
manuals
Access a link to a downloadable CD-ROM
image of all customer documentation for
this release. Customers are authorized to
create CD-ROMs for their use from this
image.
Use the Teradata Information Products web
site to order printed versions of manuals.
2 Click Data Warehousing under the Online
Publications, Browse by Category.
3 Click CD-ROM List and Images.
2
Click How to Order under Print & CD
Publications.
3 Follow the ordering instructions.
General information
about Teradata
The Teradata home page provides links to
numerous sources of information about
Teradata. Links include:
1 Go to Teradata.com.
2 Select a link.
• Executive reports, case studies of
customer experiences with Teradata,
and thought leadership
• Technical information, solutions, and
expert advice
• Press releases, mentions, and media
resources
5
Preface
6
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Supported Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Changes to This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Chapter 1:
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Solution Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Teradata Business Intelligence Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Teradata OLAP Connector Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 2:
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
DSN Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Microsoft Excel 2007 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Connection Wizard (Part 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Connection Wizard (Part 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Spreadsheet Connection Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing the PivotTable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
21
22
23
23
Microsoft Excel 2003/Excel XP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Chapter 3:
Using Excel PivotTables for OLAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Empty PivotTable in Excel 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Drilling Down into a Hierarchical Dimension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
7
Table of Contents
Two Hierarchies on an Axis in Excel 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Removing Grand Totals in Excel 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Expanding and Collapsing in Excel 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Hiding Levels in Excel 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Formatting Cells in Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Handling Attribute Members in Excel 2007. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Filtering in Excel 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Slice/Select/Filter Cell Data (Without Using an Axis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Filtering members on an axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Excel 2003 and Excel XP PivotTable Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Appendix A:
Troubleshooting, FAQs, and Known Issues . . . . . . . . . . . . . . . . . . . . . .35
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
“Initialization of Data Source Failed” Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
IDispatch error message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Test Connection Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
#VALUE or Nothing in Excel Spreadsheet Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Calculated Members Not Showing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Format Strings and Currency Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
“Query Did Not Run” Excel Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
“TBI Repository Version Does Not Match” Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Unable to see Hierarchy Levels or Grand Totals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Named Sets Not Showing in Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Cube is disabled in Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Can I Filter on Axis Row or Column Members?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Can I Slice/Select/Filter Data Shown in a PivotTable without an Axis? . . . . . . . . . . . . . . .39
Can I Display and Filter on Member Attributes? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Can I use Label and Other Value Filters?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Why Do Totals Seem Inaccurate Using Axis Filters? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Spreadsheet Does Not Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Appendix B:
Teradata OLAP Connector Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Metadata Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
8
Table of Contents
Permanent Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Transient Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Metadata Pre-fetching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Cell Caching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Appendix C:
Teradata OLAP Connector Registry Settings . . . . . . . . . . . . . . . . . . . 45
Registry Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Specialized Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
9
Table of Contents
10
List of Figures
Figure 1: Teradata Business Intelligence Optimizer Architecture . . . . . . . . . . . . . . . . . . . . . . 16
Figure 2: TBI Repository Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 3: Teradata OLAP Connector Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 1: Annual Nationwide Sales Example: Populating a PivotTable. . . . . . . . . . . . . . . . . . 26
Figure 2: Annual Nationwide Sales Example: Drilling Down on a Dimension. . . . . . . . . . . . 27
Figure 3: Annual Nationwide Sales Example: Breakdown of Two Hierarchies on an Axis . . 28
Figure 4: Annual Nationwide Sales Example: Removing Grand Totals. . . . . . . . . . . . . . . . . . 29
Figure 5: Filtering Data in Excel 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 6: Choosing Between Two Members on the Same Axis. . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 7: Accessing Filter Members Using Top 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
11
List of Figures
12
List of Tables
Table 1: Teradata OLAP Connector Registry Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 2: Teradata OLAP Connector Specialized Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
13
List of Tables
14
CHAPTER 1
Introduction
The following topics provide an introduction to the Teradata OLAP Connector.
•
Solution Architecture
•
Teradata Business Intelligence Repository
•
Teradata OLAP Connector Overview
The Teradata BIO solution provides customers with an enterprise-class, general purpose
MDX/OLAP solution for Teradata Relational Online Analytical Processing (ROLAP)
architecture. Teradata Aggregate Join Indexes (AJIs), created using Teradata Aggregate
Designer, improve performance.
Teradata BIO is a set of software components that work together to specify the
multidimensional model for your ROLAP system, and handle MDX queries from various BI
clients.
The three major components in the Teradata BIO solution, shown in Figure 1 on page 16, are:
•
Teradata Schema Workbench
•
Teradata Aggregate Designer
•
Teradata OLAP Connector
15
Chapter 1: Introduction
Figure 1: Teradata Business Intelligence Optimizer Architecture
An OLAP cube administrator starts by using the Teradata Schema Workbench to indicate how
a star or snowflake schema and fact table in your relational database should be mapped to
OLAP cubes, dimensions, hierarchies, levels, and measures. The resulting cube schema is
published by Teradata Schema Workbench directly to the Teradata Enterprise Data Warehouse
(EDW) for later use by BI run-time client applications.
The cube schema can also be sent via a BI Schema file to the Teradata Aggregate Designer. This
allows the DBA to design Aggregate Join Indexes (AJIs) that support high performance
ROLAP queries and store them to the EDW.
The Teradata OLAP Connector manages Excel, and other BI client applications which emit
MDX language queries, through the OLE DB for OLAP (ODBO) interface. This allows
business analysts to perform real-time OLAP queries such as slice and dice, cross-tab reports,
and dashboards direct to your Teradata EDW.
16
Teradata BIO works within the confines of your existing Teradata installation. Teradata BIO
relies on star or snowflake schemas hosted in your database, accelerated by AJIs, and
administered by native Teradata users and security roles. A star schema normally has a
primary or fact table and one or more dimensional tables. A snowflake schema builds on the
concept of a star schema and scales that technique to handle an entire data warehouse.
The Teradata Business Intelligence Repository (TBI Repository), shown in Figure 2, is a key
component of the Teradata BIO solution. A TBI Repository stores the OLAP cube definition
schemas and must be installed on each Teradata server. Cube schemas define the
multidimensional model on top of your star or snowflake schema. AJIs, managed by Teradata
Aggregate Designer, accelerate the aggregation required by MDX. Teradata users and roles are
leveraged by Teradata BIO to control access to all data.
Figure 2: TBI Repository Architecture
17
Teradata OLAP Connector provides MDX query language services. It is an MDX provider,
similar to a database driver for OLAP cubes.
Teradata OLAP Connector supports the ODBO standard interface that Excel and many other
OLAP clients use to interact with an OLAP cube.
Figure 3 shows how the Teradata OLAP Connector sits between BI client applications, such as
Microsoft Excel, and Teradata Database. Its job is to interpret any MDX language (with
reference to the cube metadata in the TBI Repository) and send ROLAP-oriented, AJI-friendly
SQL to Teradata Database.
Figure 3: Teradata OLAP Connector Architecture
18
CHAPTER 2
Configuration
The following topics provide configuration information:
•
DSN Creation
•
Microsoft Excel 2007 Configuration
•
Microsoft Excel 2003/Excel XP Configuration
Note: Before starting the client-side configuration, refer to the system requirements and
installation steps in the Teradata Business Intelligence Optimizer Release Definition.
DSN Creation
Define a data source for each Teradata Database prior to connecting with ODBC. Use the
Microsoft® ODBC Data Source Administrator to create ODBC data sources and to configure
the drivers.
The following separate sets of instructions pertain to 32-bit and 64-bit versions of Windows
XP, Windows Server, and Windows Vista.
To open ODBC Data Source Administrator (32-bit)
✔ Perform one of the following:
•
Click Start>All Programs>ODBC>32-bit ODBC Administrator.
•
Click Start>Control Panel>Administrative Tools>Data Sources (ODBC).
To open ODBC Data Source Administrator (64-bit)
1
Open the C:\%WINDIR%\SysWOW64\ directory, where %WINDIR% is the location of
your Windows operating system files.
2
Run odbcad32.exe.
Note: If you create DSNs frequently, create a shortcut to this executable in an easily accessible
location to view/edit/add new 32-bit DSNs from within Windows 64-bit versions.
19
Chapter 2: Configuration
To set up an ODBC data source
1
Open the ODBC Data Source Administrator.
The ODBC Data Source Administrator dialog box appears.
2
Click the System DSN tab, and click Add.
The Create New Data Source dialog box appears.
3
Under the Name column, select Teradata
4
Click Finish.
The ODBC Driver Setup for Teradata Database dialog box appears.
5
Enter information in the Data Source Name field, and the Teradata Server name or
addresses. You may also enter username and password for authentication.
If the username and password are not entered here, or in the Excel connection or Excel
spreadsheet files, then you will be prompted for them when needed.
Note: If an error message appears when you attempt to connect to the database from Excel
(““Initialization of Data Source Failed” Message” on page 35), you can safely dismiss it and
enter your database credentials.
Entering your password in the Teradata DSN is stored in encrypted form and transmitted
in encrypted form. In contrast, credentials stored in a Microsoft .odc or .xls file are not
encrypted.
6
Click OK.
This section provides instructions for setting up an Excel 2007 connection to a Teradata BIOenabled Teradata Database. For Excel XP or Excel 2003 configuration, refer to “Microsoft
Excel 2003/Excel XP Configuration” on page 23.
Note: Make sure an OLAP cube is installed on the TBIO Repository before beginning.
The configuration process is in the following sequence:
•
Data Connection Wizard (Part 1)
•
•
Spreadsheet Connection Information
•
Viewing the PivotTable
When deciding whether to save your password in the un-encrypted .odc file you are creating,
consider the following:
•
20
If the password is unsaved, Excel versions prior to Excel 2007 Service Pack 2 (SP2) will
generate an error message (““Initialization of Data Source Failed” Message” on page 35)
each time you refresh your cube or reopen a spreadsheet containing a connection to your
OLAP data cube. You will then be prompted for your password.
•
If your DSN contains username and password information, then it is unnecessary to save
the password in the .odc file.
•
If your DSN already contains a username and password, and you want to override the
username in the .odc connection process, you must also override the password. To do this,
perform the steps below.
To override the DSN password
1
Launch the Data Connection Wizard. For instructions, refer to “Data Connection Wizard
(Part 1).”
2
Select the Connection tab.
3
Check the Allow saving password checkbox.
4
Check Save password in file checkbox.
Note: To change the credentials, you must change both the username and password fields.
If you do not change both when overriding credentials in a DSN, you will get the
“Initialization of data source failed message” twice, and no PivotTable will be created.
To create a connection in Excel 2007
1
Specify a cell as the left corner of your PivotTable.
2
Select the Data tab.
3
Click From Other Sources, and select From Data Connection Wizard from the list.
The Data Connection Wizard appears.
4
Select Other/Advanced, and click Next.
The Data Link Properties dialog box appears.
5
From the Provider tab, select Teradata OLAP Connector, and click Next.
6
On the Connection tab, enter the Teradata DSN designated as the data source.
7
To store a password in an .odc file:
a
Select Use a specific user name and password.
b
Uncheck the Blank password checkbox.
c
Check the Allow saving password checkbox.
d
Enter your Teradata user name and password.
Note: Checking Allow saving password does not save your password, it enables saving the
password to the connection file in the future.
8
Click Test Connection.
If the connection fails, refer to “Test Connection Fails” on page 36.
21
9
Choose the schema you want to connect to from the Enter the initial catalog to use
dropdown selector, and click OK.
To complete the Data Connection Wizard
1
Choose one of the following:
•
To have a separate .odc file for each cube in the TBI Repository, check the Connect to a
specific cube checkbox. This reduces prompting for the associated cube each time a
PivotTable is created or refreshed.
•
To create one .odc file that points to the database, uncheck the Connect to a specific
cube checkbox. This enables creating PivotTables from different cubes in the same
database using a single connection file.
Note: Not specifying Connect to a specific cube, in combination with checking Always
attempt to use this file to refresh data, causes prompting twice for the cube when
refreshing. This is a known, harmless behavior.
2
Select the database and OLAP cube for opening this Excel PivotTable, then click Next.
The Save Data Connection File dialog box appears.
Note: You can modify the file name of the .odc file that this connection information will
be recorded in. Connection files are stored in My Documents\My Data Sources.
3
Type a descriptive name in the Friendly Name field.
Note: Do not accept the default in the Friendly Name field. You may end up with several
.odc files in your list of data sources, and this text displays when you choose Existing
Connections within Excel. Consider including BI Repository and cube information in the
friendly name.
4
Enter secondary information in the Description field.
Note: This text displays when you choose Existing Connections within Excel.
5
Check Save password in file to save the Teradata password in the connection file.
Saving the password allows you to use the connection without entering your Teradata
password every time you reopen the spreadsheet or refresh the connection.
Note: If you didn’t check the Allow saving password checkbox in the Data Link Properties
dialog, the password is not passed through from the Data Link Properties dialog window to
the Data Connection Wizard to be saved.
6
Check Always attempt to use this file to refresh data.
This determines if the connection information is in the .odc file or the .xlsx file.
Note: To mail the .xlsx file without the .odc file, leave this checkbox unchecked. You can
save the password in the .xlsx file to not require recipients to enter a password.
7
Click Finish to save the connection .odc file.
The Import Data dialog box appears. See “Spreadsheet Connection Information.”
22
When Excel 2007 restarts this connection appears under the Existing Connections tool
button. To start a new PivotTable from an existing connection, click Existing Connections
in the Data tab to bring up a list of saved connections.
Spreadsheet Connection Information
To save a password in the spreadsheet (optional)
Perform the following steps to save the password in the actual .xlsx file (optional), so the .odc
file is no longer necessary for password information.
1
On the Import Data dialog box, click Properties...
The Connection Properties dialog box appears.
2
Select the Definition tab.
3
Check Save Password to request that the password also be saved in the .xlsx file.
4
Click OK.
5
On the Import Data dialog box, click OK.
•
If prompted to select a cube from among the cubes in the database, choose one.
•
If the password is unsaved, Excel versions prior to Excel 2007 Service Pack 2 (SP2) will
generate an error message (““Initialization of Data Source Failed” Message” on
page 35) each time you refresh your cube or reopen a spreadsheet containing a
connection to your OLAP data cube. You will then be prompted for your password.
•
For more information about data connection, see the Excel 2007 online help.
Viewing the PivotTable
•
To check that your connection and PivotTable are working, check one of the measures, for
example the Store Sales checkbox, and wait to see the sum of sales for the whole cube
populate into cell A1.
•
To get a table of cells, scroll down in the field list to find a dimension to drag to the
Column Labels or Row Labels panes. Wait for the results.
•
More information on working with PivotTables from OLAP cubes in Excel will be covered
in Chapter 3: “Using Excel PivotTables for OLAP.”
Note: When reopening an Excel file and performing operations that communicate with the
OLAP database, you may encounter a security warning dialog window stating “Microsoft
Office has identified a potential security concern. The operation connects to an external data
source...” This is normal, but be sure that you trust your data source.
Before configuring Excel 2003 or Excel XP, configure a Data Source Name (DSN) on your
computer. For instructions, refer to “DSN Creation” on page 19.
23
To add a new database query
1
From the Data menu, click Import External Data>New Database Query.
Note: If a data source connection currently exists, you can skip these steps and click Import
External Data>Import Data from the Data menu to access the connection.
Note: If you have not installed Microsoft Query, then you might be prompted to install
this feature. Click Yes to proceed with the installation.
2
In the Choose Data Source dialog box, select the OLAP Cubes tab.
3
Highlight <New Data Source> and click OK.
4
In the Create New Data Source window, specify a name for the data source/connection.
Next, for the Select an OLAP provider for the database field, choose Teradata OLAP
Connector from the dropdown list.
5
Click Connect.
6
In the Select Data Source window that appears, select the Machine Data Source tab and
select a previously created Teradata DSN.
7
Click OK.
If your username and password are not stored in your DSN, then you will be prompted for
credentials.
Note: If your DSN already contains a username and password, you cannot override it
here. If you try, you will get two duplicate error messages (““Initialization of Data Source
Failed” Message” on page 35), and no PivotTable.
8
When the Select the catalog to use prompt appears, select your schema and click OK.
9
From Create New Data Source, select a cube from the drop down menu.
Note: Checking Save my user ID and password generates an error message upon refresh
for Excel versions prior to 2007 Service Pack 2. For instructions on how to prevent the user
from always having to enter the password on re-opening/using an OLAP-sourced
PivotTable, then refer to ““Initialization of Data Source Failed” Message” on page 35.
The Choose Data Source dialog box appears with the newly created data source.
10 Select the data source and click OK.
The PivotTable and PivotChart Wizard dialog box appears.
11 Perform one of the following:
•
Click Layout and use the resulting PivotTable layout wizard to drag and drop
dimensions and members on a special layout pane. This is useful for two dimensions
on one axis. The layout wizard enables reversing the precedence of two dimensions on
the same axis, but members and measures do not display.
•
Click Finish. A blank spreadsheet appears. As you add measures to the data area and
dimensions to axes, you will see numeric values and dimension members to confirm
your actions.
For more information on adjusting, filtering, or drilling into Excel 2003 PivotTables, see
“Excel 2003 and Excel XP PivotTable Tasks” on page 33.
24
CHAPTER 3
Using Excel PivotTables for OLAP
The following topics provide Excel PivotTable usage examples:
•
Empty PivotTable in Excel 2007
•
Drilling Down into a Hierarchical Dimension
•
Two Hierarchies on an Axis in Excel 2007
•
Removing Grand Totals in Excel 2007
•
Expanding and Collapsing in Excel 2007
•
Hiding Levels in Excel 2007
•
Formatting Cells in Excel
•
Handling Attribute Members in Excel 2007
•
Filtering in Excel 2007
•
Excel 2003 and Excel XP PivotTable Tasks
Excel PivotTables allow you to examine/visualize your data in different ways by rearranging
what is shown against various axes. They are often used to aggregate data and see the subtotals
broken down against the two axes.
This chapter uses an Annual Nationwide Sales example to demonstrate how to use Excel as a
BI tool.
•
In non-OLAP database tables, you might have columns like year, country, sale, or millions
of rows for each sale ever made. PivotTables allow you to view this same data as a shorter
table with a country location axis across the top and a year axis down the left. The data for
each year and location is summarized and put in the correct cell.
•
For OLAP business intelligence purposes, you can drill down and see the regions within a
country and/or the stores within a region. Filtering, or drilling down into detail, is
frequently called slicing and dicing. For example, you could filter out internet sales to
restrict viewing to in-person store sales.
These are some of the powerful things you can do with Excel PivotTables to enhance your
enterprise business intelligence and make informed strategic decisions. To learn more about
Excel PivotTables, read Beginning PivotTables in Excel 2007 by Debra Dalgleish.
25
Chapter 3: Using Excel PivotTables for OLAP
To test a PivotTable, within the Choose fields to add to report: pane of the PivotTable Field List,
find an OLAP measure. In the Annual Nationwide Sales example, Store Sales is the selected
measure.
•
To view all available measures, click the + to the left of Values.
•
Check the checkbox to the left of the Store Sales measure. The Store Sales measure appears
the Values pane (alternately, left-click and drag Store Sales to the Values pane).
•
The sum of Store Sales for the whole cube will populate into cell A1.
Figure 1 shows how to scroll down a field list to include selected dimensions. In this example,
the Time - Year and Product - Product Family have been left-clicked and dragged to the Row
Labels pane and Column Labels pane. Excel calls the Teradata OLAP Connector to retrieve
results from the Teradata Database broken down by the axes.
Figure 1: Annual Nationwide Sales Example: Populating a PivotTable
26
A common BI operation is to break information down into smaller pieces on a dimension by
clicking the + icon to the left of a row label. In the example below, the year 1998 has been
expanded into quarters.
Figure 2: Annual Nationwide Sales Example: Drilling Down on a Dimension
27
To get a breakdown by two hierarchies on a single axis, drag a field from the PivotTable Field
List to the PivotTable.
In the Annual Nationwide Sales example, the Customer - Gender field has been dragged to the
Column Labels pane of the PivotTable Field List. Each Product Family now includes columns
for F and M genders.
Figure 3: Annual Nationwide Sales Example: Breakdown of Two Hierarchies on an Axis
28
To remove a grand total
1
Right-click any cell, and select PivotTable Options.
2
Click the Totals and Filters tab.
3
Uncheck the two checkboxes in the Grand Totals group.
4
Click OK.
Following these steps does not remove the grey subtotals for each product family in the
Annual Nationwide Sales example. In the example below, the user right-clicks top level
column label Food Total, and then clicks the Subtotal ‘Product Family’ menu item to remove
them.
Figure 4: Annual Nationwide Sales Example: Removing Grand Totals
29
To expand and collapse a dimension member
✔ Right-click a dimension member, and then use the Expand/Collapse menu item.
Hiding Levels in Excel 2007
To expand and collapse a dimension member
✔ Right-click a dimension member, and then use the Show/Hide Fields menu item.
Formatting Cells in Excel
If some cells have only one decimal place or lack currency formatting, you can manually apply
formatting with Excel. For instructions on how to ensure all personnel in your organization
automatically receive updated formatting, see the Teradata Schema Workbench Guide.
Handling Attribute Members in Excel 2007
To display member attributes
✔ Hover over a dimension member in a PivotTable.
In Excel, these member attributes are called properties.
To display columns of properties on a dimension member
✔ Right-click a dimension member, then select Show Properties in Report.
The property columns appear in the spreadsheet.
To sort dimension members
✔ Right-click a dimension level, then select Sort.
For more information about displaying and filtering member attributes, refer to “Can I
Display and Filter on Member Attributes?” on page 39.
30
Slice/Select/Filter Cell Data (Without Using an Axis)
Drag a dimension from the PivotTable Field List pane to the Report Filter sub-pane of the
PivotTable Field List. If the dragged dimension is in cell A1, this moves the entire PivotTable
down and places a filter cell above the PivotTable.
Figure 5: Filtering Data in Excel 2007
Click the funnel icon on a filter cell to select any member of that dimension.
To select multiple items, check the Select Multiple Items checkbox.
Note: Having three or more dimensions in the Report Filter pane might slow performance.
Filtering members on an axis
There are three ways to filter members on an axis:
•
On any dimension member, use right-click and select Filter>Keep/Hide.
•
Near the top left corner of your PivotTable are the cells annotated Row Labels and Column
Labels. Left-click a row or column triangle filter icon to show filter choices and an axis
filter selector. The axis filter tree allows you to select any subset of dimension members
from that axis. If you have two dimensions on that axis, you can choose which tree to select
from, using the top element of the dialog box.
31
Figure 6: Choosing Between Two Members on the Same Axis
•
Left-click a row or column triangle filter icon to access Value Filters. You can choose Top
10 to get access to top or bottom N filtering of any ‘measure’ that you have displayed in the
large portion of your PivotTable.
Figure 7: Accessing Filter Members Using Top 10
32
This section is an introduction to manipulating PivotTables in Excel 2003 and Excel XP.
To restore the PivotTable Field List
✔ Right-click anywhere in the PivotTable and select Show Field List.
To add another dimension to an axis
✔ Click and drag a dimension from the PivotTable Field List to the axis member area.
Note: The order of dimensions on an axis determines which dimension has higher
precedence. You can change the order of dimensions by dragging them to a different
position. This can also be done using the Layout Wizard.
To remove a dimension from an axis
✔ Left-click and drag the dimension name to an empty portion of the spreadsheet.
To open the Layout Wizard
1
Right-click any cell in the PivotTable.
2
Choose PivotTable Wizard, then click Layout.
To drill down on a row or axis member, and display group details
1
Right-click the member.
2
Choose Group And Show Detail>Show Detail.
To remove a drill down and show only the next higher summary level
1
Right-click the higher member or dimension.
2
Choose Group and Show Detail>Hide Detail.
To remove Grand Totals
1
Right-click anywhere in the PivotTable and choose Table Options.
2
Under Format Options, uncheck the Grand totals for columns and Grand totals for rows
check boxes.
3
Click OK.
33
To implement a report filter (page slice)
✔ Click Add To (Page Area), or mouse-drag a dimension to cell A1 (the Drop Page Fields
Here area).
To narrow a filter (member slice)
1
Click the inverted triangle icon in the filtered cell.
2
Select any member and click OK to slice to a single member.
To select multiple items, click the filter icon and check the Select multiple items checkbox.
To add a chart
1
Select the data region (row or column) and right-click it.
2
Select PivotChart.
To filter a dimension attached to an axis
1
Click filter icon for the dimension name. Then follow steps similar to the report filter
above.
2
Click Add To (Page Area), or mouse-drag a dimension to cell A1 (the Drop Page Fields
Here area).
Note: For additional information about filtering, refer to “Can I Filter on Axis Row or
Column Members?” on page 38.
34
APPENDIX A
Troubleshooting, FAQs, and Known
Issues
The following topics provide troubleshooting solutions, answers to frequently asked
questions, and a list of known issues:
•
Troubleshooting
•
Frequently Asked Questions
•
Known Issues
Troubleshooting
“Initialization of Data Source Failed” Message
Prior to Excel 2007 SP2, an “Initialization of Data Source Failed” Excel Error can occur when
you try to connect to the database. The message also displays when initially opening a
connection, refreshing a connection, or reopening and drilling down on a spreadsheet. You
must include a password in the DSN, the connection .odc file, or in the .xlsx file.
Note: If you have intentionally not included a password in any of these three places due to
corporate security policies, dismiss the error dialog box. When the Teradata
DatabaseConnect... dialog box appears, enter your Teradata password.
This error message can occur for two reasons:
•
Excel versions prior to Excel 2007 Service Pack 2 attempt to connect using Microsoft
Integrated Security and fails.
•
If this error message displays twice, it is related to having a username in your DSN, and
attempting to override it in the connection without overriding the password.
To resolve this issue (message displays once)
✔ For Excel 2007, perform one of the following:
•
Upgrade your Excel 2007 to Service Pack 2.
•
Create a new connection and make sure the password is saved by following the
instructions in “Microsoft Excel 2007 Configuration” on page 20.
✔ For Excel 2003, add the Teradata username and password in your Teradata DSN
configuration. See “DSN Creation” on page 19 for instructions.
35
Appendix A: Troubleshooting, FAQs, and Known Issues
Troubleshooting
To resolve this issue (message displays twice)
✔ For Excel 2007, create a new connection and make sure the password is saved by carefully
following the connection process in “Microsoft Excel 2007 Configuration” on page 20.
During the connection-creation process, perform the following:
a
Change the user name and password.
b
Check Allow saving password.
c
Check Save password in file.
✔ For Excel 2003 and Excel XP, add the Teradata username and password in your Teradata
DSN configuration. See “DSN Creation” on page 19 for instructions.
Note: It is not possible to override the DSN username and password using the Excel 2003
connection process.
IDispatch error message
This error occurs in Excel when trying to create an Excel connection without setting up a valid
DSN. See “DSN Creation” on page 19 for instructions.
To prevent this error in the future, click Test Connection on the Connection tab of the Data
Link Properties dialog box when creating a DSN. To troubleshoot a failed connection, see
“Test Connection Fails.”
Test Connection Fails
If the data connection fails from Microsoft Excel, check the following:
•
The DSN entered on the Connection tab of the Data Connection Wizard is accurate. For
instructions, see “Microsoft Excel 2007 Configuration” on page 20 or “Microsoft Excel
2003/Excel XP Configuration” on page 23.
•
Make sure that the DSN has the correct database system name or IP address. See “DSN
Creation” on page 19 for instructions.
•
Make sure that credentials specified in the DSN are correct.
#VALUE or Nothing in Excel Spreadsheet Cell
An empty OLAP measure cell in Excel is (called NULL or #VALUE), can occur in a Teradata
BIO MDX-calculated cell, or a cell that sums multiple MDX calculated values. For example,
this could happen with a divide-by-zero error in an MDX calculated measure or member.
See your cube administrator for help.
Calculated Members Not Showing
By default in Excel 2007, calculated members defined in your cube schema do not appear.
Note: Calculated members are not a feature of Excel 2003 or earlier versions.
36
Troubleshooting
To display calculated members
1
Right-click any cell in your PivotTable, and select PivotTable Options.
2
Click the Display tab.
3
Select the Show calculated members from OLAP server check box.
4
Click OK.
Format Strings and Currency Conversion
Using a Format String of $#,##0.00 or $#,##0 within the Teradata Schema Workbench cube
definition tool localizes the currency character based on the locale of the Teradata OLAP
Connector machine running the BI client. This is likely wrong if the value is really in dollars.
To avoid this, the Schema Workbench administrator should use \$#,##0.00 or \$#,##0, which
escapes the $ and forces the dollar sign to remain on a client machine with a different
operating system locale.
Note: Changing a format string from $#,##0 to €#.##0 does not cause mathematical
conversion.
“Query Did Not Run” Excel Message
An error message appears, stating “The query did not run, or the database table could not be
opened.”
The two main reasons this error might occur:
•
The Schema Workbench cube administration tool performs syntax checking of MDX
queries used in calculated measures, named sets, and calculated members. This message
appears if Excel detects a semantic error.
•
The database role permissions set by your cube administrator do not allow the Excel user
to access hierarchy members used in MDX calculations.
“TBI Repository Version Does Not Match” Error
An error message appears, stating “The TBI Repository version does not match the version
expected by this version of Teradata OLAP Connector. Please upgrade to a newer version of
Teradata OLAP Connector to use this Repository. Expected version: ”
This message can occur for the following reasons:
•
Your cube administrator has installed a new repository with a slightly different structure.
•
You have installed Teradata OLAP Connector version updates. These updates should be
installed by your cube administrator.
The repository version very rarely changes. This message indicates a mismatch between the
structural version that Teradata OLAP Connector expects and the repository itself.
37
Unable to see Hierarchy Levels or Grand Totals
The Teradata BIO solution has a sophisticated cube and dimensional security system. It
depends on your normal Teradata security roles.
Certain roles may be restricted from drilling too far down a hierarchy. Other roles may be
restricted from seeing top level aggregates, even the All level.
Note: In Microsoft Excel, not being able to access the All level means you may not be able to
see Grand Total rows or columns.
See your cube administrator for issues with accessing levels.
Named Sets Not Showing in Excel
If your company has cubes that define Named Sets in cubes for Excel 2007 users, then users
running Excel 2003 or Excel XP (2002) will not be able to see them. Versions previous to Excel
2007 do not support Named Sets.
Cube is disabled in Excel
If an OLAP cube displays grayed out in Excel, then no cube exists in the Teradata BIO
repository. See your cube administrator for help.
Can I Filter on Axis Row or Column Members?
Yes.
To filter in Excel 2007
1
2
Left-click a filter icon to display axis filter and value filter choices:
•
The axis filter tree enables selecting any subset of dimension members from that axis. If
you have two dimensions on that axis, you can use the Select Field element to choose
which tree to select from.
•
Value filters provide Top 10 style filtering. These enable access to top or bottom N
filtering of any ‘measure’ that you have displayed in your PivotTable.
On any dimension member, right-click and select Filter>Keep/Hide.
To filter in Excel 2003 and Excel XP
38
1
Left-click a filter icon to display axis filter choices. The axis filter tree allows you to select
any subset of the selected dimension members from that axis.
2
To apply value filters, right-click an axis member, and select Field Settings. Ensure that the
name in the Name field matches the axis member name that you would like to filter.
3
Click Advanced to display the PivotTable Field Advanced Options dialog box. You can turn
on Top 10 AutoShow settings, and then apply top or bottom N filtering of any measure
specified on your PivotTable.
4
On any dimension member, right-click and select Hide. Additional options might include
Hide Levels or Hide Dimension depending on which member you selected.
Can I Slice/Select/Filter Data Shown in a PivotTable without an Axis?
Yes.
In Excel 2007, drag a dimension from the PivotTable Field List pane to the Report Filter subpane. This moves the entire PivotTable down (if it is in cell A1) and puts a filter icon above the
PivotTable.
In Excel 2003, drag a dimension from the PivotTable Field List pane to the page area annotated
Drop Page Fields Here row.
Click the filter icon to select/slice any member of that dimension. You can also select N of M of
the members to view a selected subset.
Note: Having more than two dimensions in the Report Filter/Page Area will slow
performance.
Can I Display and Filter on Member Attributes?
Yes.
Hover the mouse over a dimension member in Excel for a tooltip display of the member
attributes.
Note: If these tooltips are disabled, you can enable the options on the Display tab of the
PivotTable Options dialog box.
On an axis member you can right-click and select Show Properties In Report>Show All
Properties. This adds columns into the table for specified member attributes for filtering.
Can I use Label and Other Value Filters?
No.
On an axis filter popup menu, Label Filters is grayed out. This is because label filters are not
currently supported.
To restrict filtering to member attributes, see the instructions in “Can I Display and Filter on
Member Attributes?.”
Note: Value Filters other than the Top 10 style are not currently supported.
Why Do Totals Seem Inaccurate Using Axis Filters?
When a dimension with multiple members on a PivotTable axis has a number of members
filtered out, the resulting total does not change. This result is called a non-visual total, and is
expected Teradata BIO behavior.
39
Known Issues
Known Issues
Spreadsheet Does Not Refresh
Using the Excel 2007 Refresh feature might not retrieve new data, because the query from
Excel can be satisfied by the Teradata OLAP Connector cache.
The solution is to close the spreadsheet and reopen it.
40
APPENDIX B
Teradata OLAP Connector Caching
Teradata OLAP Connector has a sophisticated caching architecture to provide high
performance ad hoc queries.
Dimension metadata, except members, are read in and kept permanently in RAM for the
duration of the ODBO session. Dimension member metadata is kept in a transient member
cache. OLAP measure cell values are cached using a Least Recently Used (LRU) mechanism.
This appendix contains descriptions of the caching mechanisms and the changeable settings.
Caution:
Do not change cache settings without consulting with the Teradata Global Support Center.
For the location of these settings, see the Teradata Schema Workbench User Guide.
Metadata Caching
The structure of an OLAP cube is represented by metadata entities such as dimensions,
hierarchies, levels, and members. These entities are requested by ODBO clients throughout
the course of an ODBO session. By caching entities on the client PC, Teradata OLAP
Connector avoids retrieving metadata repeatedly from Teradata Database.
In terms of caching, there are two classes of metadata entity:
•
Permanent Entities
•
Transient Entities
Permanent Entities
Permanent metadata entities are as follows:
•
Dimensions
•
Hierarchies
•
Levels
•
Level properties
•
Named sets
•
Members of the Measure dimension
•
Hierarchy default members
When an ODBO client requests a cube, all of the cube’s permanent entities are pre-loaded
from the TBI Repository. These entities are cached for the duration of the ODBO session.
41
Appendix B: Teradata OLAP Connector Caching
Cell Caching
There is no limit placed on the maximum number of entities in this category. The assumption
is that the number of permanent entities is always going to be low.
Transient Entities
Transient entities are retrieved from Teradata Database and cached on demand. Members are
the only class of transient entity. Members are subject to expiration based on their usage
frequency and the size of the metadata cache. The maximum metadata cache size can be
configured using the MaxMetadataCacheSize registry key. This value sets the maximum
number of members that can exist in the cache at any time and defaults to 1,000,000 if not set.
If adding newly-retrieved members to the metadata cache will cause the maximum size to be
exceeded, stale entities are ejected. Stale entities are identified based on the frequency of their
use, using a Least Frequently Used (LFU) algorithm. Members cached as part of a parent set
are ejected together.
If a set of members has been requested and is too large to fit within the cache, the set is
retrieved, but is not cached. When the current command has completed execution, the set is
discarded. If the maximum metadata cache size is set to 0, all members are applied to this
policy, effectively disabling the metadata cache.
Members are retrieved from the cache individually or as part of a parent set. For example, if a
group of members are requested as part of the set [Product].[Products].Members, the cached
members can fulfill future requests for individual members of the set.
Note: While Teradata OLAP Connector routinely ejects metadata from the cache during
execution, all cached metadata is destroyed when the ODBO client session terminates.
Metadata Pre-fetching
Teradata OLAP Connector attempts to minimize the number of Teradata Database retrievals
used to satisfy member metadata requests by pre-fetching members. When a request is made
for a single member or for the children of a member, all members on that level are retrieved
and cached. The maximum size of a level that is subject to pre-fetching can be configured
using the PrefetchLevelSize registry key. This value defaults to 20,000 members. To disable
member pre-fetching, set the value to 0.
Teradata OLAP Connector also attempts to pre-fetch measures with a SUM aggregator. The
MaxMeasuresForPrefetch registry key specifies the maximum number of measures to
pre-fetch. This value defaults to 20. When the number of measures in the cube exceeds this
value, Teradata OLAP Connector retrieves the first N measure, where N is the value specified
in the registry. Setting the registry value to 0 disables measure pre-fetching.
Cell Caching
Whenever a SQL query is executed against Teradata Database to fulfill a request for cell data
(measures as opposed to metadata), the resulting cell data is cached. The cell cache uses a
simple LRU algorithm.
42
Cell Caching
The cell cache maximum size is specified by the MaxCellCacheSize registry key. The type is
DWORD and the default value is 100 (decimal) in units of megabytes. A setting of 100 results
in a 100MB cell cache. To disable the cell cache, set the size to 0.
While Teradata OLAP Connector ejects cached cell data during execution, all cached cell data
is destroyed when the ODBO client session terminates.
43
Cell Caching
44
APPENDIX C
Teradata OLAP Connector Registry
Settings
BI client applications connect to your EDW and the Teradata Repository using Teradata OLAP
Connector. Teradata OLAP Connector has useful administrative settings that are not
documented in the Teradata OLAP Connector User Guide, whose audience is the BI client
application user. BI client application users typically do not have permission to change the
Windows registry.
Caution:
Do not change the registry settings without consulting a Teradata BIO expert or the Teradata
Global Support Center.
The registry location root for these settings depends on the BI client user’s operating system
word width, 32-bit Windows or 64-bit Windows:
•
Win32: [HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\Teradata Business
Intelligence Optimizer\13.01\Teradata OLAP Connector\RuntimeSettings]
•
Win64: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Teradata\Teradata
Business Intelligence Optimizer\13.01\Teradata OLAP Connector\RuntimeSettings]
Registry Settings
The first four settings in Table 1 are cache and pre-fetch-oriented. To understand these
settings before changing them, you must read Appendix B: “Teradata OLAP Connector
Caching.”
Table 1: Teradata OLAP Connector Registry Settings
Key
Type
Default
Value
MaxCellCacheSize
DWORD
100
Approximately specifies the maximum size
of the measure cell cache in MB. To disable
cell cache, set value to 0.
MaxMetadataCacheSize
DWORD
1000000
Specifies the maximum size of the
dimension member metadata cache. The
quantity specified is the maximum number
of members to keep in cache between MDX
queries. To disable cache, set value to 0.
45
Appendix C: Teradata OLAP Connector Registry Settings
Specialized Settings
Table 1: Teradata OLAP Connector Registry Settings (continued)
Key
Type
Default
Value
PrefetchLevelSize
DWORD
20000
Teradata OLAP Connector always
attempts to pre-fetch all dimension
members in a level. If the level size exceeds
this value, the level does not pre-fetch. To
disable pre-fetching, set value to 0.
MaxMeasuresForPrefetch
DWORD
20
The maximum number of measures to
pre-fetch. To disable pre-fetching, set value
to 0.
MaxCachedCalculatedSet
Size
DWORD
10000
Specifies the maximum number of
members in a calculated set. If the set
exceeds this size, the set is not cached.
SqlQueryTimeout
DWORD
ODBC
driver
default
Specifies the amount of time, in seconds, a
SQL query should wait before returning to
the application.
These settings are only published in this appendix for reference purposes.
Caution:
Do not change these settings without consulting a Teradata BIO expert or the Teradata Global
Support Center.
Table 2: Teradata OLAP Connector Specialized Settings
Key
Type
Default
Value
PushdownCalculations
DWORD
2
Valid values:
0:Only use internal MDX engine.
1: Always push down to Teradata Database
when supported by expression.
2: Only push down to Teradata Database
when supported by expression AND the
solve order is 0 AND all calculated members
have a solve order of 0.
UseGroupingSets
DWORD
2
Specifies the setting for SQL grouping set
usage. Valid values:
0: Disable grouping sets.
1: Always use grouping sets.
2: Grouping set support auto detection
from Teradata Database.
46
Table 2: Teradata OLAP Connector Specialized Settings (continued)
Key
Type
Default
Value
UseNullIfZero
DWORD
1
Specifies the setting for controlling the use
of NullIfZero in database-evaluated
calculated measures involving division.
When set to 1, the SQL expression wraps the
denominator with NullIfZero. When set to
0, the SQL expression might fail if there is a
division by 0 on Teradata Database.
UseQueryBands
DWORD
2
Specifies the setting for query band usage.
Valid values:
0: disable query bands.
1: always use query bands.
2: query band support auto detection from
database.
47
48
Glossary
A
aggregate
cube.
Summary data that provides definitions for aggregate tables that help optimize a
aggregation The process of merging multiple data values into one value. For example, sales
data collected daily can then be aggregated to the week level, the week data could be
aggregated to the month level, and so on. The data can then be referred to as aggregate data.
Aggregation and summarization are synonyms, as are aggregate data and summary data.
AJI Aggregate Join Index. Combines one or more commonly-used columns of the base
tables with the results from one or more aggregation expressions pre-computed from one or
more columns of the tables. This is used to improve query performance of summarized data.
attribute A characteristic of a dimension member in a logical data model, representing a set
of dimension members. It is associated with a database column. For example, the Time
dimension might have a Year attribute which represents the set of years in a database column.
B
base table A base table can be any table that acts as an origin of detailed data. In OLAP, the
fact table is often considered to be the base table in a star schema.
C
calculated member
other members.
A member of a dimension whose value is calculated from the values of
children Members of a dimension that are subordinate to a parent member. Typically,
children would be used in a calculation that created a consolidated total for the parent.
Children can also have children, or levels that are subordinate to themselves. Children can
have more than one parent.
client An OLAP client usually handles most of the presentation work, and only some of the
processing. The OLAP server handles the rest of the processing.
cube A named collection of measures and dimensions. Measures and dimensions are
derived from a fact table, which identifies the columns from which the measures are calculated
and contain references to the tables which hold the dimensions.
49
Glossary
D
data model An abstract model that describes how data is represented or structured, and
how data elements relate to each other. A multidimensional data model in OLAP consists of
cubes, measures, dimensions, hierarchies, levels, and attributes.
data source
The source of computer data or a site where data is stored and accessed.
dimension A logical grouping of attributes. A dimension acts as an efficient and intuitive
way of organizing data for retrieval and analysis.
dimension table A database table that contains attribute-associated data and is created as a
companion table to a fact table.
drill down/up To view data in different levels of detail. Specifically, a user can drill up to get
more generalized data or down for more detailed data. The level to which a user can drill
depends on the granularity of the data.
E
elements The actual data values that appear in a dimension table associated with an
attribute. January and September would be elements of the Month attribute in the Time
dimension. Also referred to as an attribute element.
F
facts Variables or measures, normally stored as numeric fields, which are the focus of the
decision support investigation. Facts would be inventory levels, sales amounts, commissions,
and so on.
fact table A fact table acts as the base table for a star schema and, when normalized, is
surrounded by dimension tables containing attribute data. The fact table contains measure or
fact data. See also base table.
H
hierarchical relationships Parent/child relationships are examples of hierarchical
relationships, where a parent member represents the consolidation of its children members.
See hierarchy.
hierarchy An organization of dimension attributes into a logical tree structure which
defines parent-child relationships between the attributes, including how data can be
aggregated from children to parent.
K
key
50
A key identifies a column or a group of columns in a table.
Glossary
L
levels Attributes organized in a hierarchical structure.
M
MDX Multidimensional Expression language. A query language for querying and
manipulating the multidimensional data stored in OLAP cubes. MDX is also a calculation
language, with syntax similar to spreadsheet formulas.
measure Normally corresponds to a fact table column and typically represents numerical
data. Measures exist in a separate OLAP dimension.
member An attribute element value in an OLAP cube.
metric
See measure.
modeling A process to define and analyze the data requirements that are needed to support
business functions. Data modeling defines the relationships between data elements and
structures.
Multidimensional OLAP (MOLAP) MOLAP is the more traditional way to do OLAP
analysis. In MOLAP, data is stored in a pre-calculated optimized multidimensional array
instead of in relational database format. MOLAP cubes are built for fast data retrieval, and are
optimal for slicing and dicing operations. MOLAP can perform complex calculations quickly.
O
ODBC Open Database Connectivity. A standard for database connectivity that provides a
standard application interface to conforming databases, including Teradata.
ODBC driver Type of driver used to connect applications with databases. The ODBC driver
processes ODBC calls from an application, but passes SQL requests to the Teradata Database
for processing.
OLAP Online analytical processing. Software technology that allows the user to interpret
multidimensional data from enterprise data warehouse systems. OLAP tools can query and
analyze the information, which has been transformed from raw data into information that
reflects business views of the enterprise. OLAP is also known as decision support processing,
and is a decision support counterpart to online transaction processing (OLTP).
OLAP Connector
See Teradata OLAP Connector.
OLE DB A specification for how to build objects to extract data from a data source. With
OLE DB it is easy to mix data from multiple data source providers and provider types.
OLE DB for OLAP (ODBO) A Microsoft-published specification and an industry standard
for multidimensional data processing. ODBO is the standard API for exchanging metadata
and data between an OLAP server and a client. ODBO extends the ability of OLE DB to access
multidimensional (OLAP) data stores. Excel and other OLAP clients use ODBO to talk to an
OLAP cube.
51
Glossary
P
parent In a hierarchical structure, the parent member is one level higher than its child
member. Usually, the value of the parent is a combination of its children’s values. See also
children.
pivot
To alter the dimensional orientation of a report or page display.
PivotTable A pivot table is a data summarization tool found in spreadsheets such as
Microsoft Excel or business intelligence software. Among other functions, pivot-table tools
can automatically sort, count, and total the data stored in one table or spreadsheet and create
a second table (called a “pivot table”) displaying the summarized data. Pivot tables are also
useful for quickly creating cross tabs. The user sets up and changes the summary's structure by
dragging and dropping fields graphically. This “rotation” or pivoting of the summary table
gives the concept its name. The term pivot table is a generic phrase used by multiple vendors;
however, Microsoft Corporation has trademarked the specific form PivotTable.
R
Relational Online Analytical Processing (ROLAP) Online analytical processing that
provides multidimensional analysis of data, aggregates, and metadata stored in an RDBMS.
The multidimensional processing can be done within the RDBMS, a mid-tier server, or the
client.
S
schema The logical and physical definition of data elements, physical characteristics, and
inter-relationships.
slice A slice can be a single value or a subset of values of a cube. For example, a subset could
be represented as a two dimensional slice out of a three dimensional cube.
slice and dice A complex process of data analysis that involves breaking down information
into smaller parts and examining data from different viewpoints. Querying data and
examining slices, pivoting the data, and drilling down on the data are examples of slice and
dice.
snowflake schema A relational database scheme for representing multidimensional data. A
snowflake schema builds on the concept of a star schema, but involves normalization of
dimension tables into multiple tables where there is typically one table for each level of the
dimension hierarchy. See also star schema.
star schema A relational database schema for representing multidimensional data. Star
schemas normally have a primary or fact table and one or more dimensional tables. The
dimensional tables supply supporting information, such as the demographics for the buyers
listed in the primary fact table. See also snowflake schema.
52
Glossary
T
Teradata Aggregate Designer Used to create Teradata AJIs to support high performance
ROLAP queries to the EDW.
Teradata Aggregate Join Indexes (AJI) Used to accelerate the aggregation required by
MDX.
Teradata Business Intelligence Optimizer (Teradata BIO) A set of software components
that work together to specify the multidimensional model for a ROLAP system, and provide
run-time handling of MDX queries from various BI client applications. The Teradata BIO
solution provides an enterprise class, general purpose MDX/OLAP solution for use on a
ROLAP architecture.
Teradata Schema Workbench Used by OLAP DBAs to indicate how star and snowflake
schemas and fact tables in an RDBMS should be mapped to OLAP cubes, dimensions,
hierarchies, levels, and measures. The resulting cube schema is published by Teradata OLAP
Connector to the EDW for use by BI run-time client applications.
Teradata OLAP Connector A client-side component that enables Microsoft Excel and other
BI client applications that emit MDX query language through a standard ODBO interface to
slice and dice data.
53
Glossary
54
Index
A
architecture
TBIO 15
TBIO repository 17
Teradata OLAP connector 18
attribute members, viewing in Excel 2007 30
axis filters, totals 39
axis row, filtering 38
C
cache settings 41
caching
cells 42
metadata 41
cell caching 42
column row 38
components 15
configuration
driver 19
DSN 19
Excel 2003/XP 23
Excel 2007 20
connection fail 36
cube
schema 16, 17
troubleshooting 38
currency conversion 37
D
data connection fail 36
Data Connection Wizard 21
data filtering 31
database query, Excel 2003/XP 24
dimension levels 30
disabled OLAP cube 38
driver configuration 19
DSN
password 21
DSN Creation 19
E
entities 41
error message
IDispatch 36
initialization of data source failed 35
query did not run 37
TBI Repository version does not match 37
Excel 2003/XP
adding/removing dimensions 33
configuration 23
connection fail 36
database query 24
filtering data 34
PivotTable tasks 33
removing grand totals 33
Excel 2007
configuration 20
connection 21
connection fail 36
empty PivotTable 26
filtering data 31
refresh 22, 40
removing grand totals 29
sorting dimension levels 30
Excel troubleshooting 36, 38
F
failed connection 36
filtering
axis and members 38
data 31
format strings 37
G
grand totals
removing, Excel 2003/XP 33
removing, Excel 2007 29
viewing 38
H
hierarchy 27, 38
I
IDispatch error message 36
L
labels 39
Layout Wizard 33
least recently used algorithm 41, 42
55
Index
LRU algorithm 41, 42
R
M
refresh 22, 40
Release Definition 4
report filters 34
repository architecture 17
maximum entities 41
MDX 18, 36, 45, 46
members, filtering 31
metadata caching
metadata pre-fetching 42
permanent entities 41
transient entities 42
N
named sets, viewing 38
non-visual total 39
O
ODBC
data source 19
documentation 5
ODBO 41
ODBO support 18
OLAP Connector See Teradata OLAP Connector
OLAP cube 22, 23, 38, 41
P
page slicing 34
password override, DSN 21
permanent entities 41
PivotTable
attribute members 30
dimension levels 30
example 26
Excel 2003/XP 33
Excel 2007 26
expanding/collapsing 30
filtering 31, 38
formatting currency 37
grand total, viewing 38
hierarchy 27, 28, 38
named sets, viewing 38
refresh 40
troubleshooting 36
using 25
pre-fetching metadata 42
product release numbers 3
properties 30
Q
query 24, 37, 40
56
S
schema
connect 24
cube 16, 17, 36
snowflake 16, 17
star 17
slicing data 31
software releases, supported 3
sorting 30
T
TBI Repository 17
TBIO architecture 15
Teradata Aggregate Designer 17
Teradata Aggregate Designer documentation 5
Teradata Database
metadata retrieval 41
version 3
Teradata OLAP Connector 18
cell caching 42
documentation 5
metadata caching 41
test connection fails 36
totals
inaccurate 39
non-visual 39
removing Excel 2003/XP 33
removing, Excel 2007 29
viewing 38
transient entities 41, 42
troubleshooting
connection fails 36
error message 37
Excel 36, 38
U
updates 37
username override, DSN 21
V
value filter
accessing 31
support 39
version update 37
viewing 26, 38

Teradata OLAP Connector User Guide - Teradata

Transcription

Similar documents

Freedom to Explore - Teradata Magazine Online

NeueNeue LL öö sungsanssungsans ää tzetze durchdurch Excel

Click Here - Excel Group of Institution

Introduction to Maptitude for MapPoint Users

Boyle`s and Charles`s Gas Law Virtual Lab

Introduction to Teradata RDBMS

Efficiently Maximizing Retail Value Across Distributed Data

FM Video and Data Radio Link 2.4 – 2.5 GHz

TechSmart® High-Temp Headlight Harnesses