Criteria for handoff from development

From: DENNIS WILLIAMS <DWILLIAMS_at_LIFETOUCH.COM>
Date: Fri, 04 Jan 2002 12:24:12 -0800
Message-ID: <F001.003E7438.20020104114521@fatcity.com>

Can anyone provide some criteria of what you look for when a data model is handed off from production? We are starting a large development project and I lobbied management to hire a data architect. As they have talked to these people, they are getting statements such as "and then the DBA will check out the data model to make sure there won't be any performance problems". I am concerned about what will be expected of me and wondered how other DBAs handle this situation. What do you look for in a model in terms of making sure the performance will be good? I said that I could look at the queries that would be run to see how many tables would need to be joined to retrieve the data, but the manager replied that a good DBA wouldn't need to see the queries, should just be able to look at the model. Up until this point, our client-server design tools have tended to protect the developers from doing dumb stuff, but now in the Java world some of those safeguards.

Dennis Williams
DBA
Lifetouch, Inc.
dwilliams_at_lifetouch.com

--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: DENNIS WILLIAMS
  INET: DWILLIAMS_at_LIFETOUCH.COM

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Fri Jan 04 2002 - 14:24:12 CST