Thursday, April 12, 2012 11:56 AM
iam newibes.....pls ...how to Designing a database for a tennis league .?????????
how to design and Architecture and tables and everything on tennies game.
pls guide to me....
- Split by Louis DavidsonMVP, Moderator Saturday, April 14, 2012 3:41 AM question in middle of thread
Friday, April 13, 2012 2:17 PM
Start by identifying the things that you need to keep track of....players, leagues, tournaments, whatever. Then identify the properties of those things...players have names, tournaments take place at a location. Then make sure there isn't any duplicate data (don't store a players' name in the tournament table, just link them.)
Then, when you're hopelessly confused, get yourself a book on relational design. I wrote one, Designing Effective Database Systems. CJ Date's Introduction to Database Systems is academic (for which read "a bit dry"), but a classic. A lot of people like Database Design for Mere Mortals. I don't, but I'm not the target audience. I can recommend Steven Roman's Access Database Design and Programming is of date but well-written. Pick one you like the looks of.
As I said, relational databases are wierd. It's like looking at those holographic pictures...there's a trick to the way you look at them that's hard to articulate it, but at some point it will "click" and start making sense.
Rebecca M. Riordan
Saturday, April 14, 2012 3:35 AMModerator
I disagree that it is "weird", but it is definitely different from any other coding. It all comes down to breaking down the data you want to store into chunks that can be stored as single pieces of information. Totally agree on the book path, and not just because I have written a book on database design myself, but because if you are just starting out, a book (or a class) will lead you along the path better than random websites, or even here in this forum.
On the other hand, please come back here and ask for advice along the way.
Step one in a project like this: "Designing a database for a tennis league"
Is to stay away from the database server, and write down in simple text, every single piece of information you can, and then every rule that you will need to enforce. From there the task will be a heck of a lot easier. Tables will be nouns that represent one thing (player, tournament, rankings), any sort of text linking tables will be relationships (Players play in tournaments, players play challenge matches), and adjectives will be columns (player rank, player name, etc)
It isn't a hard process, but the most important thing is to do your design before you start creating tables and coding because changes are free when the design is just on paper. You may not design the entire database before coding, but having a good understanding of the entire problem is key.
Without good requirements, my advice is only guesses. Please don't hold it against me if my answer answers my interpretation of your questions.
Saturday, April 14, 2012 7:14 PMyou don't provide much detail but as said above write down everything you want to capture. Figure out which are entities (player, tournament, court, etc) and from there decide which attributes belong to each entity. From this point start to normalize the db to at least the 3rd form
- Edited by Knowledgy Solutions Saturday, April 14, 2012 7:15 PM
Sunday, April 15, 2012 4:21 AMAnswererLooks like a homework is not it? See this link http://www.databaseanswers.org/data_models/chess_tournaments/index.htm I think the Chess Tournaments tables will be close (no doubles games :-)) to Tennis Matches
Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/