Good Sense Approach to Databases

Read More About Databases

Have you ever wanted to make a database, but are not certain how to approach it? What are your information needs? Are you happy with just using a flatfile type database which spreadsheet programs offer, or are you looking for keeping a relational database which data duplication can be almost eliminated. Can other programs be used to help control your information and also keep reports that you generate? Here is some insight of what is possible when you can emply Common Sense with this type of programming.

For any type of data that you need to keep in a database, you should program on its design. What data are you wanting to keep, what kind of reporting is to be done, will you be expanding the database to include other information over time? What database program, or platform, can you program with, MS Access, FileAmigo, FoxPro, OpenOffice.Org Base, etc. Are you desiring the database to be web-based so that you can process the information to other people, or independent on your own personal computer? Depending on the bells and whistles you wish and how complicated you desire the program to be, will depend on the platform you use.

Database design is to be well thought-out. Once you have the database to be active and have data stored, it is difficult to alter its pattern. In the design, you must remember how much data you are to store, how fast you need the informationto flow, how much other datayou will desire to add later. Try to remember that the more datayou store, whether it's records or fields, the slower the database will run.

I like to program the One-to-many relationship type databases because I can add to the database as time goes. My dataneeds do change over time. For me, this is the most beneficial approach. This type of database allows you to define a main table, which contains data that doesn't change, and sub-tables where you can put informationthat relates to the primarydata. For example, I have a database of music that is played each Sunday in Church. The primarytable record consists of the song title, artist, copyright date, etc. I track the dates I play the music and where in the program this occurs. This is a sub-table record because I am adding datato each maintable record. So when I want to find out when a song has been played and where in the service this occurred, I bring together the primarytable and the sub table of dates. Then I display the information.

Once I'm done with the planning of the database, I look it over to find datathat may be duplicate. If its datathat I can do without, I eliminate it. The term Normalizing is the procedure of organizing the data so that redundant data is eliminated. This would mean having the same data stored in more than one table. We also need to be aware of the related informationbeing stored. Does this accurately relate to the main data record? When the database is Normalized properly, you will cut down the amount of space the database consumes and that all datais stored in a logical manner.

Article Source: http://depositarticles.com/

InfoDome is a simple and powerful online database that makes it easy to gather, handle, analyze and share your data. I am in the process of doing some applications with this platform, so visit my website to see the projects I am working on with InfoDome.

Please Rate this Article

Not yet Rated

Click the XML Icon Above to Receive Databases Articles Via RSS!

Additional Articles From - Home | Computers | Databases

Our other websites
All about SEO
Beauty Tips Forum

	Print This Article
	Post Comment
	Add To Favorites
	Email to Friends
	Ezine Ready

Submit Articles
Member Login
Link Us
Submission Guidelines
Ezine Notifications
Article RSS Feeds
Sitemap

New Stuff
About Us
Developer
Good shopping portal
Link to Us
Contact Us
Privacy Policy
Terms of Service