From: "Robert Comer" 

> The other side of the coin is your database file is going to be absolutely
> huge, it's going to be more difficult to backup the largest section of the
> data (the calls) and so the db will need to be shut down for a longer
backup
> period, ...

That sounds like a very real concern to me.

>and if Mr "I'll just move the database" comes around again it's very
> easy for him to wipe out the calls by accident again.

Always have backups. 

- Bob Comer



"Geo."  wrote in message
news:3e0af25e$1{at}w3.nls.net...
> "Ellen K."  wrote in message
> news:8srk0v4phqn9k6g5n3rur3pphlpms5q91q{at}4ax.com...
>
> > for them.  Recordings for any "sale" that has not been
delivered within
> > 30 days of the first recording will be deleted, everything else will be
> > kept.   Handling this last point is obviously simpler when the sound
> > files are right in the database.
>
> I think I understand what you are saying but OS commands like "del
filename"
> can be passed to the OS from sql server as well so I don't think it's that
> much simpler. It will simplify security for the sound recordings though.
>
> The other side of the coin is your database file is going to be absolutely
> huge, it's going to be more difficult to backup the largest section of the
> data (the calls) and so the db will need to be shut down for a longer
backup
> period, and if Mr "I'll just move the database" comes around
again it's
very
> easy for him to wipe out the calls by accident again.
>
> I'm just curious why you do it this way, whenever I see an image db
program
> it always stores the images separately from the db, I figure this is
similar
> so I'm trying to understand all the advantages to storing the vast bulk of
> the data (images, sounds, whatever) in the database itself.
>
> Geo.
>
>

--- BBBS/NT v4.01 Flag-4