| Author |
 Topic  |
|
|
Morpheus73
Average Member
Denmark
597 Posts |
 Posted - 18 April 2002 : 15:47:53
|
what will put the most strain on the server
1. an (access) database with many tables holding less content per table
2 few tables with large amounts of content in each table?
3. the same?
 |
|
|
Doug G
Support Moderator
USA
6493 Posts |
Posted - 18 April 2002 : 16:53:42
|
4. Not enough info to determine :)
What kind of data and how you code access to it has more of an impact on the system than anything else, imho.
If you're talking about a design decision, I'm curious what kind of data structure would let you do an either/or. Usually the data itself greatly determines the structure of the database.
======
Doug G
====== |
 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 18 April 2002 : 17:21:04
|
As Doug correctly pointed out the database structure should be determined, firstly, by the nature of the data itself.
The first approach to database design usually entails the development of a model (often an Entity/Relationship model, although I personally prefer a UML class model) to depict the entities/classes involved and their relations. It is very easy to derive a normalized database structure from this.
Normalization can be obtained through other ways, but this normalized structure, regardless of the way used to obtain it, really depends on the nature of the data that you want to keep in your database.
Sometimes a normalized database structure can hinder performance. You can then de-normalize in order to overcome that, but then you can do it with a good reason to do it, and with proper knowledge of the advantages and disadvantages of doing it.
Usually normalization is usually the way to go, regardless of the method you choose to achieve it.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs
Edited by - ruirib on 18 April 2002 17:22:11 |
|
|
|
Morpheus73
Average Member
Denmark
597 Posts |
Posted - 18 April 2002 : 18:26:29
|
well, basically itīs snitz forums....
what would be the best do you think - having like 10 different forums with same members table (cookie set to website) or making a sub system of forums using "GROUP" capability?
|
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 18 April 2002 : 18:37:19
|
quote:
well, basically itīs snitz forums....
what would be the best do you think - having like 10 different forums with same members table (cookie set to website) or making a sub system of forums using "GROUP" capability?
Do you need to have ten forums? And what is group capabality?
I would say, however, that the use of a common database to the forums, if Access based, could be a severe limitation, if you get some traffic on the forums. Using several Dbs would certainly improve the overall performance.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs |
|
|
|
TerryG
Junior Member
United Kingdom
179 Posts |
Posted - 19 April 2002 : 09:22:07
|
ruirib,
quote:
The first approach to database design usually entails the development of a model (often an Entity/Relationship model, although I personally prefer a UML class model) to depict the entities/classes involved and their relations. It is very easy to derive a normalized database structure from this.
I use Access and ADO/ASP at work on an Intranet and thought I knew a bit about it but all the above is new to me. What resources would you recommend for me to learn about Entity/Relationship or UML class models and "normalized database structure" ? Any good books or sites you would recommend? Thanks
Edited by - terryg on 19 April 2002 09:22:58 |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 19 April 2002 : 09:36:02
|
Right now I can only give the book I like most for using an Object-Oriented Approach to database design: Object-Oriented Modeling and Design for Database Applications, Michael Blaha / William Premerlani, Prenttice-Hall.
There are others, but this is devoted specifically to database design using UML and an OO approach.
There many good books on relational database design. I can try to find the title of one I found very interesting since it was very pragmatical and covered the basics regarding normalization and use of Entity/Relationship models in a simple and readable manner. I'll have to look for it since I haven't used it for quite a while.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs |
|
|
|
TerryG
Junior Member
United Kingdom
179 Posts |
Posted - 19 April 2002 : 11:15:44
|
quote:
I'll have to look for it since I haven't used it for quite a while.
Thanks ruirib
|
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 19 April 2002 : 11:59:48
|
Terry, the book I was looking for is:
Relational Database Design With Microcomputer Applications, Glen A. Jackson, Prentice Hall.
Amazon.com says it's out of print, but there is someone trying to sell a used copy. I'd really recomend this book. There are other good books on the subject, but this is the best I've seen for learning E/R models and normalization.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs |
|
|
| |
Topic |
|
Topic Locked
