Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
MikeB
Constraint Violating Yak Guru
387 Posts |
 Posted - 2003-08-26 : 16:03:14
|
| I have an application that save production / shipping information for a group of companies. This use to be two companies with one plant and one office. Now it is three companies with 2 plants and t offices. The database is Access (I know, I know, I am trying to get SQL Server) and currently all information on the previous 2 companies is stored in one MDB file. Now, however, with the introduction to the new plant, the amount of records is going to double. In just the scheduling table alone, I can see at the very least 7500 record a month (90,000 / year). I am thinking of splitting this into multiple mdb files simply to simplify the maintenance. One production mdb for each company and a general mdb file for general information. Will this make a difference at all?Mike B |
|
|
Stoad
Freaky Yak Linguist
1983 Posts |
Posted - 2003-09-01 : 15:05:55
|
| I think that it is better to store everything in one mdb,300,000 records / year is near to nothing for MS Access.As to simplifying the maintenance... will be it simpler or notonly you can decide on it. |
 |
|
|
|
|
|
Database design