By Phil Grainger, BMC UK
During the design of a DB2 application, there is now a lot more to consider than just “what should the tables look like”. We need to take into consideration where we should create indexes, and why. We might think about partitioning for performance or for manageability. What about partitioned and non partitioned indexes – they each have their advantages and disadvantages. More recently, we’ve been given the option to create Materialized Query Tables, but when would these be good to use?
This presentation steps through some of the new (and not so new) elements of DB2 database design and highlights pros and cons of each
Unfortunately, as with a lot of DB2 decisions, there are no absolute correct answers – the right answer in your case will always “depend” on circumstances, but hopefully this presentation will give you the information you need to make informed choices
Phil has over 20 years experience of DB2, starting work all those years ago in 1987 with DB2 Version 1.2. Since then he has worked with all versions, including DB2 10
From his beginnings as a DB2 DBA for one of the largest users of DB2 at that time in the UK, through his time at PLATINUM technology and including almost 10 years as Senior Principal Product Manager for CAs line of DB2 solutions, Phil has always been a keen supporter of user groups and is a regular speaker at both vendor sponsored and independent events. His work with IDUG includes being a past member of the European IDUG Planning Committee, an inductee into the IDUG Volunteer Hall of Fame and now Board Liaison for BMC Software
Phils focus as Senior Principal Product Manager for DB2 tools at CA was with an international view as to the usage of DB2
In 2009, 2010, 2011 and 2012, Phil was honoured by IBM as an Information Champion
Phils is now at BMC Software working as their Lead Product Manager in support of their DB2 tools portfolio
In addition, Phil is a regular contributor to the IDUG sponsored DB2-L discussion list