From what I've seen you might include things like: Increased reliability/24x7 accessibility RAC Dataguard More efficient use of resources SAN Grid :) The key being ways in which the technology will support the company either in becoming more efficient, being available more often, saving money, etc. Jay Miller -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jared Still Sent: Friday, March 04, 2005 11:47 AM To: Oracle-L Freelists Subject: All good things .... ... come to those who wait. My manager has informed me that he would like me to take on a role as a database architect rather than 'just' as a DBA. Good news for me, as that is what I was hired to do at another job about 52 months ago. Too bad it was at Enron Broadband Services. But that's not exactly why I am writing here. One of the tasks in this capacity is to develop a database roadmap for our company. Where the technology is going, how we should exploit it, etc. As this is something I have not previously done, I was wondering if anyone has or knows of examples they can share. It would be nice to see what is typically expected (or not expected) with this type of a document. I'm not looking too plagiarize, but just get a better feel for this type of document, what level of detail it may or may not provide, that sort of thing. I have googled for it, but couldn't come up with anything useful. Thanks, -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l