I want to design my own SQL database?

Question

Help..


Where do I start?

Answer 1

http://dev.mysql.com/doc/
http://dev.mysql.com/doc/refman/5.0/en/tutorial.html
http://www.visualcase.com/tutorials/database-design-tutorial.htm
http://www.webdevelopersnotes.com/tutorials/sql/mysql_database_introduction_mysql_beginners_tutorial.php3
http://www.geekgirls.com/databases_from_scratch_3.htm
http://www.edm2.com/0612/msql7.html

Answer 2

There are many books and sites online available that can help you design your database schema. First, you have to decide what you want to hold in your database. Then you can derive the different tables that your database will contain. If you are looking to store information about Employees of a company then Employee might be one of your tables. This table would consist of all data related to a specific Employee. The table could contain columns such as FirstName, LastName or EmployeeID. After you have mapped out what tables you will need to store the required data you would then want to look at adding primary keys to the tables. Normalizing the tables, or ensuring that data is not repeated in multiple tables, would be one of your next steps. Designing a database is a bit of a black art as you can give 5 different DBA's the task and you would probably get back 5 different designs. Start with a small example and learn the different steps that it takes. Then you can expand on this as your needs grow.

Answer 3

A girl designing a database, that's hot.

Answer 4

MS get entry to is a reliable device to start up to ordinary strategies to apply relational databases. it truly is a document-depending device - and in no way a real "database server". in case you want to study sq. and queries and relationships - then MS get entry to may be the perfect starter device and then pass a server database. if you attempt to ordinary strategies to manage severe volume databases that require optimization and attempt to advance your skillset to artwork as a database administrator, then i could start up with both MySQL or MS sq. Server 2005 convey - it truly is more suitable physically powerful, yet putting it up may require more suitable element (administration...) because it truly is server depending.

Answer 5

The most overlooked task in designing a custom database is PLANNING. Too often we plan our database while we're creating it which leads to poor design and functionality. Planning and developing your table structures is equivalent to building the foundation of a home. If you cut corners on the foundation of your home or use cheap materials, your home will have structural problems down the road. Likewise, if you have poorly structured tables in your database, you'll be limiting the FUNCTIONALITY of your database. Here are some basic steps for insuring that your database foundation is solid.

KNOW WHAT YOU WANT

Begin with the end in mind. Get feedback from anyone who will be using the system or receiving reports generated by it. What reports will they want? What do they EXPECT from the database? Communication with everyone involved is critical. Get others involved and excited about the new database. Too many database applications fall by the wayside -- not because they are not good, but because they were the 'brainchild' of only one person. If that person leaves the company, the system will probably not be maintained and used.

START WITH THE FINAL PRODUCT

Sketch all REPORTS first. Perhaps you need mailing labels, letters or special summary reports. What information needs to be in them and in what format? Again, involve others, when applicable, in discussing reports.

KNOW WHAT IT CAN DO

Learn the LIMITS of your database software. Will it display information in the desired format that you need for your reports? Will it import and export in formats that allow you to use other software? You can gain even greater flexibility by using other software applications in CONJUNCTION with your database program. For example, add a desktop publishing flair to your letters by exporting the results of queries to a word processing program and merging there. Most database programs will export to word processing merge data files. Microsoft Access, for example will export a Microsoft Word merge data file.

DETERMINE YOUR PARAMETERS

Determine your selection CRITERIA. How should you sort or query your database? For letters and labels, will you normally print by state? Zip code? Company name? Or perhaps you will print contacts by their type, such as a customer, prospect, or lead. Ask yourself these questions for each report that you sketched in step two.

SETTING UP YOUR FIELDS

Start by listing all of the fields needed. Brainstorm and write everything down that you might need. Specify the lengths and data types of each field. For example, Zip Code would be Text 10. Although a zip code may seem to be a number, it should be considered a text field because of the leading zeroes and dash. Then group like fields TOGETHER. If you were creating a customer database, you would place all the customer contact information in one table, all the order information in another, and a history of contact with people in another. Also make each table self-contained and eliminate REDUNDANT fields.

THE CORE OF YOUR DATABASE

Assign KEY FIELDS. A key field is the column(s) with which you can reference any given row in a table. It is what makes each row unique. For example, ContactID is the key field in our Contact table. InvoiceNo is the key field in our Invoices table. Use key fields to LINK tables together and look up information. Speed up queries and searches by creating indexes on your key fields.

SETTING UP YOUR TABLE STRUCTURE

Decide on the RELATIONSHIPS between tables. How will your tables connect? For example you might use ContactID in both a contact table and an order table to give them a common link.

A WAY TO ADD INFORMATION

They lay out your INPUT screens. What is the most efficient way to enter information with a minimum number of keystrokes? If your database program supports SUBFORMS, learn how to use them. For example, you can combine contact information and a history of every interaction you have had with that person on one screen. The contact information would be in the main form, and the list of activity with that contact would be in a subform.

PUTTING IT ALL TOGETHER

After the planning is complete, the CREATION process should be relatively easy if you know how to use the basics of your database. Create your tables, forms, and then reports.

HUNT OUT THE BUGS

Finally, TEST, TEST, TEST. If you are revising an existing system, continue to use it simultaneously with the new system until everything is optimized and correct. Often you do not find errors or missing fields until the database is fully loaded with data. Ask anyone who will be using your database to use it and offer suggestions and comments. Expect to fine-tune your database.

LET IT LOOSE

Your database is a living entity. You will return to the planning and design phases as you find new USES for your custom database and your needs change.