1. New Generation of OpenEdge ® RDBMS Advanced Storage Architecture II Tomáš Kučera Principal Solution Engineer / EMEA Power Team

2. © 2007 Progress Software Corporation2 > whoami  Started with Progress Software Czech Republic – Dec 19, 1994  2 years @ Technical Support (1996 at ETSC)  Since Dec 1996 – Consultant, Presales, Trainer, Project Manager  Currently – GFS Mgmt responsibilities for Cze&Pol, member of the EMEA Power Team – primary responsibility for SAND  Product Areas: OpenEdge, Sonic, some Apama and Actional  Contact: tku@progress.com, Skype: tomas_kucera TKU

3. © 2007 Progress Software Corporation3 Audience Survey ReleaseWhenAge 7.2Along agoancient 8.2Along agoancient 8.3Along agoancient 9.0ADec 1998over 8 years 9.1ADec 1999over 7 years 10.0ADec 2004over 2 years 10.1AJan 2006over 1 year 10.1BJan 20073 months

4. © 2007 Progress Software Corporation4 Audience Survey ReleaseWhenAge 7.2Along agoancient 8.2Along agoancient 8.3Along agoancient 9.0ADec 1998over 8 years 9.1ADec 1999over 7 years 10.0ADec 2004over 2 years 10.1AJan 2006over 1 year 10.1BJan 20073 months

5. © 2007 Progress Software Corporation5 Agenda  Summary of Advanced Storage Architecture  Advanced Storage Architecture II  Migrating to ASA II  Bonus

6. © 2007 Progress Software Corporation6 What‘s Advanced Storage Architecture II  ASA I Implemented in Progress V9 Data Storage Areas RECID unique per area  ASA II Implemented in OpenEdge 10 A brand new space allocation mechanism RECID unique per area and object block  OE10 RDBMS can have objects from both ASAI&II Summary

7. © 2007 Progress Software Corporation7 Agenda  Summary of Advanced Storage Architecture  Advanced Storage Architecture II  Migrating to ASA II

8. © 2007 Progress Software Corporation8 Advanced Storage Architecture II  Data Clusters  Database „Objects“  Storage Area Type II What‘s in the box?

9. © 2007 Progress Software Corporation9 Data Clusters  A group of 8 or more adjacent blocks – fixed size for area  A unit of space allocation for objects  A unit of space allocation for extents  All blocks in cluster belong to same object  Entire cluster can be read in a single IO operation

10. © 2007 Progress Software Corporation10 Database „Objects“  Composed of one or more clusters  Object types: Table Index Sequence generators Large objects: binary - BLOB, character - CLOB, character – XML Empty

11. © 2007 Progress Software Corporation11 Storage Area Type II  Data Storage Area is made up of one or more extents and contains one or more database objects  Extent contains one or more data clusters  Data clusters have fixed size of 8, 64 or 512 database blocks and are unit of space allocation  Blocks in a cluster are contiguous and belong to the same database object

12. © 2007 Progress Software Corporation12 Areas, Extents, Clusters, Blocks Area root cluster A Table An Index Another Table Free clusters Empty clusters Extent header Free blocks Extent 1 Extent 0 Area cl 0 cl 1 cl 2 cl 3 cl 4 cl 5 cl 6 cl 7 cl 8 cl 9 cl 10 cl 11 cl 12 cl 13 cl 14 cl 15

13. © 2007 Progress Software Corporation13 New Database Block Types Block TypeContents Extent HeaderExtent type, current extent size, maximum extent size, cluster size, area id, block size, control file name Area Rootcluster size, link to free cluster map cluster highwater mark Free Cluster Mapbitmap of clusters in use or free, next and prev links Object Listlist of object id’s and their root cluster id’s Object Rootobject id, object type, link to free map, link to row space map Cluster Listlist of clusters belonging to an object

14. © 2007 Progress Software Corporation14 ASA Performance FeatureBenefit Unnecessary elimination of table and index fragmentation Reduced need for data reorganization providing less frequent and shorter downtimes Allocated space for objects in contiguous chunks that can be read (and written) using large i/o operations Enhanced overall performance Better utilization of available disk bandwidth Enhanced overall database i/o performance Enhanced maintenance utility performance for “bulk” operations Full object scans possibleEnhanced online application performance

15. © 2007 Progress Software Corporation15 Agenda  Summary of Advanced Storage Architecture  Advanced Storage Architecture II  Migrating to ASA II

16. © 2007 Progress Software Corporation16 Migrating to ASA II  Backup your database  Keep dbanalys & promon data for reference  Install OpenEdge 10 (no need to delete / overwrite Progress V9)  Upgrade database to OE10  Run UPDATE STATISTICS for SQL  Backup your database again!  Recompile application code  Ready... Steady... GO!!! General Upgrade Strategy

