Remove data - Revision history

Hah at 05:41, 14 September 2009

2009-09-14T05:41:04Z

Hah at 05:39, 14 September 2009

2009-09-14T05:39:54Z

Hah at 05:38, 14 September 2009

2009-09-14T05:38:24Z

Hah at 13:03, 11 September 2009

2009-09-11T13:03:22Z

Hah at 13:02, 11 September 2009

2009-09-11T13:02:13Z

Hah at 11:56, 11 September 2009

2009-09-11T11:56:39Z

Hah: New page: You should clean up your databases, especially your local forest database might become quite full of redundant data. The result databases... Look in "Project..."!

2009-09-09T14:39:25Z

New page: You should clean up your databases, especially your local forest database might become quite full of redundant data. The result databases... Look in "Project..."!

New page

You should clean up your databases, especially your local forest database might become quite full of redundant data. The result databases... Look in "Project..."!

← Older revision		Revision as of 05:41, 14 September 2009
Line 1:		Line 1:
	You should clean up your forest databases, as described [[Delete_a_Project\|here]], unless you are done with all analyses and ready to delete the entire database (then use the SQL Server Management Studio).		You should clean up your forest databases, as described [[Delete_a_Project\|here]], unless you are done with all analyses and ready to delete the entire database (then use the SQL Server Management Studio).

−	Since result databases are created by the system (storing results from simulations and optimizations), the simple solution is to delete the database and create a new one. Partial removal of results is done in PlanWise and can be of interest, e.g., when data from analyses within the same project should be saved in the same database (and, when using SQL Server Express, maximum size of a database ~~currently~~ is 4 GB).	+	Since result databases are created by the system (storing results from simulations and optimizations), the simple solution is to delete the database and create a new one. Partial removal of results is done in PlanWise and can be of interest, e.g., when data from analyses within the same project should be saved in the same database (and, when using SQL Server Express, maximum size of a database is limited to 4 GB).

← Older revision		Revision as of 05:39, 14 September 2009
Line 1:		Line 1:
−	You should clean up your forest databases, described [[Delete_a_Project\|here]], unless you are done with all analyses and ready to delete the entire database (then use the SQL Server Management Studio).	+	You should clean up your forest databases, as described [[Delete_a_Project\|here]], unless you are done with all analyses and ready to delete the entire database (then use the SQL Server Management Studio).

	Since result databases are created by the system (storing results from simulations and optimizations), the simple solution is to delete the database and create a new one. Partial removal of results is done in PlanWise and can be of interest, e.g., when data from analyses within the same project should be saved in the same database (and, when using SQL Server Express, maximum size of a database currently is 4 GB).		Since result databases are created by the system (storing results from simulations and optimizations), the simple solution is to delete the database and create a new one. Partial removal of results is done in PlanWise and can be of interest, e.g., when data from analyses within the same project should be saved in the same database (and, when using SQL Server Express, maximum size of a database currently is 4 GB).

← Older revision		Revision as of 05:38, 14 September 2009
Line 1:		Line 1:
	You should clean up your forest databases, described [[Delete_a_Project\|here]], unless you are done with all analyses and ready to delete the entire database (then use the SQL Server Management Studio).		You should clean up your forest databases, described [[Delete_a_Project\|here]], unless you are done with all analyses and ready to delete the entire database (then use the SQL Server Management Studio).

−	Since result databases are created by the system (storing results from simulations and optimizations), the simple solution is to delete the database and create a new one. Partial removal of results is done in PlanWise and can be of interest, e.g., when data from analyses within the same project should be saved in the same database (and, when using SQL Server Express, maximum size of a database is 4 GB).	+	Since result databases are created by the system (storing results from simulations and optimizations), the simple solution is to delete the database and create a new one. Partial removal of results is done in PlanWise and can be of interest, e.g., when data from analyses within the same project should be saved in the same database (and, when using SQL Server Express, maximum size of a database currently is 4 GB).

← Older revision		Revision as of 13:03, 11 September 2009
Line 1:		Line 1:
	You should clean up your forest databases, described [[Delete_a_Project\|here]], unless you are done with all analyses and ready to delete the entire database (then use the SQL Server Management Studio).		You should clean up your forest databases, described [[Delete_a_Project\|here]], unless you are done with all analyses and ready to delete the entire database (then use the SQL Server Management Studio).

−	Since result databases are created by the system (storing results from simulations and optimizations), the simple ~~way~~ is to delete the database and create a new one. Partial removal of results is done in PlanWise and can be of interest, e.g., when data from analyses within the same project should be saved in the same database (and, when using SQL Server Express, maximum size of a database is 4 GB).	+	Since result databases are created by the system (storing results from simulations and optimizations), the simple solution is to delete the database and create a new one. Partial removal of results is done in PlanWise and can be of interest, e.g., when data from analyses within the same project should be saved in the same database (and, when using SQL Server Express, maximum size of a database is 4 GB).

← Older revision		Revision as of 13:02, 11 September 2009
Line 1:		Line 1:
	You should clean up your forest databases, described [[Delete_a_Project\|here]], unless you are done with all analyses and ready to delete the entire database (then use the SQL Server Management Studio).		You should clean up your forest databases, described [[Delete_a_Project\|here]], unless you are done with all analyses and ready to delete the entire database (then use the SQL Server Management Studio).

−	Since result databases are created by the system (~~to save~~ results from simulations and optimizations), it is ~~usually best~~ to delete ~~especially your local forest~~ database ~~might become quite full~~ of ~~redundant data~~. ~~The result databases~~.~~.. Look~~ in ~~"Project..~~."!	+	Since result databases are created by the system (storing results from simulations and optimizations), the simple way is to delete the database and create a new one. Partial removal of results is done in PlanWise and can be of interest, e.g., when data from analyses within the same project should be saved in the same database (and, when using SQL Server Express, maximum size of a database is 4 GB).

← Older revision		Revision as of 11:56, 11 September 2009
Line 1:		Line 1:
−	You should clean up your databases, especially your local forest database might become quite full of redundant data. The result databases... Look in "Project..."!	+	You should clean up your forest databases, described [[Delete_a_Project\|here]], unless you are done with all analyses and ready to delete the entire database (then use the SQL Server Management Studio).
		+
		+	Since result databases are created by the system (to save results from simulations and optimizations), it is usually best to delete especially your local forest database might become quite full of redundant data. The result databases... Look in "Project..."!