User Tools

Site Tools


faq:dbsize

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
faq:dbsize [2013/04/01 18:40] – [Reorganising Databases] Colin Liebenroodfaq:dbsize [2018/08/30 00:19] (current) – external edit 127.0.0.1
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 //Newsletter// before any new information is added. An article in the PUG //Newsletter//
- 
 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 68: Line 40:
 There are two ways to reorganise a database: There are two ways to reorganise a database:
  
-  - Use the Reorganise function in the [[faq:utilities/dbutil|Database Utilities]] program. +  - Use the Reorganise function in the [[utilities/dbutil|Database Utilities]] program.
   - 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:GEDCOM|Using GEDCOM Files]] for more information on GEDCOM Export/Import.
-See [[faq:GEDCOM|Using GEDCOM Files]] for +
-ore information on GEDCOM Export/Import.+
  
 ==== Moving to Larger Versions ==== ==== Moving to Larger Versions ====
  
 +=== Using the Database Utility ===
 +See [[utilities:dbutil|Pedigree Database Utility]] for details.
 === Using PediTree === === Using PediTree ===
  
   - Export your existing database as a //GEDCOM 4 Pedigree// file.   - Export your existing database as a //GEDCOM 4 Pedigree// file.
- 
   - Create a new empty database from your existing database. You can choose from five different maximum sizes from 1Mb (standard) up to 9Mb.   - Create a new empty database from your existing database. You can choose from five different maximum sizes from 1Mb (standard) up to 9Mb.
- 
   - Import the GEDCOM file.   - Import the GEDCOM file.
  
Line 98: Line 64:
  
   - 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. </li>   - Create a new empty database from your existing database. </li>
- 
   - Convert the empty database to the large (or huge) format.   - Convert the empty database to the large (or huge) format.
- 
   - Arrange for Pedigree to run it large or huge mode.   - Arrange for Pedigree to run it large or huge mode.
- 
   - Import the GEDCOM file and create the indexes.   - 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 - 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 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. 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. | {{faq:rename.gif}} | | 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. | {{faq:rename.gif}} |
- 
- 
  
 For step 4, you need to create a new shortcut to Pedigree. 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 First start Windows Explorer (press **Start**+**E**), find the Pedigree folder and click
- 
 on it to open it. 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 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 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**. 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 Press F2 and edit this title to **Pedigree (large)** (or **Pedigree (huge)**), press
- 
 Enter to finish. 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:pedlarge.gif}}| | 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:pedlarge.gif}}|
- 
  
  
  
faq/dbsize.1364834429.txt.gz · Last modified: 2018/08/30 00:09 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki