Difference between revisions of "Create Forest Database"

From Heureka Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
A "Restore"-procedure executed in SQL Server Management Studio to create a local forest database is described [[Install_SQL_Server_Express|here]]. A corresponding functionality is now available in PlanStart. In both cases the SQL Server software needs to be installed on the computer, while the built-in functionality seems to be compatible only with SQL Server 2005.
 
A "Restore"-procedure executed in SQL Server Management Studio to create a local forest database is described [[Install_SQL_Server_Express|here]]. A corresponding functionality is now available in PlanStart. In both cases the SQL Server software needs to be installed on the computer, while the built-in functionality seems to be compatible only with SQL Server 2005.
  
In menu "External data" > "Import FMPP data...":
+
In menu "Tools" > "Create Forest Database":
  
#"Browse..." to the catalogue on your computer holding the four basic files.
+
#"Browse..." to the catalogue on your computer holding the backup-file of a forest database. If you are missing such file, contact a Heureka administrator (usually, available on a ftp-server).
#Set the additional information necessary.
+
#In "Settings..." you give the additional information necessary, e.g. "LOCALHOST" or "LOCALHOST\SQLEXPRESS", depending on the installed SQL Server.
#Link to an existing analysis area or create a new (namned in "Description").
+
#Press "Create database" and wait (might take a while, depending on the size of the database-backup.  
#Press "Ok".  
 
 
   
 
   
Data is checked for errors in the FMPP. Additional variables could have been estimated in the field inventory (maybe variables useful in analyses with the Heureka system).
+
Now you should have a local forest database. This might be empty or with some testdata already imported. There are several possibilities to import new data and set up an analysis area of your own. Read more about this in other parts of the [[PlanStart User's Guide]]
  
 
*'''Note'''
 
*'''Note'''
 
:Be careful when using imputed plot data/simulated single tree-data based on a stand register of uncertain quality. Any systematic errors here will comply and might even grow with the prognoses, with negative impact on the planning result's reliability. In strategic planning, this carefulness should increase with the length of the planning period.
 
:Be careful when using imputed plot data/simulated single tree-data based on a stand register of uncertain quality. Any systematic errors here will comply and might even grow with the prognoses, with negative impact on the planning result's reliability. In strategic planning, this carefulness should increase with the length of the planning period.

Revision as of 08:58, 11 September 2009

A "Restore"-procedure executed in SQL Server Management Studio to create a local forest database is described here. A corresponding functionality is now available in PlanStart. In both cases the SQL Server software needs to be installed on the computer, while the built-in functionality seems to be compatible only with SQL Server 2005.

In menu "Tools" > "Create Forest Database":

  1. "Browse..." to the catalogue on your computer holding the backup-file of a forest database. If you are missing such file, contact a Heureka administrator (usually, available on a ftp-server).
  2. In "Settings..." you give the additional information necessary, e.g. "LOCALHOST" or "LOCALHOST\SQLEXPRESS", depending on the installed SQL Server.
  3. Press "Create database" and wait (might take a while, depending on the size of the database-backup.

Now you should have a local forest database. This might be empty or with some testdata already imported. There are several possibilities to import new data and set up an analysis area of your own. Read more about this in other parts of the PlanStart User's Guide

  • Note
Be careful when using imputed plot data/simulated single tree-data based on a stand register of uncertain quality. Any systematic errors here will comply and might even grow with the prognoses, with negative impact on the planning result's reliability. In strategic planning, this carefulness should increase with the length of the planning period.