faq:dbsize
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
faq:dbsize [2013/04/01 18:40] – [Reorganising Databases] Colin Liebenrood | faq:dbsize [2013/04/01 18:46] – [Reorganising Databases] Colin Liebenrood | ||
---|---|---|---|
Line 4: | Line 4: | ||
==== Size Limits ==== | ==== Size Limits ==== | ||
- | |||
//What is the maximum size of a Pedigree database? // | //What is the maximum size of a Pedigree database? // | ||
- | |||
There are two limits, which apply individually to each record-type | There are two limits, which apply individually to each record-type | ||
- | |||
in a Pedigree Database (Person, Marriage, Source...). Firstly, | in a Pedigree Database (Person, Marriage, Source...). Firstly, | ||
- | |||
the maximum number of records is 32767, including any records deleted | the maximum number of records is 32767, including any records deleted | ||
- | |||
in the current session. | in the current session. | ||
- | |||
- | |||
Secondly, the maximum size of the data file (Person.dat, | Secondly, the maximum size of the data file (Person.dat, | ||
- | |||
Marriage.dat....) is 1Mb in a standard Pedigree database. Where | Marriage.dat....) is 1Mb in a standard Pedigree database. Where | ||
- | |||
this size is approached, then for PediTree, or Pedigree versions 2.6d | this size is approached, then for PediTree, or Pedigree versions 2.6d | ||
- | |||
or later, there are other options: a //large// database can be up | or later, there are other options: a //large// database can be up | ||
- | |||
to 3Mb; a //huge// database up to 4Mb (Pedigree version 2.6j or later). PediTree | to 3Mb; a //huge// database up to 4Mb (Pedigree version 2.6j or later). PediTree | ||
- | |||
only has even larger options: //jumbo// up to 6Mb; //massive// up to 9Mb. | only has even larger options: //jumbo// up to 6Mb; //massive// up to 9Mb. | ||
- | |||
These options allocate file-space in larger chunks: the | These options allocate file-space in larger chunks: the | ||
- | |||
standard database allocates in 16-byte chunks; //large// in 48-byte | standard database allocates in 16-byte chunks; //large// in 48-byte | ||
- | |||
chunks; //huge// in 64-byte chunks. The consequence is that on | chunks; //huge// in 64-byte chunks. The consequence is that on | ||
- | |||
average each record takes more space, so that changing to larger versions | average each record takes more space, so that changing to larger versions | ||
- | |||
will usually increase the size of an existing file, | will usually increase the size of an existing file, | ||
- | |||
before any new information is added. An article in the PUG // | before any new information is added. An article in the PUG // | ||
- | |||
Vol.7 No.3 p.14 gives further details. | Vol.7 No.3 p.14 gives further details. | ||
- | |||
- | |||
Before deciding to move to a larger version, it may be | Before deciding to move to a larger version, it may be | ||
- | |||
worth reorganising the existing database to eliminate spare space, | worth reorganising the existing database to eliminate spare space, | ||
- | |||
including that taken by any deleted records. If you are close to | including that taken by any deleted records. If you are close to | ||
- | |||
the size limit, but are no longer making substantial additions to | the size limit, but are no longer making substantial additions to | ||
- | + | your database, this may be sufficient. | |
- | your datab | + | |
- | ase, this may be sufficient. | + | |
- | + | ||
==== Reorganising Databases ==== | ==== Reorganising Databases ==== | ||
Line 69: | Line 41: | ||
- Use the Reorganise function in the [[faq: | - Use the Reorganise function in the [[faq: | ||
- | |||
- Create a new database containing the same information. There are three steps: | - Create a new database containing the same information. There are three steps: | ||
- | |||
- Export your existing database as a GEDCOM file. | - Export your existing database as a GEDCOM file. | ||
- | |||
- Create a new empty database from your existing database. | - Create a new empty database from your existing database. | ||
- | |||
- Import the GEDCOM file and create the indexes. | - Import the GEDCOM file and create the indexes. | ||
- | + | See [[faq: | |
- | See [[faq: | + | |
- | ore information on GEDCOM Export/ | + | |
==== Moving to Larger Versions ==== | ==== Moving to Larger Versions ==== |
faq/dbsize.txt · Last modified: 2018/08/30 00:19 by 127.0.0.1