Question - splitting a database up.
I have a case management system built in access. it services 8 teams, each team has 10 people. Its working ok and has about 10K records a month I am managaing the back end with weekly Compacts and even with 20K records its about 90meg.
The main query ( taken from the main table ) has about 100 fields. Its pretty big.
what i thinking of doing is spltting it up per team - so each team has its own databse - adding about 1200 per month.
i think this will make it quicker and if one teams goes down ( corrupted ) it doesnt affect the rest. As for reporting, i will make a front ebnd which looks in all the tables using the UNION sql command so it acts like one big table. This will mainly be used out of hours of to cause any problems.
some questions :
1 : if all the tables in eachs team database are called "Tblmain" - can i still do a UNION ALL query or do they have to have different names ?
2 : is there a quicker way to do this raher thana union all ?
I hope this finds it way to an expert !
d
I have a case management system built in access. it services 8 teams, each team has 10 people. Its working ok and has about 10K records a month I am managaing the back end with weekly Compacts and even with 20K records its about 90meg.
The main query ( taken from the main table ) has about 100 fields. Its pretty big.
what i thinking of doing is spltting it up per team - so each team has its own databse - adding about 1200 per month.
i think this will make it quicker and if one teams goes down ( corrupted ) it doesnt affect the rest. As for reporting, i will make a front ebnd which looks in all the tables using the UNION sql command so it acts like one big table. This will mainly be used out of hours of to cause any problems.
some questions :
1 : if all the tables in eachs team database are called "Tblmain" - can i still do a UNION ALL query or do they have to have different names ?
2 : is there a quicker way to do this raher thana union all ?
I hope this finds it way to an expert !
d