I have one table that is used to hold all info. Our db is slowing down. Do I really need to break it up? Five years of info that is needed for statistics are in it. If I should break it up into smaller tables, how to go about it and still use this older data in my forms?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Break one table into many
- Thread starter toni3
- Start date
Toni13
Is your database "normalized"? That is, do you have only 1 table or many related tables?
If you only have 1 table, you should consider re-writing how your store your data. In the meantime, you can copy and paste the FORMAT of your table into the datbase and call it "oldTABLE NAME" and then use append and delete queries to move the data.
Hope this helps.
Jim
"Get it right the first time, that's the main thing..."![[wavey]](/data/assets/smilies/wavey.gif "[wavey] [wavey]")
Is your database "normalized"? That is, do you have only 1 table or many related tables?
If you only have 1 table, you should consider re-writing how your store your data. In the meantime, you can copy and paste the FORMAT of your table into the datbase and call it "oldTABLE NAME" and then use append and delete queries to move the data.
Hope this helps.
Jim
"Get it right the first time, that's the main thing..."
- Thread starter
- #3
Toni
Ouch! No wonder it's slow.
If you don't want to spend the time normalizing your tables, your only option is to create backup tables within your database (or in another database if you want).
You should create a maketable query for records where the entrydate is earlier than 1/1/03. That will create the backup of older items. Then, open that query in design mode, change it to a delete query using the same where criteria on the entrydate field, and that will remove the older records from the active table.
MAKE A COPY OF YOUR TABLE BEFORE DOING THIS IN CASE YOU MAKE A MISTAKE!
Hope this helps.
Jim
Jim DeGeorge
Developer
Ouch! No wonder it's slow.
If you don't want to spend the time normalizing your tables, your only option is to create backup tables within your database (or in another database if you want).
You should create a maketable query for records where the entrydate is earlier than 1/1/03. That will create the backup of older items. Then, open that query in design mode, change it to a delete query using the same where criteria on the entrydate field, and that will remove the older records from the active table.
MAKE A COPY OF YOUR TABLE BEFORE DOING THIS IN CASE YOU MAKE A MISTAKE!
Hope this helps.
Jim
Jim DeGeorge
Developer
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question