small data needed - suggestions?

[Bobby Edward]

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!

 

[sloan]

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]

In your opinion what is "RARE" writes? 5 or less concurrent?

 

[sloan]

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.

....

 

[Mark Rae [MVP]]

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.

In addition to Sloan's comments, what's stopping you creating the two tables
you suggest in an existing SQL Server database...?

 

[Bobby Edward]

To be honest, I like the simplicity of having the data in 1 file, an mdb.
It's easy to backup and move around. I'm a small fry developer.

 

[Bobby Edward]

1 db per deceased person? Or 1 db record?

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.

...

 

[sloan]

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.

 

[Bobby Edward]

hmmm i never heard of the factory method - i must read up on it - THANKS
SLOAN!!!!

 

[Mark Rae [MVP]]

To be honest, I like the simplicity of having the data in 1 file, an mdb.
It's easy to backup and move around.

Er, OK...

 

[sloan]

I have a blog entry that is ~just~ about the Simple Factory pattern as well.

http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!126.entry

 

[Jeff Dillon]

Or store it in a xml file

Er, OK...