DOCSLIB.ORG

SAP HANA™ Storage Requirements

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SAP HANA™ Storage Requirements SAP HANA¥ Storage Requirements As an in-memory database, SAP HANA uses storage devices to save a copy of the data, for the purpose of startup and fault recovery without data loss. The choice of the specific storage technology is driven by various requirements like size, performance and high availability. This paper discusses the SAP HANA storage requirements. __________________________ SAP HANA Development Team V2.5, January 2015 Contents Legal Disclaimer ..................................................................................................................................3 Change history ....................................................................................................................................3 1 Introduction ................................................................................................................................4 Conceptual Storage Layout .............................................................................................................4 Sizing ..............................................................................................................................................6 Disk Space Required for the Data Volume ...................................................................................7 Disk Space Required for the Log Volume .....................................................................................7 Disk Space Required for SAP HANA Installation ...........................................................................8 Disk Space Required for Backups .................................................................................................8 Disk Space Required for Exports ..................................................................................................9 2 High Availability ..........................................................................................................................9 Failure Recovery: Host Auto-Failover...............................................................................................9 Failure Detection and Failover....................................................................................................... 10 File Access and Fencing ................................................................................................................. 10 Non-shared Storage .................................................................................................................. 10 Shared Storage with Shared File Systems .................................................................................. 11 Disaster Recovery Approaches ...................................................................................................... 12 Backups..................................................................................................................................... 12 Storage Replication ................................................................................................................... 13 System Replication .................................................................................................................... 14 3 Performance ............................................................................................................................. 15 Scenarios ...................................................................................................................................... 15 I/O Patterns .................................................................................................................................. 17 I/O Sizing ...................................................................................................................................... 17 4 Summary................................................................................................................................... 19 5 Acknowledgements ................................................................................................................... 19 6 Terminology Appendix .............................................................................................................. 20 7 References ................................................................................................................................ 21 © 2015 SAP SE page 2/21 Legal Disclaimer THIS DOCUMENT IS PROVIDED FOR INFORMATION PURPOSES ONLY AND DOES NOT MODIFY THE TERMS OF ANY AGREEMENT. THE CONENT OF THIS DOCUMENT IS SUBJECT TO CHANGE AND NO THIRD PARTY MAY LAY LEGAL CLAIM TO THE CONTENT OF THIS DOCUMENT. IT IS CLASSIFIED AS “CUSTOMER” AND MAY ONLY BE SHARED WITH A THIRD PARTY IN VIEW OF AN ALREADY EXISTING OR FUTURE BUSINESS CONNECTION WITH SAP. IF THERE IS NO SUCH BUSINESS CONNECTION IN PLACE OR INTENDED AND YOU HAVE RECEIVED THIS DOCUMENT, WE STRONGLY REQUEST THAT YOU KEEP THE CONTENTS CONFIDENTIAL AND DELETE AND DESTROY ANY ELECTRONIC OR PAPER COPIES OF THIS DOCUMENT. THIS DOCUMENT SHALL NOT BE FORWARDED TO ANY OTHER PARTY THAN THE ORIGINALLY PROJECTED ADDRESSEE. This document outlines our general product direction and should not be relied on in making a purchase decision. This document is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this document. This document and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document and shall have no liability for damages of any kind that may result from the use of these materials, except if such damages were caused by SAP intentionally or grossly negligent. © Copyright 2015 SAP SE. All rights reserved. Change history Version Date Description 1.9 June 2013 Initial release 2.0 November 2013 Added Storage Sizing section Added Performance Section 2.1 December 2013 Improved information about IO fencing with NFS based shared storages 2.2 May 2014 Updated sizing formulas Minor fixes 2.3 July 2014 Minor fixes 2.4 October 2014 Updated Sizing chapter: New formula for redo log sizing 2.5 January 2015 Updated Sizing chapter: Distinguish total memory and net data size on disk © 2015 SAP SE page 3/21 1 Introduction SAP HANA is an in-memory database which stores and processes the bulk of its data in memory. Additionally it provides protection against data loss by saving the data in persistent storage locations. For setting up a SAP HANA system, the storage layer must fulfill several requirements. This paper discusses the different requirements and common design options for the storage subsystem. Especially when using high availability and disaster tolerance features, care must be taken on planning the persistent space. SAP HANA uses storage for several purposes: x The SAP HANA installation. This directory tree contains the run-time binaries, installation scripts and other support scripts. In addition, this directory tree contains the SAP HANA configuration files, and is also the default location for storing trace files and profiles. On distributed systems, it is created on each of the hosts. x Backups. Regularly scheduled backups are written to storage in configurable block sizes up to 64 MB. x Data. SAP HANA persists a copy of the in-memory data, by writing changed data in the form of so-called savepoint blocks to free file positions, using I/O operations from 4 KB to 16 MB (up to 64 MB when considering super blocks) depending on the data usage type and number of free blocks. Each SAP HANA service (process) separately writes to its own savepoint files, every five minutes by default. x Redo Log. To ensure the recovery of the database with zero data loss in case of faults, SAP HANA records each transaction in the form of a so-called redo log entry. Each SAP HANA service separately writes its own redo-log files. Typical block-write sizes range from 4KB to 1MB. Each service of a distributed (multi-host) SAP HANA system manages its persistence independently. Logically, this is a shared-nothing approach. ConceptualStorageLayout The following illustration shows the recommended structure of a SAP HANA installation, showing a distributed SAP HANA system (named H36) with n=2 hosts. Following figure represents the file system structure of a SAP HANA setup. For the plain Linux installation 10 GB of disk size is recommended – the storage size requirements of a SAP HANA installation are expressed as a function of the host memory size (see Sizing). Additionally, at least 50 GB must be provided for the /usr/sap location in the system as this is the place where other SAP software that supports SAP HANA will be installed. It is possible to join this location with the Linux installation. © 2015 SAP SE page 4/21 / (root) Linux /usr/sap /hana 10GB 50GB data log shared H36 H36 H36 mnt00001 mnt00002 mnt00001 mnt00002 hdb00001 hdb00005 hdb00001 hdb00005 hdb00002 hdb00002 hdb00003 hdb00003 hdb00004 hdb00004 When installing SAP HANA on a host, you specify where to place the installation binaries (by default: /hana/shared/<sid>, where sid is the instance identifier of the SAP HANA installation), as well as the destination for the data and log files. In the case of a simple, single-host
Load more