17. © 2007 Progress Software Corporation17 Migrating to ASA II  Backup your database  Keep dbanalys & promon data for reference  Install OpenEdge 10 (no need to delete / overwrite Progress V9)  Upgrade database to OE10  Run UPDATE STATISTICS for SQL  Backup your database again!  Recompile application code  Ready... Steady... GO!!! General Upgrade Strategy

18. © 2007 Progress Software Corporation18 Upgrading Database to OpenEdge 10  The 5-Minute Rule  We Want More Rule You have a choice

19. © 2007 Progress Software Corporation19 Upgrading Database to OpenEdge 10  proutil -C conv910 -B 512  Conversion utility runs in place, in 5 minutes or less  Mostly we upgrade the schema tables  No changes to records or indexes  No changes to physical structures The 5-Minute Rule

20. © 2007 Progress Software Corporation20 Upgrading Database to OpenEdge 10  Pros: It is extremely quick and easy You can run the database It will very likely run better than before Most of your DBA scripts should work fine  Cons: Fragmentation may still exist All data in Type I data storage areas The 5-Minute Rule

21. © 2007 Progress Software Corporation21 Upgrading Database to OpenEdge 10  Do some more work – move data to Data Storage Areas Type II  Upgrade with conv910 utility  Move schema tables  Create Data Storage Areas Type II  Move tables and indexes  Truncate old data storage areas  Delete old data storage areas We Want More Rule

22. © 2007 Progress Software Corporation22 Upgrading Database to OpenEdge 10  Moving schema tables proutil -C mvsch Renumbers existing schema area Creates new schema area #6 Copies schema tables Deletes old schema tables We Want More Rule

23. © 2007 Progress Software Corporation23 Upgrading Database to OpenEdge 10  Create Data Storage Areas Type II prostrct add Use database block size 4K or 8K BI & AI block size should match each other Type II Data Storage Area Cluster sizes: –Tables areas: 512 –Index areas: 512 Note: D&L required to change database block size We Want More Rule

24. © 2007 Progress Software Corporation24 Upgrading Database to OpenEdge 10  Moving tables and indexes proutil -C tablemove | idxmove Can move just table, or table and its indexes We Want More Rule

25. © 2007 Progress Software Corporation25 Upgrading Database to OpenEdge 10  Truncate and delete old data storage areas proutil -C truncate bi proutil -C truncate area After that data storage area is logically truncated and its extents can now be removed prostrct remove We Want More Rule

26. © 2007 Progress Software Corporation26 Upgrading Database to OpenEdge 10  If you don‘t like this approach, you still can do the famous Dump & Load  You will have to do it if you are changing database block size  D&L options: Dictionary D&L Custom D&L Custom BUFFER-COPY Binary D&L We Want More Rule

27. © 2007 Progress Software Corporation27 Agenda  Summary of Advanced Storage Architecture  Advanced Storage Architecture II  Migrating to ASA II  Bonus

28. © 2007 Progress Software Corporation28 What‘s new in OpenEdge 10.1B  Implemented INT64 data type  64-bit Database Keys – applies to Data Storage Areas Type II only Removes 2 billion row limit – pushed to more than 9 quintillion ROWID format has to have 8 additional characters (0x0000000000000000)  Database Limits pushed farther again 31994 areas * 1 petabyte per area = ~32 exabytes of data Summary

29. © 2007 Progress Software Corporation29 What‘s new in OpenEdge 10.1B  64-bit Sequences  Large Index Key Entries Removes ~192 byte limit Allows ~1970 bytes of user data  1000 Area Limit 32000 areas assumed Can be restricted by using -maxAreas startup parameter Summary

30. © 2007 Progress Software Corporation30 What‘s new in OpenEdge 10.1B  proutil -C describe  proutil -C enableseq64  proutil -C enablelargekeys  proutil -C updatevst  proutil -C revert Summary

31. © 2007 Progress Software Corporation31 What‘s new in OpenEdge 10.1B  Shared memory segment size on 32-bit platforms Summary Shared Memory2GB Max shmsegsize128MB Max #Segments21 Shared Memory4GB Max shmsegsize4GB #Segments32 Prior 10.1B 10.1B

32. © 2007 Progress Software Corporation32 What‘s new in OpenEdge 10.1B  Enable After-Imaging Online probkup online enableai AI files must already exist (but can be added online too!) Online backup used as basis for roll-forward AI writers and replication must be enabled manually  Enable AI Online with AI Management Summary

33. © 2007 Progress Software Corporation33 Question? Tomáš Kučera tku@progress.com Skype: tomas_kucera

34. © 2007 Progress Software Corporation34