The only time I have seen a database copy corrupt both the copy and the
original db is on another database platform that uses a log file to
store transactions. I guess both the copy and the original db try to
write to the same log file and also apply any changes to the log file
back to the db... It seems to get confused and blows up both dbs. This
happens to us with Sybase SQLAnywhere...

-steve

On Wed, 2005-06-15 at 21:20 +0200, Martijn Tonies wrote:

> From: "Ann W. Harrison"
> > Martijn Tonies wrote:
> > >
> > > For one, copying a database while it's in use or while the
> Firebird
> service
> > > process is active can cause a corrupt copy AND a corrupt
> original!!
> Never
> > > do this.
> > >
> >
> > Copying can products a corrupt copy, and copying the copy back over
> the
> > original will produce a mess, but to the best of my understanding (a
> > large caveat) file copy programs will not damage the original or
> affect
> > concurrent actions on the database.
>
> Hmm - I do believe I got this from you or Helen though :-)
>
> With regards,
>
> Martijn Tonies
> Database Workbench - tool for InterBase, Firebird, MySQL, Oracle & MS
> SQL
> Server
> Upscene Productions
> http://www.upscene.com
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>
>


[Non-text portions of this message have been removed]