Recommended publications
  • Changing the Game: Monthly Technology Briefs
    the way we see it Changing the Game: Monthly Technology Briefs April 2011 Tablets and Smartphones: Levers of Disruptive Change Read the Capgemini Chief Technology Officers’ Blog at www.capgemini.com/ctoblog Public the way we see it Tablets and Smartphones: Levers of Disruptive Change All 2010 shipment reports tell the same story - of an incredible increase in the shipments of both Smartphones and Tablets, and of a corresponding slowdown in the conventional PC business. Smartphone sales exceeded even the most optimis- tic forecasts of experts, with a 74 percent increase from the previous year – around a battle between Apple and Google Android for supremacy at the expense of traditional leaders Nokia and RIM BlackBerry. It was the same story for Tablets with 17.4 million units sold in 2010 led by Apple, but once again with Google Android in hot pursuit. Analyst predictions for shipments suggest that the tablet market will continue its exponential growth curve to the extent that even the usually cautious Gartner think that by 2013 there will be as many Tablets in use in an enterprise as PCs with a profound impact on the IT environment. On February 7, as part of the Gartner ‘First Thing Monday’ series under the title ‘The Digital Natives are Restless, The impending Revolt against the IT Nanny State’ Gartner analyst Jim Shepherd stated; “I am regularly hearing middle managers and even senior executives complaining bit- terly about IT departments that are so focussed on the global rollout of some monolith- ic solution that they have no time for new and innovative technologies that could have an immediate impact on the business.
    [Show full text]
  • Synopsys: Large Graph Analytics in the SAP HANA Database Through Summarization
    SynopSys: Large Graph Analytics in the SAP HANA Database Through Summarization Michael Rudolf1 Marcus Paradies1 Christof Bornhövd2 Wolfgang Lehner3 1SAP AG 2SAP Labs, LLC 3Database Technology Group Walldorf, Germany Palo Alto, CA 94304, USA TU Dresden, Germany [email protected] [email protected] [email protected] ABSTRACT “Cell Phones “Computers & & Accessories” Graph-structured data is ubiquitous and with the advent of social Accessories” 4 networking platforms has recently seen a significant increase in 6 popularity amongst researchers. However, also many business appli- part of part of “Freddy” cations deal with this kind of data and can therefore benefit greatly 10 “Mike” from graph processing functionality offered directly by the underly- 8 5 “Phones” “Tablets” 7 ing database. This paper summarizes the current state of graph data in rates 4/5 processing capabilities in the SAP HANA database and describes our efforts to enable large graph analytics in the context of our research in 11 “Steve” rates 5/5 white 3 “Apple in project SynopSys. With powerful graph pattern matching support at iPhone 4” 16 GB the core, we envision OLAP-like evaluation functionality exposed to rates 5/5 the user in the form of easy-to-apply graph summarization templates. black rates 3/5 black 64 GB 1 32 GB 2 By combining them, the user is able to produce concise summaries 9 of large graph-structured datasets. We also point out open questions “Apple iPad “Apple and challenges that we plan to tackle in the future developments on MC707LL/A” “Carl” iPhone 5” our way towards large graph analytics.
    [Show full text]
  • SAP HANA Client Interface Programming Reference for SAP HANA Platform Company
    PUBLIC SAP HANA Platform 2.0 SPS 04 Document Version: 1.1 – 2019-10-31 SAP HANA Client Interface Programming Reference for SAP HANA Platform company. All rights reserved. All rights company. affiliate THE BEST RUN 2019 SAP SE or an SAP SE or an SAP SAP 2019 © Content 1 SAP HANA Client Interface Programming Reference.................................17 2 Configuring Clients for Secure Connections.......................................19 2.1 Server Certificate Authentication.................................................19 2.2 Mutual Authentication........................................................ 20 Implement Mutual Authentication..............................................20 2.3 Configuring the Client for Client-Side Encryption and LDAP.............................. 26 3 Connecting to SAP HANA Databases and Servers...................................27 3.1 Setting Session-Specific Client Information..........................................29 3.2 Use the User Store (hdbuserstore)................................................32 4 Client Support for Active/Active (Read Enabled)...................................34 4.1 Connecting Using Active/Active (Read Enabled)...................................... 34 Client Requirements For A Takeover.............................................35 4.2 Hint-Based Statement Routing for Active/Active (Read Enabled)...........................36 4.3 Forced Statement Routing to a Site for Active/Active (Read Enabled)........................37 Implement Forced Statement Routing to a Site for Active/Active
    [Show full text]
  • Compact and Efficient Representation of General Graph Databases
    This is a post-peer-review, pre-copyedit version of an article pub- lished in Knowledge and Information Systems. The final authenti- cated version is available online at: http://dx.doi.org/10.1007/ s10115-018-1275-x Compact and Efficient Representation of General Graph Databases1 Sandra Alvarez-Garc´ıa´ 1, Borja Freire2, Susana Ladra3 and Oscar´ Pedreira3 1Indra, A Coru~na,Spain; 2 Enxenio S.L., A Coru~na,Spain; 3 Universidade da Coru~na, CITIC, Database Laboratory, A Coru~na,Spain Abstract. In this paper, we propose a compact data structure to store labeled at- tributed graphs based on the k2-tree, which is a very compact data structure designed to represent a simple directed graph. The idea we propose can be seen as an extension of the k2-tree to support property graphs. In addition to the static approach, we also pro- pose a dynamic version of the storage representation, which allows flexible schemas and insertion or deletion of data. We provide an implementation of a basic set of operations, which can be combined to form complex queries over these graphs with attributes. We evaluate the performance of our proposal with existing graph database systems and prove that our compact attributed graph representation obtains also competitive time results. Keywords: Compression; Graph Databases; Property Graphs; Attributed Graphs; Compact Data Structures; Dynamic Graphs 1. Introduction Graphs are a natural way for modeling data in such domains where the most arXiv:1812.10977v1 [cs.DS] 28 Dec 2018 relevant information relies on the relationships between the entities. Some rep- resentative examples are Web graphs (Raghavan and Garcia-Molina 2003), so- cial networks (Padrol-Sureda et al.
    [Show full text]
  • SAP on Google Cloud: High Availability
    SAP on Google Cloud: High availability Overview © 2020 Google LLC. All rights reserved. Contents About this document 2 Introduction 2 Levels of high availability 3 Level 1: Infrastructure 3 Zones and regions 3 Live migration 4 Host auto restart 4 Level 2: Database setup 5 SAP HANA databases 5 Synchronous SAP HANA System Replication 5 SAP HANA host auto-failover on Google Cloud 7 SAP ASE databases 8 MaxDB databases 8 IBM Db2 databases 9 Microsoft SQL Server databases 9 Level 3: Application servers 10 Summary 12 Further reading 13 ​1 ​© 2020 Google LLC. All rights reserved. About this document This document is part of a series about working with SAP on Google Cloud. The series includes the following documents: ● High availability (this document) ● Migration strategies ● Backup strategies and solutions ● Disaster-recovery strategies Introduction The term high availability (HA) is used to describe an architecture that improves a system’s ​ ​ availability. The availability of a system refers to a user’s ability to connect to the system and conduct the required operations. If a user can’t connect, the system is perceived as unavailable, regardless of the underlying issue. For example, a networking issue can prevent users from accessing the service, even though the system is running. A high-availability setup interacts with multiple components of the architecture to minimize the points of failure, typically by using redundancy. To measure a service’s performance throughout the year, the metric of percentage of uptime is ​ ​ used to calculate the ratio of uptime to the aggregate of uptime and downtime. A system that is available for ~8750 hours during the 8760 hours of a year has an uptime of 99.89% (8750/8760) and a downtime of 10 hours.
    [Show full text]
  • New Sap Framework Marries Geospatial Data with Hana Business Data
    ▲ E-Guide NEW SAP FRAMEWORK MARRIES GEOSPATIAL DATA WITH HANA BUSINESS DATA SearchSAP NEW SAP FRAMEWORK MARRIES GEOSPATIAL DATA WITH HANA BUSINESS DATA Home New SAP framework marries geospatial data with HANA business data ISCOVER THE NEW SAP framework that D marries geospatial data with HANA business data in this expert e-guide. Learn how it can help organizations enrich business applications with geospatial data from geographic information systems (GIS) like Esri ArcGIS. Also, find out about the latest version of SAP Business One. PAGE 2 OF 9 SPONSORED BY NEW SAP FRAMEWORK MARRIES GEOSPATIAL DATA WITH HANA BUSINESS DATA NEW SAP FRAMEWORK MARRIES GEOSPATIAL DATA WITH HANA BUSINESS DATA Jim O’Donnell, News Editor Home New SAP framework The marriage of SAP HANA business data and Esri mapping information marries geospatial data with HANA became more solid with the release of SAP Geographical Enablement Frame- business data work. Esri is a geospatial data company based in Redlands, Calif. Recent releases of SAP HANA have included features that integrated Esri geospatial data into HANA applications, and the SAP Geographic Enablement Framework extends this integration as a standalone product, according to Karsten Hauschild, SAP solution manager. The framework helps organizations to enrich business applications with geospatial data from geographic information systems (GIS) like Esri ArcGIS, Hauschild said. This can help drive applications that go beyond the simple map-related software found on consumer mobile devices. “If you look at what’s going on now, these map-driven user experiences are enabled on these mobile devices with built-in GPS, but that’s only on the con- sumer side, and they are satisfied by locating places or checking directions,” PAGE 3 OF 9 SPONSORED BY NEW SAP FRAMEWORK MARRIES GEOSPATIAL DATA WITH HANA BUSINESS DATA Hauschild said.
    [Show full text]
  • SAP HANA – from Relational OLAP Database to Big Data Infrastructure
    SAP HANA – From Relational OLAP Database to Big Data Infrastructure Norman May, Wolfgang Lehner, Shahul Hameed P., Nitesh Maheshwari, Carsten Müller, Sudipto Chowdhuri, Anil Goel SAP SE fi[email protected] ABSTRACT and data formats [5]. Novel application scenarios address primar- SAP HANA started as one of the best-performing database engines ily a mixture of traditional business applications and deep analytics for OLAP workloads strictly pursuing a main-memory centric ar- of gathered data sets to drive business processes not only from a chitecture and exploiting hardware developments like large number strategic perspective but also to optimize the operational behavior. of cores and main memories in the TByte range. Within this pa- With the SAP HANA data platform, SAP has delivered a well- per, we outline the steps from a traditional relational database en- orchestrated, highly tuned, and low-TCO software package for push- gine to a Big Data infrastructure comprising different methods to ing the envelope in Big Data environments. As shown in figure 1, handle data of different volume, coming in with different velocity, the SAP HANA data platform is based in its very core on the SAP and showing a fairly large degree of variety. In order to make the HANA in-memory database system accompanied with many func- presentation of this transformation process more tangible, we dis- tional and non-functional components to take the next step towards cuss two major technical topics–HANA native integration points mature and enterprise ready data management infrastructures. In as well as extension points for collaboration with Hadoop-based order to be aligned with the general “definition” of Big Data, we data management infrastructures.
    [Show full text]
  • Database Software Market: Billy Fitzsimmons +1 312 364 5112
    Equity Research Technology, Media, & Communications | Enterprise and Cloud Infrastructure March 22, 2019 Industry Report Jason Ader +1 617 235 7519 [email protected] Database Software Market: Billy Fitzsimmons +1 312 364 5112 The Long-Awaited Shake-up [email protected] Naji +1 212 245 6508 [email protected] Please refer to important disclosures on pages 70 and 71. Analyst certification is on page 70. William Blair or an affiliate does and seeks to do business with companies covered in its research reports. As a result, investors should be aware that the firm may have a conflict of interest that could affect the objectivity of this report. This report is not intended to provide personal investment advice. The opinions and recommendations here- in do not take into account individual client circumstances, objectives, or needs and are not intended as recommen- dations of particular securities, financial instruments, or strategies to particular clients. The recipient of this report must make its own independent decisions regarding any securities or financial instruments mentioned herein. William Blair Contents Key Findings ......................................................................................................................3 Introduction .......................................................................................................................5 Database Market History ...................................................................................................7 Market Definitions
    [Show full text]
  • What's New in the SAP HANA Client Company
    INTERNAL SAP HANA Client 2.4 Document Version: 1.1 – 2020-10-26 What's New in the SAP HANA Client company. All rights reserved. All rights company. affiliate THE BEST RUN 2020 SAP SE or an SAP SE or an SAP SAP 2020 © Content 1 New and Changed Features in the SAP HANA Client..................................3 What's New in the SAP HANA Client 2 INTERNAL Content 1 New and Changed Features in the SAP HANA Client Note Information about earlier versions of the SAP HANA Client (prior to version 2.4) is included in the SAP HANA Platform documentation. Client Version Type Description 2.4 New Direct TCP You can create an HTTP and TLS proxy connection with­ Connec­ out using WebSockets, tions Through an allowing direct TCP con­ HTTP Proxy nections via an HTTP proxy. HTTP Proxy Client Con­ nections Implement HTTP Proxy Client Connections JDBC Connection Prop­ erties 2.4 New SAP SAP HANA Cloud supports HANA SNI routing. You must use Cloud version 2.4.167 (2.4.67 for Sup­ port the JDBC driver) or later of the SAP HANA client inter­ faces with SAP HANA Cloud. There are also restrictions on the platforms that sup­ port SAP HANA Cloud. 2.5 New .NET A new environment varia­ Core En­ ble, HDBDOTNETCORE, hance­ and examples have been ments added for .NET Core. Run the .NET Core Exam­ ples What's New in the SAP HANA Client New and Changed Features in the SAP HANA Client INTERNAL 3 Client Version Type Description 2.5 New .NET You can now develop .NET Core Core applications on Linux Sup­ and macOS with the SAP ports Li­ nux and HANA client.
    [Show full text]
  • SAP on AWS Overview
    SAP on AWS Overview April 2017 Amazon Web Services – SAP on AWS Overview April 2017 © 2017, Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether express or implied. This document does not create any warranties, representations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. Page 2 of 13 Amazon Web Services – SAP on AWS Overview April 2017 Contents Abstract 4 AWS Overview 4 Global Infrastructure 4 AWS Security and Compliance 5 AWS Products and Services 5 SAP on AWS 6 AWS and SAP Alliance 6 Benefits of Running SAP on AWS 7 SAP Support on AWS 7 SAP on AWS Use Cases 8 SAP on AWS Case Studies 9 SAP Licensing on AWS 9 Managed Services for SAP on AWS 10 SAP System Deployment 10 SAP HANA on AWS 11 Pricing SAP on AWS 12 Additional Information 12 Contributors 12 Notes 13 Page 3 of 13 Amazon Web Services – SAP on AWS Overview April 2017 Abstract Companies of all sizes can take advantage of the many benefits provided by Amazon Web Services (AWS) to achieve business agility, cost savings, and high availability by running their SAP environments on the AWS Cloud.
    [Show full text]
  • The Forrester Wave™: In-Memory Database Platforms, Q3 2015 by Noel Yuhanna August 3, 2015
    FOR ENTERPRISE ARCHITECTURE PROFESSIONALS The Forrester Wave™: In-Memory Database Platforms, Q3 2015 by Noel Yuhanna August 3, 2015 Why Read This Report Key Takeaways The in-memory database platform represents a SAP, Oracle, IBM, Microsoft, And Teradata new space within the broader data management Lead The Pack market. Enterprise architecture (EA) professionals Forrester’s research uncovered a market in which invest in in-memory database platforms to SAP, Oracle, IBM, Microsoft, and Teradata lead support real-time analytics and extreme the pack. MemSQL, Kognitio, VoltDB, DataStax, transactions in the face of unpredictable mobile, Aerospike, and Starcounter offer competitive Internet of Things (IoT), and web workloads. options. Application developers use them to build new The In-Memory Database Platform Market Is applications that deliver performance and New But Growing Rapidly responsiveness at the fastest possible speed. The in-memory database market is new but Forrester identified the 11 most significant growing fast as more enterprise architecture software providers — Aerospike, DataStax, professionals see in-memory as a way to address IBM, Kognitio, MemSQL, Microsoft, Oracle, their top data management challenges, especially SAP, Starcounter, Teradata, and VoltDB — in the to support low-latency access to critical data for category and researched, analyzed, and scored transactional or analytical workloads. them against 19 criteria. This report details how well each vendor fulfills Forrester’s criteria and Scale, Performance, And Innovation where the vendors stand in relation to each Distinguish The In-Memory Database Leaders other to meet next-generation real-time data The Leaders we identified offer high-performance, requirements. scalable, secure, and flexible in-memory database solutions.
    [Show full text]
  • The Topic of Procedures and HANA SQL Script for SAP Business One, Version for SAP HANA
    Welcome to the topic of procedures and HANA SQL Script for SAP Business One, version for SAP HANA. 1 At the end of this topic, you will be able to describe how procedures can be used for modeling and list some tips for working with HANA SQL Script. We will see how to create a procedure . 3 HANA procedures are frequently used as a data source for dashboards and Crystal reports. You can use procedures separately or in combination with views. 4 We have looked at calculation views, now we will look at procedures. What is the difference between a procedure and calculation view and when should each be used? Procedures are quite popular for use in Crystal Reports and dashboards. We can use a query as a data source for both Crystal or a dashboard, but if we had instead created a calculation view, we could only consume it in Crystal as a table. In dashboard development you cannot include a table as a data source. You always run a query to retrieve a dataset as data source for a dashboard. From the perspective of the semantic model, a calculation view can define attributes and measures. Using the MDX query, we can do some aggregation over the measures during the query execution. However, we can not do an MDX query over a procedure. In summary, a calculation view can be retrieved as a semantic model, while just a simple query cannot be regarded as a semantic model and cannot be invoked in an MS Excel pivot table. However, another possible option for dashboard development is to use the combination of a calculation view and a query for a dashboard.
    [Show full text]