Software

Ask something
Discussion Locked

Access on a Server

0 helpful
4 replies

by ryan proctor

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Have Access on a server, assigned users are 164, max users at any one time is about 20, max users during a test is 47. My question is this, where is the point that Access 1: starts to slow down and 2: point of failure. There is plenty of memory (2.5G assigned) for the test, is there any experience out there with this sort of test?

4 replies

by dirtycar74

I think that more information would help to provide a suitable answer. I believe that the number one thing to consider is the design of the database you are using; the more efficiently it is built, the less the database will show signs of slowing and the more data it can handle in a given time. My first suggestion would be to run the analyzer tool and see if Access suggests any design changes. Typically, a well-designed database in Access 2000+ can handle a very large amount of data and a significant number of concurrent users; but nothing is static, there are far too many things to consider separately - Hardware architecture, OS setup, RAM, etc... But like I said, typically, you should consider the complexity of the application and the way that it is designed.

by ryan proctor

All ready known, was looking for people that had similar issues and what they did to work around them

by ryan proctor

The Access database being run has 15 tables with 14 running off of a base table. The base table has 150 columns with over 273,000 rows. Yes that is correct and not a typo. The terminal server is running Windows Server 2000 SP 4 on a 2.8Ghz 3.8GB system. Hope this helps with your answer.

This discussion is closed to new replies.