Table Partitioning in SAP


When tables grow large, queries on the table will be slow. Index range scans, table scans, backups and restores will be slow. The most common characteristic of such tables is that the older entries in the table are seldom changed and updates happen on the newer entries. By partitioning the table, the older entries can be maintained in a seperate partion, thereby increasing performance--looking up for query results in a smaller set of data, parallel processing in different partitions, faster backups etc.

Types of Partitions:
  1. Range Partition: This allows you to partition data by range of values. Example: 1st partition by column Date: Jan 01 2000 - Dec 31 2005; 2nd partition by column Date: Jan 01 2006 - Dec 31 2010 and 3rd partition by column Date: Jan 01 2011 - Dec 31 2015.
  2. List Partition: This allows you to maintain a list of values that constitute a partition. Ex: 1st partition by Plant: 5000; 2nd partition by Plant:6000.
  3. Hash Partition: A hash algorithm is used to distribute data into different partitions.
  4. Combined Partition: A combination of above three partitions to create partitions and sub-partitions. 

To partition a table in SAP:
  1. Call transaction SE14
  2. Enter the table to be partitioned and click on Edit
  3. Click on Storage Parameters
  4. Click on For new creation
  5. Place the cursor on Table and click Create parameter values (second button) in the toolbar
  6. Choose a template for the parameter values (ex: Current database parameters)
  7. Place the cursor on PARTITION BY and press F4 to select the partitioning method.
  8. Depending on the partition method you choose, some more parameters will populate. You can enter one or more values for these parameters. The values are dependent on the data type and are case-sensitive.
  9. Save the changes
  10. Choose Activate and adjust database to create partitions
If you are interested in learning more about SAP performance, SAP Performance Optimization Guide by Thomas Schneider is a great book.

Comments

Post a Comment

Popular posts from this blog

OS/DB Migration - CMD. STR, TOC, EXT, R3load, DDLDBS.TPL and more

Image
With increasing need to improve performance or reduce costs or vanishing support for operating systems/databases it becomes inevitable to migrate to a better OS or DB. We feel take a quick look at the primary ingredients of the tools for OS/DB migration handled by R3SETUP. Tools - R3load, R3ldctl and R3szchk R3ldctl creates STRucture files, TemPLate files by reading the technical settings for table/indexes in SAP data dictionary. R3szchk calculates the database size object sizes (EXTent files) for the target system based on the STR files created by R3ldctl. The EXT and STR files can be later split into smaller groups. The most crucial tool R3load is responsible for unloading and loading data from the database. R3load uses the files created by R3ldctl and R3szchk and dumps the data into compressed binary format as .001, .002 .. files. It uses cmd files to achieve the task. If the cmd files are not present, it creates on its own. Files Command files*.cmd  are creat...
Read more

Fixing Inconsistent Table - Table activation fails due to inconsistency between DD and DB

If you find a table to be available on the database, but not active in ABAP dictionary, try calling SE14 as DDIC user, enter the table name and choose Table > Reconstruct, Execute. If this method fails follow these steps: Call transaction code SE37 and execute the function module  DD_TABL_ACTM with single test On the next screen, do not change any other field except the following and set them as shown below: MODE: 12 NTAB_PUTSTATE: N TABNAME: <enter the correct table name> Click on Execute The export parameter ACT_RESULT should show 0. To verify if the inconsistency is fixed, call transaction SE14 > Extras > Database Object > Check and  SE14 > Extras > Runtime object > Check.
Read more

301 Redirect Using SAP Web Dispatcher

301 redirects are typically used to redirect accesses that include www to non-www or vice-versa. Example, when you call http://blogger.com, the call is redirected to www.blogger.com. An end-user may prefer to call a URL in any manner. You must ensure that all these calls are redirected to relevant URLs with content. SAP web dispatcher can be configured to send a redirect (301) to the client. To enable redirection add icm/HTTP/redirect_<xx> to the web dispatcher's profile file. The parameter uses the following syntax: icm/HTTP/redirect_<xx> = PREFIX=<URL prefix>[, FROM=<pattern for URL>, FROMPROT=<incoming protocol>, FOR=<pattern for host name:port>,TO=<new URL prefix>, PROT=<protocol>, HOST=<host>, PORT=<port number/name>] Let's say you want to redirect all the HTTP requests on mysource.com on 80 port to mytarget.com on HTTPS 443 port icm/HTTP/redirect_0 = PREFIX=/, FROM=*, FROMPROT=http, FOR=mysource.com:80,...
Read more