Re: Relationship between users, database applications, DBMS, and database

[EMAIL PROTECTED] (emeded) wrote:
>I need to explain in one paragraph relationship between users,
>database applications, DBMS, and database. It is not so easy to
>summarize all important things in one paragraph. Can somebody help me?

I hang out in comp.databases.pick, which is for the Pick database
model, not for picking databases.  I'll cross-post this response but
no more unless asked.  These are just some comments for you to
consider as you do your own research.  I think you've asked a very
interesting question which is probably not what anyone expected.

The simple answer is: A user runs software, which is a database
application, to manipulate data contained in a database.  One or more
databases are stored in a DBMS and they are subject to the rules
enforced and features provided by that DBMS.

Outside of the technical definitions, users should not have any
understanding of the underlying mechanics of the database
applications.  That is, they shouldn't have to know how to navigate
the application or how the data in the application relates - a good
application will simply perform the functions required and expected by
the user so that they can focus on what they do and not the software
that does it.  Too many business applications expect the user to think
a certain way in order to get things done - the software should
"think" like the user.

A DBMS is a wrapper around one or more databases.  Each DBMS type
claims to be better at maintaining data better than others.  Examples
of DBMS's are Oracle, SQL Server, MySQL, D3, jBASE, dBASE, DB2,
Universe, Interbase, etc.  Again, the user should not have to know or
care what DBMS they're using, only that their data is safe and being
processed as they expect.  The question is "who is the user?"  If the
user is Sue the data entry person then she shouldn't care.  If the
user is Sue the company owner or Sue the IT director then she should
care if her DBMS is Oracle or MS Access.  The difference is both
technical and a matter of perception - would you buy stock in a large
company if you knew they did all of their financials in MS Access?

By "database application" I think you mean "application software"
which could be business software like accounts receivable or inventory
management.  It could also be a game which tracks player positions and
scores, or a program to track your favorite restaurants.  Good
application softare should be as independent as possible of the
underlying DBMS, but in the real world many developers tie their
software heavily into the DBMS to utilize the benefits the DBMS
provides.  By making software DBMS independent, you can more easily
move your application and database to another DBMS.  This portability
can be of great value to the end-user.

I'll quit there, but when you ask about the "relationship" between
these things, there is a simple definition that you can answer in one
paragraph, but there can be a lot more too it as well.

I hope that's not too much.  :)


Tony Gravagno, Nebula R&D
[EMAIL PROTECTED]
Former DBMS Product Manager, QA Manager, and other positions,
  Raining Data (database company)
Technical Editor, "C#Builder Kick Start"
Now Available in book stores and Amazon.com
http://www.amazon.com/exec/obidos/ASIN/0672325896/cstati
Author "Web Services and .NET" article series, Spectrum Magazine