So, now that I am convinced that DBMSs are truly exemplary of the greatness of mankind, I am setting out to understand the different categories of DBMSs or in fancy nerd-language, the different types of DBMS architectures.
Architects Build Models
I am feeling slightly hippy, so here is a definition to suit my mood:
Data flows: Data moving through an organization or within an information system. (Jessup, Valacich, and Wade 413)
That was fun!
And now, onto more serious fodder:
Data model: A map or diagram that represents the entities of a database and their relationships. (Jessup, Valacich, and Wade 413)
And, how convenient! Here is an illustration of 5 common data models:
4 common Database Models are the following:
For further reading on the 4 common database models listed above, and on some more unusual ones, go here.
DBMS programs
Now, onto the more interesting stuff. Having designed a database system to suit an organization's strategic goals, the next crucial decision is the one to choose which DBMS program is the one best suited for the organization. There are several of these programs, so here are the tree most common ones:
References:Jessup, Leonard M., Joseph S. Valacich, and Michael R. Wade. Information Systems Today: Why IS Matters. 2nd ed. Toronto: Pearson Prentice Hall, 2008.
"Database Model." en.wikipedia.org. 28 Mar 2009. 5 Apr 2009
www.mysql.com. 6 Apr 2009
www.oracle.com. 6 Apr 2009
www.sap.com/canada. 6 Apr 2009
www.mysql.com/
No comments:
Post a Comment