Subject | Re: Data Loss in Windows Vista |
---|---|
Author | Adam |
Post date | 2008-10-15T11:54:24Z |
--- In firebird-support@yahoogroups.com, "bogdan" <bogdan@...> wrote:
only used for read only databases because there is no point setting
aside room for updated records if it is impossible to update records.
anything because there would be less pages to read from disk, but the
moment you go to update a record the engine has to set up and possibly
request from the OS space for a new data page.
Adam
>Whilst it could be employed to conserve disk space, it is normally
> > Database header page information:
> > Flags 0
> > Checksum 12345
> > Generation 84490
> > Page size 4096
> > ODS version 10.1
> > Oldest transaction 81692
> > Oldest active 84481
> > Oldest snapshot 84481
> > Next transaction 84482
> > Bumped transaction 1
> > Sequence number 0
> > Next attachment ID 0
> > Implementation ID 16
> > Shadow count 0
> > Page buffers 0
> > Next header page 0
> > Database dialect 3
> > Creation date Feb 8, 2008 9:00:35
> > Attributes force write, no reserve
> >
>
> >I give in,... what's 'no reserve'
> >Alan
>
> AFAIK - it is used for systems with limited amount of space available.
only used for read only databases because there is no point setting
aside room for updated records if it is impossible to update records.
> Pages are filled near 100%.Probably the other way around. Loading speed would be quicker if
>
> Never to use for production databases.
> Data loading is extremely slow
anything because there would be less pages to read from disk, but the
moment you go to update a record the engine has to set up and possibly
request from the OS space for a new data page.
Adam