Database Design
Posted in 2000
Topics: Server Administration, Security, Permissions & Auditing, Triggers, Constraints & Referential Integrity
Hi everyone I would ask a very general question about DBA role here. I am not quite sure what is exactly DBA's job regarding database design. Is there any cut edge between jobs of business analyst , programmer and DBA? Most topics covered here are about informix database itself. Giving a new project from beginning, what will a DBA start with? Involving business analysis? Creating databse, tables, primary key, foreign key, constraint and index? Thanks in advance. Regards Andy Jiang
Depends on where you work. For instance, where I work, the business analyst tells the programmer what needs to be accomplished. The programmer tells the dba what kind of data needs to be stored, and the dba tells the programmer how the tables will be set up. Any changes after the initial design are discussed between the programmer and business analyst. Your own structure may differ greatly. PS, this was an abridged version of the process! :) Andy Jiang wrote: > Hi everyone > > I would ask a very general question about DBA role here. > > I am not quite sure what is exactly DBA's job regarding database design. Is > there any cut edge between jobs of business analyst , programmer and DBA? > Most topics covered here are about informix database itself. > > Giving a new project from beginning, what will a DBA start with? Involving > business analysis? Creating databse, tables, primary key, foreign key, > constraint and index? > > Thanks in advance. > > Regards > > Andy Jiang
Hi, I would guess that as the DBA you should be designing the database with input from the other two! You should be putting in the majority of the design input as you will be the person who looks after the database long after the others have run for the hills! But then again, this is just my humble opinion! See Ya IV "Andy Jiang" <ajiang@mail.lumley.co.nz> wrote in message news:MjAq5.1278$eZ8a.6357484@news.xtra.co.nz... > Hi everyone > > I would ask a very general question about DBA role here. > > I am not quite sure what is exactly DBA's job regarding database design. Is > there any cut edge between jobs of business analyst , programmer and DBA? > Most topics covered here are about informix database itself. > > Giving a new project from beginning, what will a DBA start with? Involving > business analysis? Creating databse, tables, primary key, foreign key, > constraint and index? > > Thanks in advance. > > Regards > > Andy Jiang > >
Ian Vellosa wrote: > > Hi, > > I would guess that as the DBA you should be designing the database with > input from the other two! You should be putting in the majority of the > design input as you will be the person who looks after the database long > after the others have run for the hills! > > But then again, this is just my humble opinion! > > See Ya > IV > > "Andy Jiang" <ajiang@mail.lumley.co.nz> wrote in message > news:MjAq5.1278$eZ8a.6357484@news.xtra.co.nz... > > Hi everyone > > > > I would ask a very general question about DBA role here. > > > > I am not quite sure what is exactly DBA's job regarding database design. > Is > > there any cut edge between jobs of business analyst , programmer and DBA? > > Most topics covered here are about informix database itself. > > > > Giving a new project from beginning, what will a DBA start with? Involving > > business analysis? Creating databse, tables, primary key, foreign key, > > constraint and index? When I was a programmer I used to think: the DBA should worry about the server and leave my schemas alone. Then I became the DBA and tried to implement my laisez faire philosophy. The result is a massive profusion of databases, tables unrelated to each other in the same database, critical databases that should be dependent on referential integrity with none, databases that cannot be kept in sync across two servers because they use serial keys and are updated separately, applications dependent on closely related data in three databases that are maintained separately, etc. It is a DBA's nightmare. In my next life I will be a hardass and design all of the databases myself! Take a lesson. Art S. Kagel
"Art S. Kagel" <kagel@bloomberg.net> writes: > In my next life I will be a hardass and design all of > the databases myself! Take a lesson. The toughest one of all: if you want something done right, you have to do it yourself. -- Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412 Ronald Cole <ronald@forte-intl.com> Phone: (760) 499-9142 President, CEO Fax: (760) 499-9152 My GPG fingerprint: C3AF 4BE9 BEA6 F1C2 B084 4A88 8851 E6C8 69E3 B00B