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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Linked table performance
- Thread starter JBaileys
- Start date
Setting up linked tables is not near as costly as using such things like the IN clause within a SQL statement. There are some very real reasons as to why there would be so many DB files, one, and probably the biggest reason deals specifically with the max size allowed for any one Access DB file, which CAN NOT exceed 2GB in size. Some may say, this would take a lot to exceed this limit, but in my own opinion, that's sort of statement would only be true in a relatively small DB environment.
The amount of data that gets added can get to be a rather large amount over time. To estimate, think of 3 questions:
How many users are on the system?
What are the various types of data being stored in the system?
How much data of each type is being added/removed from the system on a per business day average?
Even with me being very big on getting data to 5NF, I still face this issue. Some would say, if one has this sort of issue to face, why then don't one go to some other DB program that is meant to handle such amounts of data? We all have duties that has to be perform, and we all have things that has to be met. With the owners that we currently have for the business, they are so tight with the spending of the money they get, I have to make do with what I currently have, which is Access.
As one of my co-workers states it, pick any 2: Cheap, Good, Fast. You won't get all 3. If you want it good and cheap, it will take a long time. If you want it good and fast, it will take some major money. If you want it cheap and fast, it won't be good.
At the minimal in a multi-user environment, one should have 2 DB files, a FE DB file (the DB file that each user should have a current copy of on their own PC machine), and at least 1, if not multiple, BE DB file (the DB file(s) that's on the server which contains the table structures and all of the data in the system).
17 DB files sounds kinda high, but then I guess it would depend on the amount of data that's being recorded and the type of data each BE DB file contains. I currently have 5 DB files. 1 of the 5 DB files is more or less treated as both a BE DB file, and as an add-in, cause it's a db file that has information for conversion purposes, thus it to be opened in Read-Only mode while it's stored on the server side so as it's only retrieved when it's needed, but yet available to all users that may need it.
Ronald R. Dodge, Jr.
Production Statistician
Master MOUS 2000
When the going gets tough, the tough gets going.
The amount of data that gets added can get to be a rather large amount over time. To estimate, think of 3 questions:
How many users are on the system?
What are the various types of data being stored in the system?
How much data of each type is being added/removed from the system on a per business day average?
Even with me being very big on getting data to 5NF, I still face this issue. Some would say, if one has this sort of issue to face, why then don't one go to some other DB program that is meant to handle such amounts of data? We all have duties that has to be perform, and we all have things that has to be met. With the owners that we currently have for the business, they are so tight with the spending of the money they get, I have to make do with what I currently have, which is Access.
As one of my co-workers states it, pick any 2: Cheap, Good, Fast. You won't get all 3. If you want it good and cheap, it will take a long time. If you want it good and fast, it will take some major money. If you want it cheap and fast, it won't be good.
At the minimal in a multi-user environment, one should have 2 DB files, a FE DB file (the DB file that each user should have a current copy of on their own PC machine), and at least 1, if not multiple, BE DB file (the DB file(s) that's on the server which contains the table structures and all of the data in the system).
17 DB files sounds kinda high, but then I guess it would depend on the amount of data that's being recorded and the type of data each BE DB file contains. I currently have 5 DB files. 1 of the 5 DB files is more or less treated as both a BE DB file, and as an add-in, cause it's a db file that has information for conversion purposes, thus it to be opened in Read-Only mode while it's stored on the server side so as it's only retrieved when it's needed, but yet available to all users that may need it.
Ronald R. Dodge, Jr.
Production Statistician
Master MOUS 2000
When the going gets tough, the tough gets going.
- Thread starter
- #3
The number of users on the system is fairly low as high as maybe 7-8.
We are actually now beginning to convert the Access dbs to SQL Server. This is a long process - but favorable. Today, we store customer and special customer scoring data outside in Access yet.
The system sees about 100 records a day for changes. So, our linked table concern will be going away soon.
We are actually now beginning to convert the Access dbs to SQL Server. This is a long process - but favorable. Today, we store customer and special customer scoring data outside in Access yet.
The system sees about 100 records a day for changes. So, our linked table concern will be going away soon.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
