By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,327 Members | 1,936 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,327 IT Pros & Developers. It's quick & easy.

Backend database ... scared about performance

P: n/a
Hello all

I have a client who is wanting me to develop an Access DB or VB app
that is basically a fairly simple call tracking system.

They are expecting approximately 15-20 users, and possibly about
25,000 calls per year.

I'm nervous using MS Access 2003 as the backend, since I'm thinking
those metrics are going to be too much for Access.

What do people think? Is this too much for Access? If so, are there
any other suggestions? THis client doesn't have the budget or
infrastructure to support SQL Server, which would be my preference ...
but its out of the question.

Thanks!
Dec 18 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
ch******@gmail.com wrote:
Hello all

I have a client who is wanting me to develop an Access DB or VB app
that is basically a fairly simple call tracking system.

They are expecting approximately 15-20 users, and possibly about
25,000 calls per year.

I'm nervous using MS Access 2003 as the backend, since I'm thinking
those metrics are going to be too much for Access.

What do people think? Is this too much for Access? If so, are there
any other suggestions? THis client doesn't have the budget or
infrastructure to support SQL Server, which would be my preference ...
but its out of the question.

Thanks!
That is a wee, tiny, insignificant amount of data for Access/Jet. You will need
a good design to handle 15-20 concurrent users, but the amount of data is not an
issue.

By the way, there are versions of SQL Server that are free.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
Dec 18 '07 #2

P: n/a
ch******@gmail.com wrote:
>I have a client who is wanting me to develop an Access DB or VB app
that is basically a fairly simple call tracking system.

They are expecting approximately 15-20 users, and possibly about
25,000 calls per year.

I'm nervous using MS Access 2003 as the backend, since I'm thinking
those metrics are going to be too much for Access.
The volume is fine however corruptions can happen. The real decision is, can the
data be rekeyed if you lose a days worth of work? In a call centre application not a
chance. For example can you imagine the ill feeling if a hotel lost a days worth of
reservations? The screaming by the guests with a reservation number who couldn't get
a room would be huge.

SQL Server, and as Rick points out, there are free versions which would very likely
work quite nicely, is significanlty more robust in that area.
>What do people think? Is this too much for Access? If so, are there
any other suggestions? THis client doesn't have the budget or
infrastructure to support SQL Server, which would be my preference ...
but its out of the question.
So the client has 15-20 people working in a call centre and can't spend $4,000 or
$6,000 on a SQL Server system? This confounds me. Let someone else have the
privilige of working with them. In other words fire them.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Dec 18 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.