essbase11_managing asdb
DESCRIPTION
Essbase 11 - ASO Applications - part 4TRANSCRIPT
Corporate Template 2004Hyperion Essbase 7X: New Features
Managing Aggregate Storage Databases
Presentation Title
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Objectives
At the end of this lesson, you should be able to:
Manage tablespaces and storage caches
Optimize outline paging
Identify security considerations
Explain database statistics
Presentation Title
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Tablespace Overview
A tablespace defines database storage in the form of file locations.
Each aggregate storage application has four tablespaces
Default: the database values
Temp: temporary work space
Log: transaction log files
Metadata: the database data structure
A file location specifies a physical disk space for storing database files.
File location 2
Presentation Title
Tablespace describes where and how the files for physical storage can be allocated. Cubes never span tablespaces. Each tablespace may contain one or more file locations. File location is a full path to the directory where the data files will be stored, along with several parameters (max. file size and max. disk space consumption). By having multiple file locations within the same tablespace you can allow a cube to span multiple physical drives or logical volumes.
During both the data load and aggregation process data is being stored in both the Temp and Default directories of an Aggregate Storage database. By using separate physical drives and I/O channels for the location of these files you can reduce I/O contention or bottle necks and therefore improve overall performance. Storing large databases on different physical drives with different I/O channels can also improve query performance.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Specifying Location Properties
Location properties specify
maximum disk space to be used in the directory
maximum file size allowed within the location
Max Disk Size: 200MB
Max File Size: 16MB
File location path
Presentation Title
The Application Servies creates data files named essn.dat in a subdirectory of the file location path, where n is a decimal digit. For instance, if the file location path is C:\ Hyperion\Essbase, the application name is ASOsample, and the tablespace name is default, then the C:\Hyperion\Essbase\ASOsample\default application subdirectory is created when the file location is created, and the data files are put in that subdirectory.
The creation of the file location fails if the application subdirectory already exists or if the file location path does not exist.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Managing Tablespaces
You can manage only the Default and Temp tablespaces by using either
of the two methods:
Presentation Title
Tablespace Manager controls all aspects of retrieving and storing data and works with tablespace definitions to manage the physical disk for data storage and work areas.
When Analytic Services expands a file or adds a file to a tablespace, it will look for space in the first location listed. If there is not enough disk space, the subsequent locations are checked in order. When all space has been used, an error message is returned. When values in a database are cleared, the files in the tablespaces shrink, releasing disk space. When work files are no longer needed, they are deleted and disk space in the tablespace is released. If space is unused, other computer programs can use it.
When an aggregate storage application starts first time, the Analytic Services creates two system tablespaces and adds file location %ARBORPATH%\app to each of them. These tablespaces are “metadata” and “log”. These tablespaces are not user-visible, cannot be changed in any way and are not expected to grow much beyond their initial size (2-8MB each). Additionally, two user-visible tablespaces are created, with names “default” and “temp”. They are initially set to use the same single file location with no file size/disk space limits, but the user can later remove that file location and/or add mode locations. Temporary tablespace is used to store intermediate results during data loads, batch calculations and queries. The “default” tablespace is used to store cube data.
Tablespaces themselves cannot be removed or renamed.
All operations are performed on the file locations within “temp” or “default” tablespaces. File location cannot be removed if there’s already some data loaded into the cube. When you remove a file location, all files created within that file location will be removed, and then the additional subdirectory named “appname\tablespace-name” will be removed as well.
There’s no way to change a path for a file location – one needs to drop it and create a new file location instead. One consequence is that a database cannot be named “default”, ”log”, “metadata” or “temp”.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Aggregate Storage Cache Overview
Essbase allocates an aggregate storage cache, a small area in memory, per application to speed up data loads, aggregations, and retrievals.
The 32 Mb default cache size supports 2Gb of level 0 data.
The cache size is affected by the number of application threads.
Your cache size, in Mb = 32Mb * (Your size of level-0 data, in Gb / 2Gb)
essbase.cfg
Presentation Title
Analytic Services uses the aggregate storage cache to facilitate use of memory during data loads, aggregations, and retrievals. When an aggregate storage application is started, Analytic Services allocates a small area in memory as the aggregate storage cache for the application. As additional cache area is needed, Analytic Services increases the cache size incrementally until the maximum cache size specified for the application is reached or until the operating system denies additional allocations.
In some situations, changing the current setting can optimize use of memory. By default, the cache size is set at 32 MB, the minimum size for the setting. As a general guideline, you can use the size of input-level data to determine when to increase the maximum size for the cache. The size of input-level data is the size of level 0 values.
A 32 MB cache setting supports a database with approximately 2 GB of input-level data. If the input-level data size is greater than 2 GB by some factor, the aggregate storage cache can be increased by the square root of that factor. For example, if the input-level data size is 3 GB (which is 2 GB * 1.5), multiply the aggregate storage cache size of 32 MB by 1.22 (which is approximately the square root of 1.5), and set the aggregate cache size to the result: 39.04 MB.
Another factor to consider is the number of threads set for parallel calculation. Essbase uses multiple threads during the aggregation materialization process. The threads divide up aggregate storage cache. If you increase the number of threads specified in the CALCPARALLEL configuration setting for aggregate storage applications or databases (in aggregate storage databases, performance can be improved by setting the number of threads larger than the number of processors), consider the possible need to increase the size of the aggregate storage cache. Typically increasing the cache by the same factor as the threads should yield good results
The cache is partially allocated at the application startup, and grows on demand later until it reaches the configured limit. Initially, only minimal amount of memory is allocated, and if that fails, the server will refuse to start. That amount is 8MB or 64KB for each server thread, whatever is greater. Note that if the cache size is less than SERVERTHREADS * 64K + 8M, the size is silently increased to that value.
If at some point system refuses to allocate more memory for the cache, the cache size is adjusted down to the current size of the cache.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Viewing the Aggregate Cache Statistics
You can check the following runtime
statistics for the aggregate storage
cache:
Presentation Title
You can view the following aggregate storage run-time statistics under the Run-time node in the Statistics tab of the Database Properties window:
Cache hit ratio: Ratio of the number of requests answered from the aggregate storage cache as opposed to from the hard disk.
Current cache size (KB): The current size of the aggregate storage cache. The aggregate storage cache grows dynamically up to the specified limit.
Current cache size limit (KB): The current setting for the maximum size to which the aggregate storage cache may grow.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Managing the Aggregate Storage Cache
You can change the aggregate cache size limit by using either of the two
methods:
Presentation Title
The maximum size of the aggregate storage cache can be set through two different methods:
In the Administration Services Console
By executing a MaxL DDL statement
To change the size of the aggregate storage cache in the Administration Console:
From Enterprise View or a custom view, select the application.
Right-click and select Edit properties from the pop-up menu.
In the Application Properties window, select the General tab.
Next to the Pending cache size limit node, enter a value, in megabytes, for the size of the cache.
Click Apply.
To change the maximum size of the aggregate storage cache using MaxL DDL to 64MB, you can write the following statement:
alter application ASOSamp set cache_size 64MB;
The cache setting takes effect after the application is restarted
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Outline Paging Overview
Outline pages
8192 bytes
8192 bytes
Presentation Title
Outline Paging
Aggregate storage database outlines are pageable. This feature may significantly reduce memory usage for very large database outlines. For aggregate storage databases, Essbase Analytic Services preloads part of the database outline into memory instead of preloading the entire outline into memory. This allows optimal performance during name lookup that is needed during data load, reporting, spreadsheet and MDX queries. During data retrieval Analytic Services pages other parts of the outline into memory as required. When you create an aggregate storage database, the outline is created in a pageable format. When you use the Aggregate Storage Outline Conversion Wizard to convert an existing block storage outline to aggregate storage, the outline is automatically converted to a pageable format.
Paging an outline into memory enables Analytic Services to handle very large outlines (for example, 10 million or more members), but potentially increases data retrieval time. You can customize outline paging to obtain the optimum balance between memory usage and data retrieval time.
Outline Paging File
For aggregate storage outlines, the outline file (.otl) is pageable and contains outline data organized in pages of 8192 bytes.
Outline Paging Cache
For aggregate storage outlines, member data resides in pages in the outline (.otl) file. These pages are brought into memory whenever some member information is needed. To maximize performance for outline paging, pages are loaded into the outline paging cache. The outline paging cache uses a 'least recently used' algorithm (LRU), which means pages loaded into the cache to satisfy a member data request remain in the cache until they have to make room for new pages to be brought in.
Page content is organized to provide maximum locality of reference, that is, a good number of a member's siblings are most likely on the same page. Therefore, subsequent requests for the same data or even similar data are executed much more quickly than they would be otherwise.
The default cache size is 8MB and the page size for all supported operating systems is 8192 bytes. Therefore, 1024 pages can be loaded into the cache at any one time.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Optimizing Outline Paging
Modify the OPGCACHESIZE parameter in the essbase.cfg file:
Restart the Analytic Services Server
MAXL> query application ASOsamp get opg_cache statistics;
total_cache_size_gi total_cache_size_by requested_pages_fou
requested_pages_not clean_pages_forced_ current_clean_buffe
OPGCACHESIZE 12280
Presentation Title
Depending on how you want to balance memory usage and data retrieval time, you can customize outline paging for aggregate storage outlines by adjusting the OPGCACHESIZE parameter in the essbase.cfg configuration file.
For very large outlines, performance may be improved by increasing the cache size. To find out if it makes sense to increase the cache you must determine the outline paging cache hit rate (the percent of requested pages that are found in the cache by executing the following MaxL DDL statement:
query application APP-NAME get opg_cache statistics;
If the hit rate is low (<90%), increasing the cache size may improve performance.
To specify the size of the memory cache available to the outline paging feature, edit the OPGCACHESIZE parameter in the essbase.cfg configuration file as follows:
OPGCACHESIZE cachesize, where
cachesize specifies available memory cache size (in kilobytes (KB)). Default: 8,192 KB. Minimum: 1,024 KB. Maximum: 500,000 KB.
Restart the Analytic Services Server to make the configuration change effective.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Compacting the Outline File
Deleting members does not compact the outline file.
You can compact the outline in the Administration Console or MaxL.
2
1
3
Applying Security to ASO Databases
Levels of permissions can be
granted to users and groups
defined at the system, application, or database scope
set for database filters
Defining and executing aggregations requires Calculation (Essbase Administration Services) or Execute (MaxL) permissions or higher
Building dimensions requires Write permissions on the database
© 2004 Hyperion Solutions Corporation. All Rights Reserved.
Presentation Title
The Analytic Services security system speaks to a range of database security needs with a multi layered approach. Security can be applied in the following ways:
Users and groups
Server-wide settings
Database filters
All security permissions for aggregate storage applications are the same as in block storage databases, with the following exceptions:
To define and execute aggregations you need Calculation (Essbase Administration Services) or Execute (MaxL) permissions or higher
Since dimension builds clear the database, it can be performed only by users with Write permissions on the database
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Backing Up Aggregate Storage Applications
To back up an aggregate storage application:
Stop the application
Copy contents of the application directory
Copy the application tablespaces that are not located under the application directory.
ESSCMD command BEGINARCHIVE does not support aggregate storage databases
MaxL statement alter database begin does not support aggregate storage databases
© 2004 Hyperion Solutions Corporation. All Rights Reserved.
Presentation Title
To back up an aggregate storage application, first stop the application. Use the operating system utilities to copy the entire application directory, for example C:\Hyperion\Essbase\app\ASOsamp.
ESSCMD command BEGINARCHIVE does not support aggregate storage databases.
MaxL statement alter database begin does not support aggregate storage databases.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Aggregate Storage Database Statistics
Number of input level cells
Number of aggregate views
Number of aggregated cells
Input level data size
Page size
Temporary disk space allocated and used
© 2004 Hyperion Solutions Corporation. All Rights Reserved.
Presentation Title
The number of bits being used in the key for the dimension.
Each cell in an aggregate storage database is stored as a key/value pair. The key length is 8 bytes or a multiple of 8 bytes; for example, 8, 16, 24.
Each key corresponds to a numeric value in the database. The statistics shown above report key lengths in bytes and the number of bits used per key. How many bits each dimension uses in the dimensional key is shown in the value column for each dimension.
How many bits used in each key may amount to less than the bytes needed for physical storage of the key. As an example where this knowledge might be useful, consider a case in which a key is using 65 bits. If you can reduce the key length by one bit to 64, then you can have then key length be 8 bytes instead of 9, an improvement which reduces the overall size of the database. Another use for these statistics might be to examine them to see how much you gain from removing any particular dimension.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Summary
learned how to:
Optimize outline paging
Identify security considerations
Explain database statistics
Presentation Title
Managing Aggregate Storage Databases
Presentation Title
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Objectives
At the end of this lesson, you should be able to:
Manage tablespaces and storage caches
Optimize outline paging
Identify security considerations
Explain database statistics
Presentation Title
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Tablespace Overview
A tablespace defines database storage in the form of file locations.
Each aggregate storage application has four tablespaces
Default: the database values
Temp: temporary work space
Log: transaction log files
Metadata: the database data structure
A file location specifies a physical disk space for storing database files.
File location 2
Presentation Title
Tablespace describes where and how the files for physical storage can be allocated. Cubes never span tablespaces. Each tablespace may contain one or more file locations. File location is a full path to the directory where the data files will be stored, along with several parameters (max. file size and max. disk space consumption). By having multiple file locations within the same tablespace you can allow a cube to span multiple physical drives or logical volumes.
During both the data load and aggregation process data is being stored in both the Temp and Default directories of an Aggregate Storage database. By using separate physical drives and I/O channels for the location of these files you can reduce I/O contention or bottle necks and therefore improve overall performance. Storing large databases on different physical drives with different I/O channels can also improve query performance.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Specifying Location Properties
Location properties specify
maximum disk space to be used in the directory
maximum file size allowed within the location
Max Disk Size: 200MB
Max File Size: 16MB
File location path
Presentation Title
The Application Servies creates data files named essn.dat in a subdirectory of the file location path, where n is a decimal digit. For instance, if the file location path is C:\ Hyperion\Essbase, the application name is ASOsample, and the tablespace name is default, then the C:\Hyperion\Essbase\ASOsample\default application subdirectory is created when the file location is created, and the data files are put in that subdirectory.
The creation of the file location fails if the application subdirectory already exists or if the file location path does not exist.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Managing Tablespaces
You can manage only the Default and Temp tablespaces by using either
of the two methods:
Presentation Title
Tablespace Manager controls all aspects of retrieving and storing data and works with tablespace definitions to manage the physical disk for data storage and work areas.
When Analytic Services expands a file or adds a file to a tablespace, it will look for space in the first location listed. If there is not enough disk space, the subsequent locations are checked in order. When all space has been used, an error message is returned. When values in a database are cleared, the files in the tablespaces shrink, releasing disk space. When work files are no longer needed, they are deleted and disk space in the tablespace is released. If space is unused, other computer programs can use it.
When an aggregate storage application starts first time, the Analytic Services creates two system tablespaces and adds file location %ARBORPATH%\app to each of them. These tablespaces are “metadata” and “log”. These tablespaces are not user-visible, cannot be changed in any way and are not expected to grow much beyond their initial size (2-8MB each). Additionally, two user-visible tablespaces are created, with names “default” and “temp”. They are initially set to use the same single file location with no file size/disk space limits, but the user can later remove that file location and/or add mode locations. Temporary tablespace is used to store intermediate results during data loads, batch calculations and queries. The “default” tablespace is used to store cube data.
Tablespaces themselves cannot be removed or renamed.
All operations are performed on the file locations within “temp” or “default” tablespaces. File location cannot be removed if there’s already some data loaded into the cube. When you remove a file location, all files created within that file location will be removed, and then the additional subdirectory named “appname\tablespace-name” will be removed as well.
There’s no way to change a path for a file location – one needs to drop it and create a new file location instead. One consequence is that a database cannot be named “default”, ”log”, “metadata” or “temp”.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Aggregate Storage Cache Overview
Essbase allocates an aggregate storage cache, a small area in memory, per application to speed up data loads, aggregations, and retrievals.
The 32 Mb default cache size supports 2Gb of level 0 data.
The cache size is affected by the number of application threads.
Your cache size, in Mb = 32Mb * (Your size of level-0 data, in Gb / 2Gb)
essbase.cfg
Presentation Title
Analytic Services uses the aggregate storage cache to facilitate use of memory during data loads, aggregations, and retrievals. When an aggregate storage application is started, Analytic Services allocates a small area in memory as the aggregate storage cache for the application. As additional cache area is needed, Analytic Services increases the cache size incrementally until the maximum cache size specified for the application is reached or until the operating system denies additional allocations.
In some situations, changing the current setting can optimize use of memory. By default, the cache size is set at 32 MB, the minimum size for the setting. As a general guideline, you can use the size of input-level data to determine when to increase the maximum size for the cache. The size of input-level data is the size of level 0 values.
A 32 MB cache setting supports a database with approximately 2 GB of input-level data. If the input-level data size is greater than 2 GB by some factor, the aggregate storage cache can be increased by the square root of that factor. For example, if the input-level data size is 3 GB (which is 2 GB * 1.5), multiply the aggregate storage cache size of 32 MB by 1.22 (which is approximately the square root of 1.5), and set the aggregate cache size to the result: 39.04 MB.
Another factor to consider is the number of threads set for parallel calculation. Essbase uses multiple threads during the aggregation materialization process. The threads divide up aggregate storage cache. If you increase the number of threads specified in the CALCPARALLEL configuration setting for aggregate storage applications or databases (in aggregate storage databases, performance can be improved by setting the number of threads larger than the number of processors), consider the possible need to increase the size of the aggregate storage cache. Typically increasing the cache by the same factor as the threads should yield good results
The cache is partially allocated at the application startup, and grows on demand later until it reaches the configured limit. Initially, only minimal amount of memory is allocated, and if that fails, the server will refuse to start. That amount is 8MB or 64KB for each server thread, whatever is greater. Note that if the cache size is less than SERVERTHREADS * 64K + 8M, the size is silently increased to that value.
If at some point system refuses to allocate more memory for the cache, the cache size is adjusted down to the current size of the cache.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Viewing the Aggregate Cache Statistics
You can check the following runtime
statistics for the aggregate storage
cache:
Presentation Title
You can view the following aggregate storage run-time statistics under the Run-time node in the Statistics tab of the Database Properties window:
Cache hit ratio: Ratio of the number of requests answered from the aggregate storage cache as opposed to from the hard disk.
Current cache size (KB): The current size of the aggregate storage cache. The aggregate storage cache grows dynamically up to the specified limit.
Current cache size limit (KB): The current setting for the maximum size to which the aggregate storage cache may grow.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Managing the Aggregate Storage Cache
You can change the aggregate cache size limit by using either of the two
methods:
Presentation Title
The maximum size of the aggregate storage cache can be set through two different methods:
In the Administration Services Console
By executing a MaxL DDL statement
To change the size of the aggregate storage cache in the Administration Console:
From Enterprise View or a custom view, select the application.
Right-click and select Edit properties from the pop-up menu.
In the Application Properties window, select the General tab.
Next to the Pending cache size limit node, enter a value, in megabytes, for the size of the cache.
Click Apply.
To change the maximum size of the aggregate storage cache using MaxL DDL to 64MB, you can write the following statement:
alter application ASOSamp set cache_size 64MB;
The cache setting takes effect after the application is restarted
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Outline Paging Overview
Outline pages
8192 bytes
8192 bytes
Presentation Title
Outline Paging
Aggregate storage database outlines are pageable. This feature may significantly reduce memory usage for very large database outlines. For aggregate storage databases, Essbase Analytic Services preloads part of the database outline into memory instead of preloading the entire outline into memory. This allows optimal performance during name lookup that is needed during data load, reporting, spreadsheet and MDX queries. During data retrieval Analytic Services pages other parts of the outline into memory as required. When you create an aggregate storage database, the outline is created in a pageable format. When you use the Aggregate Storage Outline Conversion Wizard to convert an existing block storage outline to aggregate storage, the outline is automatically converted to a pageable format.
Paging an outline into memory enables Analytic Services to handle very large outlines (for example, 10 million or more members), but potentially increases data retrieval time. You can customize outline paging to obtain the optimum balance between memory usage and data retrieval time.
Outline Paging File
For aggregate storage outlines, the outline file (.otl) is pageable and contains outline data organized in pages of 8192 bytes.
Outline Paging Cache
For aggregate storage outlines, member data resides in pages in the outline (.otl) file. These pages are brought into memory whenever some member information is needed. To maximize performance for outline paging, pages are loaded into the outline paging cache. The outline paging cache uses a 'least recently used' algorithm (LRU), which means pages loaded into the cache to satisfy a member data request remain in the cache until they have to make room for new pages to be brought in.
Page content is organized to provide maximum locality of reference, that is, a good number of a member's siblings are most likely on the same page. Therefore, subsequent requests for the same data or even similar data are executed much more quickly than they would be otherwise.
The default cache size is 8MB and the page size for all supported operating systems is 8192 bytes. Therefore, 1024 pages can be loaded into the cache at any one time.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Optimizing Outline Paging
Modify the OPGCACHESIZE parameter in the essbase.cfg file:
Restart the Analytic Services Server
MAXL> query application ASOsamp get opg_cache statistics;
total_cache_size_gi total_cache_size_by requested_pages_fou
requested_pages_not clean_pages_forced_ current_clean_buffe
OPGCACHESIZE 12280
Presentation Title
Depending on how you want to balance memory usage and data retrieval time, you can customize outline paging for aggregate storage outlines by adjusting the OPGCACHESIZE parameter in the essbase.cfg configuration file.
For very large outlines, performance may be improved by increasing the cache size. To find out if it makes sense to increase the cache you must determine the outline paging cache hit rate (the percent of requested pages that are found in the cache by executing the following MaxL DDL statement:
query application APP-NAME get opg_cache statistics;
If the hit rate is low (<90%), increasing the cache size may improve performance.
To specify the size of the memory cache available to the outline paging feature, edit the OPGCACHESIZE parameter in the essbase.cfg configuration file as follows:
OPGCACHESIZE cachesize, where
cachesize specifies available memory cache size (in kilobytes (KB)). Default: 8,192 KB. Minimum: 1,024 KB. Maximum: 500,000 KB.
Restart the Analytic Services Server to make the configuration change effective.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Compacting the Outline File
Deleting members does not compact the outline file.
You can compact the outline in the Administration Console or MaxL.
2
1
3
Applying Security to ASO Databases
Levels of permissions can be
granted to users and groups
defined at the system, application, or database scope
set for database filters
Defining and executing aggregations requires Calculation (Essbase Administration Services) or Execute (MaxL) permissions or higher
Building dimensions requires Write permissions on the database
© 2004 Hyperion Solutions Corporation. All Rights Reserved.
Presentation Title
The Analytic Services security system speaks to a range of database security needs with a multi layered approach. Security can be applied in the following ways:
Users and groups
Server-wide settings
Database filters
All security permissions for aggregate storage applications are the same as in block storage databases, with the following exceptions:
To define and execute aggregations you need Calculation (Essbase Administration Services) or Execute (MaxL) permissions or higher
Since dimension builds clear the database, it can be performed only by users with Write permissions on the database
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Backing Up Aggregate Storage Applications
To back up an aggregate storage application:
Stop the application
Copy contents of the application directory
Copy the application tablespaces that are not located under the application directory.
ESSCMD command BEGINARCHIVE does not support aggregate storage databases
MaxL statement alter database begin does not support aggregate storage databases
© 2004 Hyperion Solutions Corporation. All Rights Reserved.
Presentation Title
To back up an aggregate storage application, first stop the application. Use the operating system utilities to copy the entire application directory, for example C:\Hyperion\Essbase\app\ASOsamp.
ESSCMD command BEGINARCHIVE does not support aggregate storage databases.
MaxL statement alter database begin does not support aggregate storage databases.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Aggregate Storage Database Statistics
Number of input level cells
Number of aggregate views
Number of aggregated cells
Input level data size
Page size
Temporary disk space allocated and used
© 2004 Hyperion Solutions Corporation. All Rights Reserved.
Presentation Title
The number of bits being used in the key for the dimension.
Each cell in an aggregate storage database is stored as a key/value pair. The key length is 8 bytes or a multiple of 8 bytes; for example, 8, 16, 24.
Each key corresponds to a numeric value in the database. The statistics shown above report key lengths in bytes and the number of bits used per key. How many bits each dimension uses in the dimensional key is shown in the value column for each dimension.
How many bits used in each key may amount to less than the bytes needed for physical storage of the key. As an example where this knowledge might be useful, consider a case in which a key is using 65 bits. If you can reduce the key length by one bit to 64, then you can have then key length be 8 bytes instead of 9, an improvement which reduces the overall size of the database. Another use for these statistics might be to examine them to see how much you gain from removing any particular dimension.
Copyright © 2003 HP corporate presentation. All rights reserved.
© 2005 Hyperion Solutions Corporation. All Rights Reserved.
Summary
learned how to:
Optimize outline paging
Identify security considerations
Explain database statistics
Presentation Title