Derek Roscoe wrote:
> Knut, hi!
>
> Thanks for the response and help. I truly appreciate it. Would you feel
> the same way if it were a public website with thousands of users?
Hi Derek,
When you say thousands of users, how many of these are concurrent users?
I think I would still go for the embedded driver, unless you are running
very resource intensive queries against the database that would take up
too much of the application/web server's resources. If the database is
only going to handle login information, I wouldn't be worried.
In any case, in most cases you should be able to easily switch to the
client driver later if that is required for some reason.
Regards,
--
Kristian
> Thanks
> again for your time!
>
> ____________________________________________________________________________
> _______________________
> DEREK J ROSCOE l director l 1500 bull lea road - suite 110 l lexington,
> kentucky 40511-1267 usa
> d: 859.243.5734 l o: 859.243.5730 l f: 800.548.6829 l e:
>
derek.roscoe@...
>
>
>
>
> -----Original Message-----
> From:
Knut.Hatlen@... [mailto:
Knut.Hatlen@...]
> Sent: Monday, June 08, 2009 8:05 AM
> To: Derby Discussion
> Subject: Re: DERBY 10.5 | Embedded vs Server Based
>
> Derek J Roscoe <
derek.roscoe@...> writes:
>
>
>> Hello,
>>
>> I am new to derby and database creation all together. I want to know with
>> method of Derby I should set up Embedded or Server Based. I am setting up
>>
> a
>
>> website where users will be filling out a form that will submit the
>>
> database
>
>> information to be stored about each and every user (username, password,
>> demographics, etc.). The submission form(s) will be dynamic pages created
>>
> in
>
>> Dreamweaver, which will then be read by ColdFusion before being displayed
>>
> to
>
>> those ultimately accessing the information.
>>
>
> Hi Derek,
>
> If the database is only accessed by a single process, which I think is
> the case here, I'd probably go for embedded since it's easier to set up
> and has less overhead.
>
>