SitePoint Sponsor

User Tag List

Results 1 to 10 of 10
  1. #1
    SitePoint Member timbo's Avatar
    Join Date
    Jul 2001
    Location
    Derbyshire, UK
    Posts
    5
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Size of access database

    I have a potential client who wishes to integrate an access database into their existing web site using asp.
    The access database has 15000 records at present, which may grow by 2000 per year. Is access suitable for this size of database, or should they be looking at upgrading prior to attempting to integrate the database.

    Thanks

  2. #2
    SitePoint Zealot
    Join Date
    Jun 2000
    Location
    Yeppoon, Australia
    Posts
    186
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I believe that Access 2000 can handle about 10000 records before you go higher (ie. to SQL Server) so I think that you'll probably have to use something more powerful that Access - I son't know about Access XP/2002 but I really don't expect that it could handle a whole heap more than 2000 as I think it still uses Jet 4.0.

    Having said that, having had a quick look through the MS Access 2K site it says that the jet 4.0 engine can handle DB sizes up to 2.14 GB. So I guess it depends on the size of your records.

    For further reading check out KB article Q275561
    Knowledge is knowing that a tomatoe is a fruit; wisdom is not putting it in a fruit salad.

  3. #3
    ALT.NET - because we need it silver trophybronze trophy dhtmlgod's Avatar
    Join Date
    Jul 2001
    Location
    Scotland
    Posts
    4,836
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    i just had the pleasure of writing some ASP for a rather large database, well, 350,000 records to be infact. I used AccessXP, which handled it no problem

  4. #4
    SitePoint Addict kevin_tremblay's Avatar
    Join Date
    Jul 2001
    Location
    Boston Area (North shore)
    Posts
    233
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    SQL would be a great solution for your client but it is not a cheap solution. But if they were to goto SQL then your growth problems would never be an issue.

    I use access for small stuff but anything over about 15,000 records I would go with SQL.

    Just my suggestion.

    Kevin -- Digitalman
    Kevin Tremblay-- Sys Admin
    work: kevin_tremblay@hsgmed.com
    "The object of the journey is not to arrive."

  5. #5
    Just Blow It bronze trophy
    DaveMaxwell's Avatar
    Join Date
    Nov 1999
    Location
    Mechanicsburg, PA
    Posts
    7,264
    Mentioned
    115 Post(s)
    Tagged
    1 Thread(s)
    The size of the database doesn't really matter. It's the number of CONCURRENT connections which does....
    Dave Maxwell - Manage Your Site Team Leader
    My favorite YouTube Video! | Star Wars, Dr Suess Style
    Learn how to be ready for The Forums' Move to Discourse

  6. #6
    SitePoint Addict kevin_tremblay's Avatar
    Join Date
    Jul 2001
    Location
    Boston Area (North shore)
    Posts
    233
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    agreed concurrent connections is the thing to worry about.

    Kevin -- Digitalman
    Kevin Tremblay-- Sys Admin
    work: kevin_tremblay@hsgmed.com
    "The object of the journey is not to arrive."

  7. #7
    SitePoint Addict ownersite's Avatar
    Join Date
    Jul 2001
    Posts
    222
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Relational table design and use of indexes are also important with this many records in an Access database (as far as performance of retrieval of data)...and don't forget a backup strategy.
    F150online- 102,000 users strong and growing...
    Ownersite.com
    - tools to enhance vehicle ownership

  8. #8
    SitePoint Enthusiast hendo's Avatar
    Join Date
    Jun 2001
    Location
    Australia
    Posts
    53
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Why not use MySQL?

    It way better than Access with respect to scalability and best of all....FREE!

    I prefer it as a cost effective 1/2 way between Access and SQL Server.

    hendo
    Steve 'Hendo' Henderson
    EnVivo!CS: Fast and Affordable Web Content Management for ASP. 100% Script, No DLLs.
    www.netsystemsco.com

  9. #9
    SitePoint Member timbo's Avatar
    Join Date
    Jul 2001
    Location
    Derbyshire, UK
    Posts
    5
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I don't think the concurrent number of users should be a problem so hopefully Access may be OK. If the client decided however to upgrade to MySQL is it relatively painless and safe to leave the Microsoft "stable"

    Timbo

  10. #10
    SitePoint Zealot
    Join Date
    Jun 2000
    Location
    Yeppoon, Australia
    Posts
    186
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    The number of concurrent users is the problem with using access, the jet engine can't handle a big demand - I have heard of some people getting quite a few connections without major problems as long as the underlying schema of the database was very, very good.
    Knowledge is knowing that a tomatoe is a fruit; wisdom is not putting it in a fruit salad.


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •