To increase application response time, you want to divide the transactions in a high-volume general ledger application module so that application users can query specific segments. You decide to create segments based on calendar year. In the Enterprise Data Manager you create a time dimension that you configure as a date range. Then you create a general ledger segmentation group that contains related general ledger tables. In the Data Archive user interface you create a data classification and configure the dimension slices to create segments for all general ledger transactions by year, from 2010 through the current year, 2013.

When you run the segmentation policy, the ILM Engine divides each table across the general ledger segmentation group based on the dimension slices you defined. The ILM Engine creates four segments, one for each year of general ledger transactions from 2010-2012, plus a default segment. The default segment contains transactions from the current year, 2013, plus transactions that do not meet business rule requirements for the other segments. As users enter new transactions in the general ledger, the application inserts the transactions in the default segment where they remain until you move them to another segment or create a new default segment.

After you create segments, you create and apply access policies to the segmentation group. The default access policy you apply allows all users and programs access to one year of application data. You create another access policy for business analysts who need access to all four years of application data. The access policy you create for the business analysts overrides the default policy.