| Author |
 Topic  |
|
|
oboro-ky
Starting Member
1 Posts |
 Posted - 01 June 2008 : 16:26:14
|
I hear war stories about using Access database with too many users at one time. Is this a concern using Snitz?
< |
|
|
AnonJr
Moderator
United States
5768 Posts |
Posted - 02 June 2008 : 00:42:33
|
It is a concern with Access - doesn't matter what software you're using to connect to it. As to how many is too many, it really depends on your server, the number of active visitors, and what they are doing.
I'm using an Access database at the core of the hospital's learning management system. There are on average 20 or so active users at any given time, reading and writing to the database. But, we've got a reasonably beefy server, and we're not sharing it with too many other data-intensive sites. Most of the sites on that server are relatively static. In the end, your results may vary depending on a lot of different factors.
If you can go with a SQL Server or a MySQL back end, I would go ahead and start off on the server. Just make sure the host will work with you on migrating your data if you decide to go with some other service.< |
 |
|
|
pdrg
Support Moderator
United Kingdom
2897 Posts |
Posted - 02 June 2008 : 07:13:37
|
Although, technically, JET (the engine inside Access) can run 255 concurrent connections - just not always as efficiently as you'd hope.
Snitz and most other web apps are actually quite gentle on the database connection-wise, they create a connection, use it, and destroy it in a fraction of a second, so 10 people on your website may only be using 0-3 connections between them in reality at any time, depending if they're just reading a page or all refreshing all the time. The bottleneck is more likely to be large datasets or inefficient SQL.< |
|
|
|
AnonJr
Moderator
United States
5768 Posts |
Posted - 02 June 2008 : 08:46:36
|
| The bottom line is that a lot of Snitz forums are running just fine using Access. It is possible to out-grow Access, but for a site that's just starting its not a bad choice. Having said that, I still stand by my original reccomendation: If you can go with a SQL Server or a MySQL back end, I would go ahead and start off on the server. Just make sure the host will work with you on migrating your data if you decide to go with some other service.< |
|
|
|
Doug G
Support Moderator
USA
6493 Posts |
Posted - 02 June 2008 : 20:52:49
|
These forums began on an Access db and got pretty busy before they were changed over to SQL Server. You'd have to ask those who hosted this forum if there were any instances of access corruption, but as the usage outgrew access there were pleny of instances of strange errors with the forums application that quit happening after the db switchover :)
< |
======
Doug G
======
Computer history and help at www.dougscode.com |
|
|
| |
Topic |
|
Topic Locked
