From: "Andrew Gayter" <[EMAIL PROTECTED]>
For example - developers cannot write efficient SQL statements without an integral knowledge of how the DB will optimize the query and which indexes have been set up. A good DBA will know this and be able to create SPs which are efficient and work correctly.
I know that our team of developers has learned an awful lot about databases in the last ten years -- and despite having created a heavily database-oriented system that keeps most of its business logic in stored procedures, it took easily four years of trial-and-error learning to get to 90% of our current proficiency. When I look back at some early and not-so-early decisions we made, or code we wrote, I just have to cringe. Unless you have time for that kind of learning curve, I suggest getting a DBA and doing everything you can to learn from her. ...and I believe that the "A" in DBA traditionally stands for "Analyst" and not "Administrator". -- Curt Hagenlocher [EMAIL PROTECTED] =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
