Re: Access backend database speed issues with DRW
From: Kevin Spencer (kevin_at_takempis.com)
Date: 02/23/04
- Next message: DBarker: "Shared Borders Problem"
- Previous message: Kevin Spencer: "Re: Access backend database speed issues with DRW"
- In reply to: skc: "Re: Access backend database speed issues with DRW"
- Next in thread: Thomas A. Rowe: "Re: Access backend database speed issues with DRW"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 23 Feb 2004 10:57:25 -0500
> is it worth having SQL server for a table with 60 records?
It's not a matter of how many records you're fetching that would determine
whether you want to use SQL Server or not. It's a matter of speed, and
especially how many concurrent users you expect to be connected. My guess
would be, Access will be fine for now. Again, after your feedback, I believe
the issue is simply the number and total size of the image files being
downloaded.
-- HTH, Kevin Spencer .Net Developer Microsoft MVP Big things are made up of lots of little things. "skc" <anonymous@discussions.microsoft.com> wrote in message news:14ff901c3fa20$ae158810$a401280a@phx.gbl... > is it worth having SQL server for a table with 60 records? > > if I had a table with 60,000 records, then it is a > different matter. > > skc > > >-----Original Message----- > >Another possibility is your use of Access as your > database back-end. Access > >is a desktop product, and not designed for Internet use. > While it can be > >used on the Internet with relatively small numbers of > concurrently-connected > >clients, it is not optimal. A database server such as SQL > Server will > >improve performance tremendously. > > > >-- > >HTH, > >Kevin Spencer > >..Net Developer > >Microsoft MVP > >Big things are made up > >of lots of little things. > > > >"skc" <anonymous@discussions.microsoft.com> wrote in > message > >news:143ba01c3fa12$0cc4df50$a101280a@phx.gbl... > >> Hi, > >> > >> I have made a website using FP2K and Access2K as a > backend > >> database to the site using the FP2K DRW. > >> > >> At the moment, I am trying to resolve a speed issue. Go > >> to www.maslenmotors.com, and click the Showroom tab and > >> click View All Cars using Broadband connection. > >> > >> You will find that the page takes absolutely ages to > >> download to a web browser. I am interrogating the > >> database by using three (or four) parameters such as: > >> Make, Age, Price and I have indexed these fields in my > >> Access2K table, by toggling the Indexed (Duplicates OK) > >> fields. > >> > >> Please can someone offer me advice on how to speed up > the > >> access. Is it my indexing, or are the pictures and DRW > >> not a good idea? In which case, how do other people do > it? > >> > >> Please help. > >> > >> Skc > > > > > >. > >
- Next message: DBarker: "Shared Borders Problem"
- Previous message: Kevin Spencer: "Re: Access backend database speed issues with DRW"
- In reply to: skc: "Re: Access backend database speed issues with DRW"
- Next in thread: Thomas A. Rowe: "Re: Access backend database speed issues with DRW"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|