Re: small data needed - suggestions?

Sorry, I mispoke.

One db per person would be too much.

Look at my blog...and you could easily start with 1 db.
And then use the Factory method to even use multiple Access(Jet) database
files (.mdb).
Like use the key system, and base it on the person's first letter of their
last name.

THe factory pattern gives you options.

A-I (obituarydb1.mdb)
J-R(obituarydb2.mdb)
S-Z(obituarydb3.mdb)

or start with 1 .mdb and only go to N .mdb's if you need to.




"sloan" <sloan@xxxxxxxxx> wrote in message
news:%23X$8WIhfIHA.3724@xxxxxxxxxxxxxxxxxxxxxxx

1 per minute??

Just not an overloaded amount of simutaneous writes.

Since this is a web app (I'm assuming)...then the web server talking to an
Access(JET) database locally..is not that big of a deal.

Access can handle a light load of 5-10 simutanaeous users in my opinion.

Your obituary thing...if you have 1 db per deceased person....would be
fine for this imho.

...




"Bobby Edward" <test@xxxxxxxx> wrote in message
news:egWJ$DhfIHA.5260@xxxxxxxxxxxxxxxxxxxxxxx
In your opinion what is "RARE" writes? 5 or less concurrent?

"sloan" <sloan@xxxxxxxxx> wrote in message
news:OwuaUAhfIHA.5620@xxxxxxxxxxxxxxxxxxxxxxx

For something with RARE writes...and many reads..you can get by with
either

Access (Jet) (.mdb)
or
SqLite


I'm working on a prototype using the FActory Pattern and supporting
multiple RDBMS.

Go here
http://sholliday.spaces.live.com/Blog/
or
http://sholliday.spaces.live.com/Blog/feed.rss

(search for "multiple rdbms")

and if I don't have it up yet...email me and I'll send you a copy.




"Bobby Edward" <test@xxxxxxxx> wrote in message
news:%23p9PH%23gfIHA.1184@xxxxxxxxxxxxxxxxxxxxxxx
I am doing a funeral home page (depressing huh?) :)

They want an obituary page where people can post comments. So, in my
db I have 2 tables (1 to many relationship)...
TABLE1: Obituary (persons info)
TABLE2: ObitComments ("many" table - comments)

There would be an admin page to approve or reject comments, manage
obituaries, etc...

My ISP only allows me a certain # of SQL Server dbs. I would hate to
"waste" one on a small project like this. Any suggestions? How would
you handle it? SQL Express is not supported either.

Thanks!









.

Relevant Pages

  • Re: Tying and soldering explained 1898
    ... Peterson has a remarkable photo of multiple Pope's lined up outside ... the factory. ...
    (rec.bicycles.tech)
  • Re: TreeSet and HashSet
    ... Lew wrote: ... where the first leaves you with multiple copies. ... In every case I can think of, it's pretty easy to make a factory or FooSet ... cares whether the Set interface has this method or the factory just keeps a ...
    (comp.lang.java.programmer)
  • Re: small data needed - suggestions?
    ... And then use the Factory method to even use multiple Accessdatabase ... obituaries, etc... ... My ISP only allows me a certain # of SQL Server dbs. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: small data needed - suggestions?
    ... And then use the Factory method to even use multiple Accessdatabase ... THe factory pattern gives you options. ... obituaries, etc... ... My ISP only allows me a certain # of SQL Server dbs. ...
    (microsoft.public.dotnet.framework.aspnet)