OEM or lots of code?

Folks... I'm writing the 11g New Features book right now (It's up on Amazon for pre-sales, so I'm told I can mention the book, but I can't talk about 11g, so please don't ask). As I'm writing I find that I'm in a bit of a quandary, so I thought I'd ask you what your preference is.

If you have used some of the Advisor features in 10g, for example, you know that there are pretty easy to use OEM interfaces into the advisors, and there is the rather long, involved use of various supplied packages available that allow you to run the advisors.

In this new book, I'm considering biasing my coverage to OEM for a few reasons:

1. OEM is less complex to use.
2. Adding coverage for both will take up many more pages. When you are writing a book you are limited to a page count range, so depth is limited based on this too.
3. The Code route, in and of itself, can be complex. I'm not sure if it's worth the extra time to add the code in some cases just because of this complexity.

I'm wondering if anyone who has used these features or suspect they will use them in the future has a preference. In some cases, if page count allows, I'll do both. In some cases I need to select either/or due to page count considerations. In the past, I've been very heavily code oriented and really relegated OEM to the background, but now I'm thinking of moving in the other direction.

Thoughts??

RF

Robert G. Freeman
Oracle Consultant/DBA/Author
Principal Engineer/Team Manager
The Church of Jesus Christ of Latter-Day Saints Father of Five, Husband of One,
Author of various geeky computer titles
from Osborne/McGraw Hill (Oracle Press)
Oracle Database 11g New Features Now Available for Pre-sales on Amazon.com! Sig V1.1

--
http://www.freelists.org/webpage/oracle-l