| Author |
 Topic  |
|
|
TerryG
Junior Member
United Kingdom
179 Posts |
 Posted - 21 February 2001 : 04:40:54
|
I am constantly being told by collegues that Access may run out of steam for larger projects I am working on, but no-one seems to be able to say what its limits are. The inference being we should use SQL Server instead. Are we talking file size for the database, or number of concurrent users or someother factor? What experience do you other Access users have? Does it fall over when the DB gets to Xmb or is it more like it just becomes a bit slower over Xhundred hits an hour. What are the advantages/disadvantages of going to SQL Server or MySQL (I know nothing whatsoever about the latter). All contributions gratefully recieved !!
|
|
|
davemaxwell
Access 2000 Support Moderator
USA
3020 Posts |
Posted - 21 February 2001 : 09:12:56
|
I believe the problems occurs with concurrent users more than the size of the database (though that can happen too). Snitz used to run with Access and I think the problems we had were more with the speed of the server itself than with Access.
Dave Maxwell
--------------
When's the next meeting of Snitzaholics Anonymous |
 |
|
|
Doug G
Support Moderator
USA
6493 Posts |
|
|
tmcgold
Starting Member
1 Posts |
Posted - 21 February 2001 : 17:20:06
|
We're using Access 97 with 200,000 visitors and over 750,000 page views per month. No problems!
|
|
|
|
redbrad0
Advanced Member
USA
3725 Posts |
Posted - 21 February 2001 : 17:37:33
|
access could be used like this as long as the database was setup right. planning the database is an important part of building a dynamic website. in my opinion you would notice a difference if you upgraded to sql. i know if i was getting that many page views, i would be using sql
Brad |
|
|
|
HuwR
Forum Admin
United Kingdom
20600 Posts |
Posted - 21 February 2001 : 17:59:26
|
Also to consider when using any DB backend it is the server that is the primary source of power for the DB, the better the server the more performance you will get from your data. after all, you wouldn't drive a porsche with a mini engine would you.
The largest contributary factors to both SQL and access performance are the amount of memory available and the speed of your disk architecture.
Basically the bigger your database becomes the more resources it will use to accomplish the same tasks.
Size affects access more than SQL mainly because access use the OS to do disk access to retreive the data from it's file, SQL on the other hand does not really on the operating systems disk subsytem to access it's data, but talks directly to its db.
|
|
|
|
MichaelTyler
Starting Member
26 Posts |
Posted - 10 March 2001 : 01:11:41
|
I think access main problem is concurrent users. If you have your indexes right you shouldnt have much of a problem retreiving data. I had an access database that was over a gig in size. Tables with over a million rows. Retrieval was fine to a point. But i only had a total of 20 user who used it and strictly for retrieval. But you should always have your indexes in the proper shape or you will be dealing with a mess. Plus Access databases tend to grow on their own. You need to compress them from time to time.
If you read the microsoft article the intersting point is this
Jet can support up to 255 concurrent users, but performance of the file-based architecture can
prevent its use for many concurrent users. In general, it is best to use Jet for 10 or fewer concurrent
users.
|
|
|
|
rick7165
Senior Member
USA
1094 Posts |
Posted - 10 March 2001 : 05:55:41
|
Access Seems to run ok for me, I'm worried about going to SQL because I don't want to be stuck not able to go back
to Access if needed, Plus I see everyone having a hard time with the mods to run in SQL.
Nice thing about access.... I can put my hands on the Database. I have no club how I can get a hold of my stuff
in SQL.
Test Site
www.eastpasco.com
Running on HuwR's SR4 release. Colors and Graphic scheme done by Richard Kinser. |
|
|
|
LarsBerg
Starting Member
10 Posts |
Posted - 10 March 2001 : 09:24:59
|
Access does run out of steam.
In one of my current projects i have had to switch from Access to SQL due to network load and performance considerations.
The Access architecture became a problem on a 10mb lan with about 500.000 records in a 50MB database.
With SQL 2000, the database has since grown to contain 1.500.000 records. SQL handles that like a charm.
Best regards,
Lars Berg |
|
|
|
MichaelTyler
Starting Member
26 Posts |
Posted - 11 March 2001 : 01:58:29
|
rick7165 your site looks great! But you only have 100 posts so I dont think you can judge whether Access works well or not.
TMC Gold I couldnt find your forums...Maybe you could provide a direct link to it.
|
|
|
| |
Topic |
|
Topic Locked
