If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Database design containing daily data
I work for a water distribution company and am faced with the task of
designing a database to analyze flows in the system in order to track water rights and maintenance issues. This entails about 30 sites with a flow total for each day over the course of a year. I want to be able to analyze any number of these sites for any given period of the year, so monthly totals are not an option. My primary question is how do I go about forming my tables? Should I build one big table for all the daily flows for all the sites (about 11000 individual flows)? Or would it be better to split them up somehow? I'm very new at this and appreciate any help you could give me. |
#2
|
|||
|
|||
Kyle
The amount of your data should not be the primary determiner of how you organize your tables. Access is a relational database, so to get the best out of its features and functions, you'll need to look into normalizing your data. If these are foreign terms (relational, normalizing), you'll either need to do a bit more studying, or may want to look for another approach. How is it that you've already settled on Access? -- Good luck Jeff Boyce Access MVP "Kyle - Park City Water" wrote in message ... I work for a water distribution company and am faced with the task of designing a database to analyze flows in the system in order to track water rights and maintenance issues. This entails about 30 sites with a flow total for each day over the course of a year. I want to be able to analyze any number of these sites for any given period of the year, so monthly totals are not an option. My primary question is how do I go about forming my tables? Should I build one big table for all the daily flows for all the sites (about 11000 individual flows)? Or would it be better to split them up somehow? I'm very new at this and appreciate any help you could give me. |
#3
|
|||
|
|||
Hi Kyle,
Typically you'd have one table for Sites, with one record for each site, and a related table storing all the daily readings for all the sites. It's then possible to build queries that will analyse the data just about any way you can think of. On Tue, 25 Jan 2005 14:53:04 -0800, "Kyle - Park City Water" wrote: I work for a water distribution company and am faced with the task of designing a database to analyze flows in the system in order to track water rights and maintenance issues. This entails about 30 sites with a flow total for each day over the course of a year. I want to be able to analyze any number of these sites for any given period of the year, so monthly totals are not an option. My primary question is how do I go about forming my tables? Should I build one big table for all the daily flows for all the sites (about 11000 individual flows)? Or would it be better to split them up somehow? I'm very new at this and appreciate any help you could give me. -- John Nurick [Microsoft Access MVP] Please respond in the newgroup and not by email. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Sharing mdbfiles | Jan | General Discussion | 9 | December 31st, 2004 07:37 PM |
Is this possible with Excel Chart? | q582gmzhi | Charts and Charting | 1 | September 8th, 2004 03:33 AM |
Adding staff photographs to my database | KK | New Users | 2 | September 3rd, 2004 07:41 AM |
What is MDE | Charlie | General Discussion | 4 | August 24th, 2004 04:15 PM |
Mial merge data base problems | Rachael | Mailmerge | 16 | May 21st, 2004 06:22 PM |