Sorry about that. We have 7 "production/run" DBAs and 6 "plan/build" DBAs on the infrastructure side, and around 50+ application DBAs with some others that wear the developer & application DBA hats simultaneously. The "run" infrastructure DBAs have some overlap, as some applications have no application DBA support at all. The DB2, SQL Server & DB2/UDB databases are supported by DBAs dedicated to those engines. We do have good monitoring/availability tools and an excellent selection of tuning tools. "Freeman, Donald" <dofreeman@xxxxxxxxxxx> Sent by: oracle-l-bounce@xxxxxxxxxxxxx 04/02/2009 02:25 PM Please respond to dofreeman@xxxxxxxxxxx From "Freeman, Donald" <dofreeman@xxxxxxxxxxx> To "'DEEDSD@xxxxxxxxxxxxxx'" <DEEDSD@xxxxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx> cc Subject RE: survey - DBA structure in your company ? The thing missing in your post is how many DBA's you have for 650 databases and another issue would be what/how many tools you have. We have 4 dba's and a dba manager here. The dba's are assigned a certain number of applications (128 total) to support, both SQL and Oracle, and perform whatever tasks pertain to that. We overlap and cross train enough to maintain at least a minimum proficiency in our "weak" database technology and application knowledge. . Donald Freeman Database Administrator II Commonwealth of Pennsylvania Department of Health Bureau of Information Technology 2150 Herr Street Harrisburg, PA 17103 From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of DEEDSD@xxxxxxxxxxxxxx Sent: Thursday, April 02, 2009 1:52 PM To: oracle-l@xxxxxxxxxxxxx Subject: survey - DBA structure in your company ? We are a reasonably large corporation, with 650 Oracle databases. We are having a bit of internal discussion going on concerning different support models: (1) Having separation of duties for DBAs: one DBA area in responsible for infrastructure across all databases and another group doing application DBA work across multiple application databases, closer to the applications and their data or (2) Doing DBA work in silos: one DBA would be responsible for a certain set of applications and databases end-to-end, responsible for all infrastructure and application data work for that set of applications We currently have a structure like this: We have systems DBAs that are responsible for the database infrastructure - installing the server software & patching, tuning at the instance level, monitoring db server capacity, backup & recovery, adding sizing datafiles, disaster recovery, database creation, user & security administration, 24x7 level 3 support. We have application DBAs that are closer to the application data, and are responsible for creating and maintaining the application schema objects (tables, indexes, etc), some SQL statement tuning, logical backups (exp/imp) of application objects, data loads, 24x7 level 2 support. I am curious what other folks are doing. -- //www.freelists.org/webpage/oracle-l