Re: Changing from an Access DB
From: Jon (js_at_roksteady.net)
Date: 03/08/04
- Next message: Jim: "RE: Applying a theme"
- Previous message: Steve Easton: "Re: 2000 error "An error occurred accessing your frontpage web files...""
- In reply to: Thomas A. Rowe: "Re: Changing from an Access DB"
- Next in thread: Thomas A. Rowe: "Re: Changing from an Access DB"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 8 Mar 2004 14:05:31 -0000
OK - a week would be long enough to draw conclusions though. Must admit I
was surprised that Access could handle that kind of load consistently.
Jon
Thomas A. Rowe wrote:
> Jon,
>
> Actually it is one of my client's sites, and that was only for 1 week
> and now traffic is back to normal, however it did prove that Access
> could handle the demand.
>
>
> "Jon" <js@roksteady.net> wrote in message
> news:%23bbtymJBEHA.624@TK2MSFTNGP10.phx.gbl...
>> I hear you. Try searching the web or newsgroups to find the answer
>> to the question when should you upgrade from Access. You'll find
>> answers ranging from Access isnt even good for a personal site to
>> Tom Rowe running 6000 users an hour (and presumably getting rich :-)
>> on Access.
>>
>> It's going to come down to money - ask your host the cost to upgrade
>> to SQL Server and then ask if your site(s) can justify the cost. If
>> you can justify the expense SQL Server will prove itself worthwhile,
>> the only reason to stick with Access is because your site can't
>> justify the cost of sql server.
>>
>> Look at it this way - when should you upgrade your car? If your car
>> isn't fast enough/roomy enough/reliable enough for your business
>> needs then of course you have to upgrade now. If you car meets your
>> needs now but business is good, will get better over the next few
>> months and you'd like a better way to get from a to b then you'd be
>> tempted to upgrade now anyway.
>>
>> Whoever you ask there really isn't a "scientific" answer to this
>> question.
>>
>> Jon
>>
>>
>> sleepin wrote:
>>> Hi Jon,
>>> Thanks for your reply but how can someone plan for when to change?
>>> Somehow the decision has to be based on either the amount of data
>>> being requested, the number of hits per page or site, or download
>>> time being experienced by visitors. Can't this be quantified?
>>>
>>> We're dealing with computers here and even a grocery store can weigh
>>> your fruit before you make a purchase.
>>>
>>>
>>> "Jon" <js@roksteady.net> wrote in message
>>> news:%236FKHHJBEHA.1796@TK2MSFTNGP12.phx.gbl...
>>>> Hi,
>>>> It's probably most dependant on your budget, Access has one (and
>>>> only one) thing going for it - it's cheap. There's no definitive
>>>> answer, even from Microsoft themselves, as to how much traffic
>>>> Access can take. You'd probably have to make your own decision
>>>> along the lines of is my site is generating enough revenue to
>>>> cover the extra cost of SQL Server and is it important to me (or
>>>> my client) to know that my site will stay up 24/7. If the answer
>>>> to both is yes it's probably time to upgrade.
>>>>
>>>> Jon
>>>> Microsoft MVP - FP
>>>>
>>>>
>>>> sleepin wrote:
>>>>> When does it become necessary to change from an Acess db to
>>>>> something else? As an example, a tutorial I found said:
>>>>>
>>>>> "when your site becomes very popular and its requirements outgrow
>>>>> the capabilities that Access offers."
>>>>>
>>>>> Is this dependent of the total number of hits the site receives,
>>>>> the total number of concurrent hits, or is it dependent on the
>>>>> total number of page hits or the total number of concurrent page
>>>>> hits? Or is there some other criteria? Thanks.
>>>>>
>>>>> Sign me,
>>>>>
>>>>> Confused
- Next message: Jim: "RE: Applying a theme"
- Previous message: Steve Easton: "Re: 2000 error "An error occurred accessing your frontpage web files...""
- In reply to: Thomas A. Rowe: "Re: Changing from an Access DB"
- Next in thread: Thomas A. Rowe: "Re: Changing from an Access DB"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
