Access ADP performance with 1000+ users?

[ak_ls]

Can anybody share experience of using Access ADP application with 1000+ users?

tried this question in general section and there was no reply. Is it that ADP applications are not targeted for large number of users?

 

[SQL_Hell]

How long is a peice of string?

This is an impossible question to answer, there are too many variables,

1. What spec is the server?
2. what version of sql
3. how fast is the Network at it's slowest point
4. how big is the database?
5. how well indexed is the database?
6. How well programmed are the queries?
7. how well normalised is the database?


I could go on

 

[ak_ls]

Thanks SQL Hell.

My question is targeted to those who have used ADP application for 1000+ users and request to share their experience and describe the environment.

So far nobody has replied. It seems that nobody has deployed the ADP / SQL Server for 1000+ users.

I, myself has no such experience. I have asked this question as I am creating few ADP/SQL Server based tools targeting use in large organizations. As per my understanding ADP/SQL Server based applications are scalable in performance and should support 1000+ users.

 

[Banana]

A word of caution: it's not the ADP per se that make it works with 1000 users.

It's how you design the application. I'm reasonably sure that a MDB would be just as capable, provided it's designed correctly.

Another thing we need to be careful is to not conflate what belongs to server and what belongs to client. For instance, number of connections that is possible is a question only a server can answer. It doesn't actually matter what kind of client you have, only the matter of connecting. If we change the question from number of connections to how many concurrent requests a server can handle, it now can only be answered by clients, not the server because it now depend on how nicely the client plays with other and doesn't try to hog the server for all itself.

 

[ak_ls]

Thanks Banana,

ADP is a single user client and it does not support more than one connection at a time. Therefore, in ADP/SQL Server based application design, users scalablity issue has to be addressed by ADO and SQL Server side.

Do you have some tips for ADP application design considerations for such situation? These may be useful for me to do a check on the my current applications design.