Dr. Stephan Bühne Senior Principal Technical Consultant SAP Solution Center Walldorf

Transcription

1

2 Dr. Stephan Bühne Senior Principal Technical Consultant SAP Solution Center Walldorf

3 Partitioning for SAP R/3 Using partitioning for managing Multi-Client systems

4 Contents Introduction to partitioning technology Challenges on Multi-Client systems Performance O2O support for partitioning setup

5 Contents Introduction to partitioning technology Challenges on Multi-Client systems Benefits for Multi-Client systems Performance O2O support for partitioning setup

6 Non-partitioned table 200, , , , , , , , , , , , , , , , , , , Table partitions Partitioning by client Partitioned Table 100, , , , , , , , , , , , , , Partition Client 100 Partition Client 200 Partition Client 600

7 Table Properties of partitions Index 100, , , , , , , , , , , , , , Partitioning can be used within SAP R/3 No change to application is needed Table definition becomes a Logical object definition Data is stored in partitions Partitions are separate storage objects Partitions can be handled separately Table reorganisations is done on partition level Indexes can be equi-partitioned to the table Index partitions can be reorganised on partition level

8 Contents Challenges on Multi-Client systems Estimating occupied space Reorganisations for different customers SAP Client copies, SAP system merges Removing unneeded clients

9 Data distribution within the Table 100,'ABCDE',' ,'ABCDE',' ,'AHJDE',' ,'TZWER',' ,'FDGDE',' ,'DFGGV',' ,'AGFHG,' ,'ADFGS',' ,'ARETW',' ,'ATZUTR','... database Tablespace Datafiles

10 Estimating occupied space Customer question: How much space is used???? Client 100 Client 200 Client 600 I can't believe that we are using so much space...

11 Estimating occupied space Size for different clients can not be estimated accurately within the database Difficulties calculating used space for different customers within the database. Ongoing discussions with customers about space, money, time and reorganisation

12 Situation with partitioning Challenges on Multi-Client systems Estimating occupied space Reorganisations for different customers SAP Client copies, SAP system merges Removing unneeded clients

13 Data distribution within the database Table partitions Tablespaces Datafiles 100, PSAP , , , , , PSAP , , , , , , , , PSAP600

14 Estimating occupied space Customer question: How much space is used? 250G 750G 150G Client 100 Client 200 Client 600 I can't believe that we are using so much space... No problem, I can show you...

15 Advantages partitioning for size estimation Partitions can be placed in own tablespaces Table- and Indexpartitions belonging to the same client can be placed in the same tablespace Tablespace size directly reflects the amount of data used for each client Storage usage becomes transparent for customers and hoster

16 Contents Challenges on Multi-Client systems Estimating occupied space Reorganisation for different customers SAP Client copies, SAP system merges Removing unneeded clients

17 Table reorganisation Table 200, , , , , , , , , , , , , , , , , , , Index 0 Data Client 100, Client 200, Client 600 Index 1 Data Client 100, Client 200, Client 600 Index 2 Data Client 100, Client 200, Client 600

18 Reorganisations Reoganisations can not be managed client independent Reorganisation of one client affects always all other clients (have to be reorganisized too) Finding a downtime for all clients simultaneosly

19 Situation with partitioning Challenges on Multi-Client systems Estimating occupied space Reorganisations for different customers SAP Client copies, SAP system merges Removing old clients

20 Managing single partitions Table Partitions Client , Index 0 Index 1 Index 2 Index Client 100 Index-Partitions Client 100 Index Client 100 Index Client 100 Table Partitions Client , , , , , Index Client 200 Index-Partitions Client 200 Index Client 200 Index Client 200 Table Partitions Client , , , , , , , , Index Client 600 Index-Partitions Client 600 Index Client 600 Index Client 600

21 Managing single partitions Tablepartitions Reorganisation Commands 100, Drop partition - Merge partition - Split partition - Rebuild partition - Move partition - Shrink partition Indexpartitions Rebuild partition (Online/ Offline)

22 Advantages partitioning for reorganisation Partitions can be reorganised independently from each other Reorganisations can be done on a client based level, instead of datbase level Only downtime (if ever) for one client is needed System availability (SLA) is increased

23 Contents Challenges on Multi-Client systems Estimating occupied space Reorganisation for different customers SAP Client copies, SAP system merges Removing unneeded clients

24 Table partitions Partitioned Table Partition Client , , , , , , , , Split partition 300, , , , , , ,copy data 600, , , , , , , , New Partition Client 300 Partition Client 600

25 Contents Challenges on Multi-Client systems Estimating occupied space Reorganisation for different customers SAP Client copies, SAP system merges Removing unneeded clients

26 Table partitions Drop partition 300, , , , , , Partition Client , , , , , , , , Partition Client 600

27 Partitioning advantages Partitions can be added or removed on demand Removing single clients will free up disk space immediately No reorganisations needed Can also be used for Merging SAP systems

28 Contents Introduction to partitioning technology Challenges on Multi-Client systems Performance O2O support for partitioning setup

29 Performance enhancements Database uses Partitioning pruning, to eleminate unused partitions Table are joind on single partitions instead of the whole table Index access on tables can be parallized when partitioned indexes are used

30 Test results runtime/min Table > 1 Billion rows Size appr. 150 GB Query: Select count(*) from.. where budat between ' ' and ' ' Counts the number of rows of one month in the table :20 Unpartitioned 00:41 Partitioned

31 Results EKx-Tables Laufzeit 06:36:00 06:00:00 05:24:00 04:48:00 04:12:00 03:36:00 03:00:00 02:24:00 01:48:00 01:12:00 00:36:00 Laufzeiten 03:15:15 00:49:28 00:00:00 Zeile 7 Zeile 8 Zeile 9 Zeile 10 Zeile 11 Zeile 12 Zeile 13 Zeile 14 Queries

32 Results List-Partitioning Results List-Partitioning 00:05:46 00:05:24 00:05:02 00:04:41 00:04:19 00:03:58 00:03:36 00:03:14 00:02:53 00:02:31 00:02:10 00:01:48 00:01:26 00:01:05 00:00:43 00:00:22 00:00:00 Zeile 10 Zeile 11 Zeile 12 Zeile 13

33 Results EKx-Tables Results Tables Rows Größe (GB) Number of Rows Unpartitioned Partitioned (PQ4) Partitioned no PQ Query :15:15 00:49:28 03:14:03 EKKO Query :09:17 00:15:55 00:31:41 EKPO Query :21:53 00:45:25 03:12:39 EKET Query :34:49 00:38:44 EKES Query 4_ :29:52 00:02:58 00:16:02 Query Nicht beendet 01:03:39 Query :32:54 00:09:53 01:08:58 Query :09:52 00:02:31 00:07:48 Query :11:29 00:09:42 00:10:27

34 Contents Introduction to partitioning technology Challenges on Multi-Client systems Performance O2O support for partitioning setup

35 O2O Support Oracle-to-Oracle migration and reorganisation service Fastest method for complete or partial database reorganisations Top speed actual: 545 GB/h, calculated on database size Includes support for partitioning setup Tables become partitioned during reorganisation

36 Conclusions Partitioning is the optimal technique for managing multi client systems Different clients can be administered independently Increases transparency for customer and hoster Lowers adminstrational costs, in respect to reorganisations Increases system availability (SLA)

37 Q & A

38 Contact Dr. Stephan Bühne SAP Solution Center Walldorf

39