> On 22-Jun-2004 00:27:06, Tim Ledgerwood wrote:
> So - in my experience, IB/FB requires NO dba. At absolute worst, it
> requires that I (once in a very long while indeed) provide remote
> telephonic support. It is powerful, simple, and easy to use. I think that
> some of the argument is based on the reasoning "it's a server DB, and
> therefore requires a DBA because server DBs require DBAs"

Tim, thanks for posting this. To me, this is priceless information. I was
also concerned when I read Dmitry (sp?) reply on this, because I am
converting an application that was written in a proprietary relational
database management system over to Delphi/Firebird and the previous
application never required a DBA to run it. I have worked on sites with
various different SQL engines installed, and normally if an application is
written correctly, it shouldn't require a DBA for any task other than
monitoring that the backups are done correctly and regularly. For the most
part, this can be scripted anyway. At least I'm speaking from a Vertical
Market Application perspective where tech support/DBA requirements eat
directly into the profitability of the application in the marketplace.

I was hoping you could expand upon your post as to any particular techniques
that you have built into your application design, or database architecture
that has allowed you to achieve this 'no DBA required' status in your
software? It would be of great value to me, and I also assume others on
this list.

Thanks,
Myles

===============================
Myles Wakeham
Director of Engineering
Tech Solutions US, Inc.
(480) 451-7440
www.techsol.org