Dan Roberts
New member
- Local time
- Today, 11:08
- Joined
- Dec 19, 2008
- Messages
- 4
I have to review large tables of medical claims histories. The total row count is 20,000,000 and the data are downloaded from a sql database. I tried to divide the database into 5 Access databases - one for each year.
I was able to import the text files but each database is very fragile and each is 1.5GB or larger. I have to refresh the data in each database every two or three weeks and the loads often fail. This is not a data warehouse precisely but there are few changes to the data except for the re-loads.
Performance is OK - loading is the biggest problem. Making the Access databases smaller would be cumbersome. The databases must be encrypted and I am using PGP but that does not seem to be he problem.
This is a single-user database. What would be handy is an Access front end to a ODBC single user database. I do not want to spend my time or my client’s as a database administrator.
Any thoughts?
I was able to import the text files but each database is very fragile and each is 1.5GB or larger. I have to refresh the data in each database every two or three weeks and the loads often fail. This is not a data warehouse precisely but there are few changes to the data except for the re-loads.
Performance is OK - loading is the biggest problem. Making the Access databases smaller would be cumbersome. The databases must be encrypted and I am using PGP but that does not seem to be he problem.
This is a single-user database. What would be handy is an Access front end to a ODBC single user database. I do not want to spend my time or my client’s as a database administrator.
Any thoughts?