When to Implement SQL?

Spentak

Registered User.
Local time
Today, 09:05
Joined
May 8, 2008
Messages
19
At what point does one need to get an SQL server, and use SQL as their back end? I want to network access across 30 computers in 10 different locations(outside of LAN), having front end databases on each computer with forms, and the back end to have the tables. Is one terminal server with remote access enough to handle my quantities? Or do I need an SQL server? Can someone point me in the right direction?
 
I don't think there's any cut-and-dried rule about when to convert. It isn't about total users so much as concurrent users. How many will use it at any one time? What do the users do? If they're mainly just querying data, you could handle more with Access than if they're all adding/editing/deleting data. How much data are we talking about? Access can handle more than most people think, but it is certainly one of the factors.

I would think 1 terminal server could handle that many users, even if they were all on at the same time.
 
When you get in Joe's situation, it's time to upgrade:
http://www.access-programmers.co.uk/forums/showthread.php?t=150309

I used to run over 20 concurrent users on old crappy HP hardware running Win 2K and multiple apps and an old version of Citrix. We had about 120 concurrent users across the farm at that time. When we upgraded Citrix and put in blade servers, we got much better performance. I'd still think you could run a simple Access application without a lot of hardware or performance issues.
 

Users who are viewing this thread

Back
Top Bottom