User Tools

Site Tools


faq:dbsize

Database Size

Size Limits

What is the maximum size of a Pedigree database?

There are two limits, which apply individually to each record-type in a Pedigree Database (Person, Marriage, Source…). Firstly, the maximum number of records is 32767, including any records deleted in the current session.

Secondly, the maximum size of the data file (Person.dat, Marriage.dat….) is 1Mb in a standard Pedigree database. Where this size is approached, then for PediTree, or Pedigree versions 2.6d 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 only has even larger options: jumbo up to 6Mb; massive up to 9Mb.

These options allocate file-space in larger chunks: the standard database allocates in 16-byte chunks; large in 48-byte chunks; huge in 64-byte chunks. The consequence is that on average each record takes more space, so that changing to larger versions will usually increase the size of an existing file, before any new information is added. An article in the PUG Newsletter Vol.7 No.3 p.14 gives further details.

Before deciding to move to a larger version, it may be worth reorganising the existing database to eliminate spare space, including that taken by any deleted records. If you are close to the size limit, but are no longer making substantial additions to your database, this may be sufficient.

Reorganising Databases

There are two ways to reorganise a database:

  1. Use the Reorganise function in the Database Utilities program.
  2. Create a new database containing the same information. There are three steps:
    1. Export your existing database as a GEDCOM file.
    2. Create a new empty database from your existing database.
    3. Import the GEDCOM file and create the indexes.

See Using GEDCOM Files for more information on GEDCOM Export/Import.

Moving to Larger Versions

Using the Database Utility

See Pedigree Database Utility for details.

Using PediTree

  1. Export your existing database as a GEDCOM 4 Pedigree file.
  2. Create a new empty database from your existing database. You can choose from five different maximum sizes from 1Mb (standard) up to 9Mb.
  3. Import the GEDCOM file.

Using Pedigree

  1. Export your existing database as a GEDCOM file.
  2. Create a new empty database from your existing database. </li>
  3. Convert the empty database to the large (or huge) format.
  4. Arrange for Pedigree to run it large or huge mode.
  5. Import the GEDCOM file and create the indexes.

Step 3 involves renaming the new empty database. Standard Pedigree databases are named e.g. foo.ped - the filetype PED denotes the standard version. Large databases have filetype PDG, e.g. foo.pdg; huge databases have filetype PDH, e.g. foo.pdh. The procedure is set out below.

After creating the new empty database, exit Pedigree. Using Windows Explorer (press Start+E), navigate to the folder containing the new empty database and click on the folder (e.g. foo.ped) to select it. Pause, then click again to select the name of the folder (or press key F2), edit the filetype to pdg or pdh as required and press the Enter key to finish.

For step 4, you need to create a new shortcut to Pedigree. First start Windows Explorer (press Start+E), find the Pedigree folder and click on it to open it.

Look in the right-hand pane for file Pedigree.exe. If the .exe doesn't show, then there will be several entries called Pedigree; look for the one of type 'Application'. Click on this icon, hold down the left mouse button and drag it onto the desktop visible behind the Explorer window. Release the mouse button, thus creating a shortcut titled Shortcut to Pedigree.

Press F2 and edit this title to Pedigree (large) (or Pedigree (huge)), press Enter to finish.

Right-click, choose Properties, choose the Program tab and edit the command line to add /large for a large database (as opposite), /huge for a huge database. Click OK.
faq/dbsize.txt · Last modified: 2018/08/30 00:19 by 127.0.0.1

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki