Steps to create replicated Partitions in EssBase

Steps to create replicated Partitions :

• take any existing database. EX sales(source database )
• create another application sale part and create a database under that application .
• open sales 1 outline and select save as click analytical server tab and selepart application , select the database sale part and replace the file. Now sale part and sales 1 outlines are same
• in this example we are going to a Partition to replicate only year 2007 data into salepart cube .
• right click on Partition under sales 1 or salepart . by default the replicated Partition type is replicated . click connection tab. Select source as sales 1 , select the server . select salepart as target and select the server . click on “double click here” under source and select appropriate dimension . in this example select year 2007 . under target also select year 2007 .
• click validate . replication Partition is created .
• right click on the target or source and click on replicate data from source

• we can load data only in level zero members .
• when a member in the outline is changed ,data will be lost . we need to reload the data
• Time balance and dynamic time series functions are not available .
• Write back option is not available in ASO cubes
• Only one database can be created per one application
• We can convert BSO to ASO , but other way not possible .
• There is no option to export the ASO data . to backup the cube , we need to copy the entire folder .
• Two-pass CALC can be achieved using solve order in ASO the solve order is 0 by default . while aggregating the cube , analytic service calculates the formulas with solve order 0 first and then solve order 1 etc .
• There are three type of hierarchies available in ASO.store , dynamic and multiple hierarchies
• stored hierarchies   cannot have formulas or shared members . also shared hierarchies can contain only+ and ~ symbols on member
• a dynamic hierarchy can contain any of the consolidation properties.
• Multiple hierarchy contains both stored and dynamic hierarch stored hierarchies should come first . a shared hierarchy present in multiple hierarchy can contain formulas and shared members .