|
 |
access thread: How robust is access?
Message #1 by "Michael B. Deck" <mdassignment@h...> on Fri, 22 Jun 2001 14:35:03
|
|
Hello -
I'm building a database application in VB6. This app will be used to
file medical reports and records so preventing against corruption is
extreamly important because of the legal implications associated with this
data. The max number of records won't exceed 25,000 and there will only
be about a dozen clients with the app even installed and it's very
unlikely that all of those will be in use at once. My question is, has
anyone written an app using access as a data server with this type of
record and user load. And does anyone think SQL Server 7 would be a
better choice.
Thanks,
Mike
Message #2 by BPulliam@B... on Fri, 22 Jun 2001 08:58:40 -0500
|
|
Mike,
I work within the Medical Benefits Administration industry, I use MS Access
is extensivley for elgibility manipulations, monthly reports, claims
analysis, and Cobra - Flex Administration. Just like every other database
out there, a proper back-up scheme must be in place. Data validation rules
set throughout the archetecture etc...
I have worked in mid-sized financial industry firms (consulting) that use
Access extensively for their forcasting models etc...sensitive stuff. Just
like anything else, in the wrong hands MS Access can be a nightmare, (Data
corruption etc.), but for a quick and easy back-end, there's nothing
better.
SQL 7 can get just as hosed up as Access can if ya don't know whatcha doin.
I Started in MS Access 2.0 four or five years ago, in that time I have
only seen one go completely corrupt, and it was unrecoverable. It was in
Access 2.0 and had a transaction loop in it that went bad....swelled the DB
up to 1.2 Gig. way past MS Access's specs.
Keep in mind you can easily migrate to SQL Server later with minimal
adjustment to your app if you keep your naming/data conventions
simple/standard. (Don't use memo, etc..)
Good luck,
Brian Pulliam
Berkley Risk Administrators Company, LLC
IS - Benefits
920 Second Avenue South, #700
Minneapolis, MN 55402-4023
PH# xxx.xxx.xxxx
"Michael B.
Deck" To: "Access" <access@p...>
<mdassignment@h... cc:
tmail.com> Subject: [access] How robust is access?
06/22/01 09:35
AM
Please respond
to "Access"
Hello -
I'm building a database application in VB6. This app will be used to
file medical reports and records so preventing against corruption is
extreamly important because of the legal implications associated with this
data. The max number of records won't exceed 25,000 and there will only
be about a dozen clients with the app even installed and it's very
unlikely that all of those will be in use at once. My question is, has
anyone written an app using access as a data server with this type of
record and user load. And does anyone think SQL Server 7 would be a
better choice.
Thanks,
Mike
Message #3 by SinghToor@a... on Fri, 22 Jun 2001 09:57:50 EDT
|
|
Hi:
There is no doubt that SQL is a better choice but if the size
and the number of users is what you are mentioning,
then you can use access tables to hold the data.
There should not be a problem.
Sincerely,
Harpreet.
Message #4 by "Brian A Paniccia" <bpanicci@n...> on Sun, 24 Jun 2001 13:07:16 -0400
|
|
Mike,
I would highly caution you on migrating to SQL server to solve a record
count caused by a poor transaction. Fix the problem and keep within
100,000 records and you will be fine. I would suggest looking at other
areas to maintain or improve performance first. SQL upsizing using a
wizard rarely is as easy as it sounds and then there is the higher cost.
Upgrade Access first, I've just migrated my clients apps to 2002 Xp and
response times are noticeably faster than 2000. If you are using Access
2.0 , moving to 2002 should be easy and it will provide a much, much
faster JET engine.
One note worth mentioning, In many cases going to SQL server can
actually slow down some functions and doesn't show performance benefits
until higher numbers of concurrent- users or sheer record and table
sizes reach large levels ( higher than 20 users or records over 5-10K/
Tables larger than 250 mb).
Access is just another tool in the tool box, so always try to right size
the tool to the job. I've found out the hard way that installing a
higher end system can often sink the success factor more than tweaking
the simpler cheaper solution. Wrox press Professional Access 2000
programming ISBN- 1-861004-08-7, has a great section on performance
tips.
-----Original Message-----
From: Michael B. Deck [mailto:mdassignment@h...]
Sent: Friday, June 22, 2001 2:35 PM
To: Access
Subject: [access] How robust is access?
Hello -
I'm building a database application in VB6. This app will be used to
file medical reports and records so preventing against corruption is
extreamly important because of the legal implications associated with
this
data. The max number of records won't exceed 25,000 and there will only
be about a dozen clients with the app even installed and it's very
unlikely that all of those will be in use at once. My question is, has
anyone written an app using access as a data server with this type of
record and user load. And does anyone think SQL Server 7 would be a
better choice.
Thanks,
Mike
|
|
|
View Cart
