How do you start a database design?

[rayden54]

I took a database class in school, but most of what I remember is about normalization and SQL. But that would require having an initial database to normalize. I can't remember how you get started.

 

I know they said something about evaulating the existing system, but in my case the existing system is a spreadsheet that doesn't DO what I want it to do.

 

I'm at the stage where I can describe in words what I want the darn thing to do, what I want it to keep track of, and even what I want it to look like when it's done (the front end), but I can't for the life of me figure out what to do first.

 

Any help is appreciated.

 

If you want to offer advice about my specific project, say so and I can edit this post to include a description of my project.

[TheJeremail]

It would probably be best to know some more info on what exactly you're trying to achieve, as the database structure will depend on it

[Guest]

We need a complete description of your project before recommending anything.

[DigitalHermit]

Know the details of your project... this includes data types, process flows, etc.

 

then you determine the tables/entities and their columns and their respective data types...

 

afterwards, make the connections between the tables...

 

go get MySQL Workbench and prototype from there...

[Nuluvius]

I don't have the time right now to launch into a full explanation with examples but maybe this might be of some use to you (it helped me when I was on my degree):

 

[Opcode]

A more in depth description of what you're looking to do and an example of what kind of data you're working with would be needed before any opinions can be thrown.

[vorticalbox]

Best advice to do is start off with a pen and a piece of paper, before you go anywhere near any databases. Draw boxes to represent tables (objects that you want to store) for example a user table and then write out the attributes you think that table might hold (username, email...) then when you have multiple tables draw lines to show any links that might be between them to show where you need foreign keys etc. Once you've designed it on paper, then and only then move on to making it on a computer.

 

I normally do a class digram, that will show you the attributes. Some might be in a database some not.

 

I'm currently doing a plan for college for a system that manages a rugby team. been doing it for weeks now still not finished  

[MatazaNZ]

I took a database class in school, but most of what I remember is about normalization and SQL. But that would require having an initial database to normalize. I can't remember how you get started.

I know they said something about evaulating the existing system, but in my case the existing system is a spreadsheet that doesn't DO what I want it to do.

I'm at the stage where I can describe in words what I want the darn thing to do, what I want it to keep track of, and even what I want it to look like when it's done (the front end), but I can't for the life of me figure out what to do first.

Any help is appreciated.

If you want to offer advice about my specific project, say so and I can edit this post to include a description of my project.

The first thing you need to do is define the purpose of the database. What you want it for, what kind of data you want to store. Then you should list off the entities to have data stored about, then the attributes of each entity. From there, once you're certain you have the detail you need, then normalise