Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
How I can come up with an effective BodyBuilding database, what entities are most important?
From which I should be able to come up with an ER diagram. I'm still a novice to databases, but I have read quite enough, most difficult I'm finding a problem with differentiating between a Gym database and BodyBuilding Club database.
Have you tried listing everything you think relates to the database, then removing the ones you don't like, then grouping them in a way that makes sense to you or users of the database?
Certification types, access to bodybuilding books, bodybuilding trainers, ease of super sets, free weight ratios, ratings from heavy lifters, etc.
Try everything, make a list, narrow it down to the items needed for proper function and your business perspective (safety, legal, etc).
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 days ago.
Improve this question
I'm designing quite simple database for storing the hotel rooms reservations. The Reservation object in the database has StartDate, EndDate, RoomId, and ClienId fields. The most frequent query to the database will be to retrieve reservations for certain period of time (e.g. find all reservations in December 2024). So, with time I assume that there will be quite alot of reservations (maybe 10000-25000), and of course I can just delete old reservations, but theoretically, is it possible for the database to swiftly execute this query in such a big data? As I understand, database will automatically organise all reservations by StartDate. Am I right? Should I even wary about that, or all modern databases will do all this "dirty work" for me? What articles/books can you recommend for me to read about databases performance?
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
When relations between tables are created it becomes very difficult to edit tables, drop and re-create them. well I decide to leave creating relations for when the job is done and that time its not easy either and later some tables might need modifying again.
what is the best practice for creating foreign keys, and all other relations?
In big projects that I devide project to several small projects, well sometime in one of the smaller projects I see that I have to make a small change to previous small projects. and this ruins everything.
I always create relations when I create my initial database structure, and because it is normally (sometimes... once was...) designed properly, the relations don't tend to change.
What you may find eases any changes to the tables is to change one of the options
In Tools-Options, choose Designers - Table and Database Designers and clear the checkbox marked Prevent saving changes that require table re-creation
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have a database design issue and I'm not sure which of my alternatives I should go with.
I have a system that shows a politician's votes on every issue. Users can log in and "support" that politician on each issue. I'm not sure how the associations should work. Here is a picture of two alternatives:
http://i1068.photobucket.com/albums/u447/dmoss18/ScreenShot2012-05-03at111656AM.png
Option 1: A politician has many votes on many issues. A user supports each politician's vote.
Option 2: A user supports a politician on a certain issue (an association table with three foreign keys).
Is option 2 not feasible at all? Is it bad practice to associate three tables in one entity? Which option is considered best practice?
I would prefer option (1) because it shows that the user supports the particular vote. In option (2) it would seem to be possible (without additional constraints) for a user to support a certain politician on a certain issue when that polititian has never voted on it at all! (Of course if that is a desirable possibility then you must go for option (2)).
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
This is question is only about terminology.
I want to know if there is some special name to describe the database that are about some theme/domains like movies, games, music, places, etc.
It's generally just "X database". For example, "movie database", "game database", and so on.
In some contexts you can refer to what is essentially a database by some other names, for example in Prolog you talk about the "knowledge base".
There are some words in the English language that basically describe databases, such as dictionaries, atlases, and encyclopedias, but those are generally considered things and are implemented with databases.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
please clarify me on the below questions,
who will do the great data model design?
Technical lead / Database Admin
Thanks,
Gunasekaran Sambandhan
Depends on how the responsibilities on your team are broken out. Normally, I would say the Technical Lead (Application Architect) would do the data model design. The DBA could then implement and tune the database to provide the best performance.
That could always changed based on the skills of the Technical Lead and the DBA though...
It depends on how large your team is and how well its structured. In data-centric applications I can tell you that as technical lead I have generally done either the database design or a high-level version that is refined (and sometimes changed a lot) by a dedicated database developer.
But there is no hard and fast rule.