Charles Severance

All results of the database tuning are reflected in the out of the box Sakai release. All the rewritten queries, and correct indexes are present in the release DDL.

BUT (there is always a but), the work inside of Oracle is very Oracle version specific and since the tuning is done by DBAs (not in SVN). These changes are often Oracle parameters like how big is the ZZZ buffer pool. What we find is that type of Oracle information is best communicated from DBA to DBA and not DBA to Developer.

Also at UM, we are effectively a continuous test bed so simply taking the in-Oracle stuff from UM might get a bunch of cruft.

What has worked in this case is that each institution has their own DBA's who take a fresh look at the tables, queries, and indexes and figure things out. Once they get familiar with things the local DBA will know enough to have some short conversations with other site's DBAs.

So the recommendation is not to just drop this on a developer team. If you are going to drop this on the developer team, then someone on the team needs to become a junior DBA - go to some Oracle training for tuning, buy some Oracle books, etc.

It would be nice for this to be turn-Key (and for 7-8K users, it is pretty much turnkey) but to run 50K - 100K users you need to bring some talent to bear.

If you are running a pilot, you can amortize some of this talent acqusistion. this is a good reason to run a pilot rather than running 100K on day one.