Recent comments
What's new in 14.10 for Teradata OLAP Solutions
Teradata OLAP Connector (TOC), Teradata Schema Workbench (TSW), Teradata Aggregate Designer (TAD) and Teradata OLAP Server (TOS) 14.10 releases are now GCA. In addition to several key new features, this release adds Teradata OLAP Server which includes an XMLA engine that provides data access interaction between a client application and a Business Intelligence provider working over the Internet providing direct and optimized access to the Teradata ROLAP environment. Teradata OLAP solutions can now be deployed with more than just Excel as BI vendors support now includes arcplan and Tableau using TOC and SAP Business Objects through TOS. And for users who support multiple BI tools, they can now be deployed using the same Multi-Dimensional Model built on Teradata. In leveraging the same multidimensional model, all investments in optimization and performance are shared across the entire customer set of BI tool users. This ensures overall lower Total Cost of Ownership.
New General Product Features
- Teradata Database and TTU 14.10 Support
- Push-Down Calculations: Performance Improvement that removes the all-or-nothing restriction in the Push-Down feature that shipped in the 14.00.01 Maintenance release Imagine you have a base measure (Sum of Sales), a calculated measure that can be pushed down (Pushdown measure, which is a measure written using the MDX functions described in the maintenance release) and a calculated measure that cannot be pushed down (Un-pushable measure, one that falls outside the list of supported MDX functions as previously written).
The following table shows some behavior changes:
|
Query |
14.00 Maintenance Release |
14.10 release |
|
Pivot table requesting two values, Sum of Sales and Unpushable measure |
Nothing pushed down |
Sum of Sales pushed down, Unpushable measure not pushed down |
|
Pivot table requesting two values, Pushable measure and unpushable measure |
Nothing pushed down |
Pushable measure pushed down, unpushable measure not pushed down |
This behavior should be true in many scenarios, including when filters are applied, calculated members are used on rows, etc.
- Trusted Session connection support through SET QUERY_BAND
- Memory utilization in the MDX engine has been optimized for performance improvement when a hierarchy level owns many MEMBERS (40 or more)
- Long Database Column names (up to 128 characters versus 30) is now supported
Teradata OLAP Connector
- Support for Excel 2007, 2010 and 2013, Tableau 8.1 and arcplan 7.1
- Client Side Operating support includes Microsoft Vista, Windows 7 and Windows 8, Microsoft Server 2008, 2008R2 and 2012
- Key new Excel features supported (Updated PivotChart, Calculated Measure, Calculated Members, Drill Down/Up)
- Excel Advanced Features – Sub queries (Slicers, Drill Down/Up, Label/Value filtering)
- Visual Totals is now enabled. This means that the grand totals and sub totals in a pivot table now change whenever the filters on the screen change. So if you drill up, down, apply a slicer, apply a filter (label, value, whatever) – the grand totals and the sub totals reflect the values in view on the pivot table.
Teradata OLAP Server
- Support for SAP BO 4.1
- XMLA service hosted on JBoss 7.1.1 on Windows Server 2008 R2 and 2012
Teradata Aggregate Designer
- Teradata Schema Workbench, Teradata OLAP Connector and Teradata OLAP Server 14.10 Support
- Added SQL Server 2012, COGNOS 10.2 Schema Support
- Support for Microsoft Windows 8 and Microsoft Server 2012 (excluding JRE 1.7)
- Added support for MIN and MAX aggregation types
- Mismatched Data Type Measure Overflow check
- Explorer option to change DBQL Database Name and Table Mapping
Nice to have access to ROLAP environment. I hope the creation of AJIs through Aggregate designer is easy.
Thanks and regards,
Raja
Raja K Thaw
My wiki: http://en.wikipedia.org/wiki/User:Kt_raj1
Street Children suffer not by their fault. We can help them if we want.
Teradata Aggregate Designer is a productivity tool used to design, validate, recommend and create AJI's to support performance optimization. The Explorer option in this tool can be used to further optimize AJI's once deployed.
what is the alternative of orcale package in teradata??
Not sure what was meant by orcacle package in Teradata? In an attempt to clarify
Teradata OLAP Connector is a client-side MDX engine that provides direct and optimized access for OLAP/MDX clients like Excel PivotTables, Tableau and arcplan directly from Teradata in a ROLAP environment. This would replace the more traditional MOLAP solution where data is extracted from the warehouse to an OLAP client or middle-tier server. It's a more effective approach to supporting business users who require multidimensional database access.
How does this work with a microstrategy reporting solution? We struggle with generated sql bogging down teradata sometimes - ideally pre-aggregation would help, but if data is in MDX, teradata olap might solve our problem?
Today the OLAP Connector is certified for use with Excel and by Tableau and arcplan. OLAP Server is certified by SAP BO Analysis for OLAP. Neither of these solutions has been certified by MSI. You are coorect in that if it were certified, you could leverage Teradata Aggregate Designer within the solution.
IS there a way to show MoM report in OLAP. What I am looking for is to select Date in both column and row and it should show me the difference from Month to Month
There is a way to present MoM report defining calculated measure in MDX with Schema Workbench.
One of example with leaf level = month would be;
(Time.[Calendar Time].CurrentMember, [Measures].[Sales])
- (Time.[Calendar Time].CurrentMember.PrevMember, [Measures].[Sales])
This will aggregate Sales per month and compare with previous and current.
This example is available at Schema Workbench package as a sample schema.
Hi Team,
Please let me know the best approach to clear the BASIC level certification TE0-141?
Regards,
Saurabh
Hi Mark,
We're currently using BO 4.1 as the BI tool and Teradata 13.10 (soon to upgrade to 14.00). We currently have star schemas in Teradata to which we connect via BO relational universes, which work good. We want to use OLAP Analysis as well on the same schemas.
After reading your comments I believe if we had to use OLAP Analysis in BO, we've got to use only the XMLAWebService (the OLAP Connector wouldn't help) right?
Wanted to check with you, if I install the XMLAWebService (OLAP Server) on a server which can talk to Teradata via ODBC, on the Teradata schema itself what would we need? Would there be a cube / aggregation that we'd need to design and implement?
Thanks in advance,
Regards,
Joe Ferrao
Joe Ferrao
If you are going to leverage Teradata OLAP portfolio with BO Analysis for OLAP then you are correct it would require Teradata OLAP Server running on Windows Server which connects to Teradata via ODBC. This will only work with Teradata schema that has been developed and deployed using Teradata Schema Workbench. Once deployed, Teradata Aggregate Designer can then be leverage to develop Aggregate Join Indexes for use in performance optimization.
The product model for the join index is very good, but I would like to ask a question about the join index in general, hoping not to go off topic.
When it is possibile to insert new monthly incrementally to the join index without having to recharge fully, as if I have a fact table of 48 months and I have a very large incremental than a month because I have to recreate the join index completely and I can not just enter the new aggregate, would save a lot of processing time, as well as in other databases. thank you for your future response.
Best Regards Silvio Andreoli
If you are trying to make a partial AJI that only reflects monthly incremental. The AJI can be crafted by having a where constraint which will beneficial for AJI creation.
However, if a query does not have the same where constraint, the optimizer won’t be able to utilize the AJI. In other words, if the query is fixed (always having the same where constraint), the AJI can be utilized.
Otherwise, having proper PIs for AJI's might be helpful to reduce the AJI creation time. Also, putting a partition on the AJI would be an approach that might be worth considering as well.
Finally, you might also reference the Teradata Aggregate Designer Orange Book as it includes addition suggestions around AJI optimizations.