Difference between revisions of "Known Issues"

Revision as of 13:30, 16 October 2012

Updated 2012-09-13

Generating reports with large dataset and several columns can lead to "Time out expired" from the connected SQL Server.
- Try to set "Query Wait" in SQl Server Management Studio (for the database server) to a larger value (http://msdn.microsoft.com/en-us/library/ms189539(v=sql.105).aspx).
- A workaround is to export data from Optimization Results > Details, and use pivot tables in Excel. Also avoid selecting more than one simulation or plan at a time when creating reports.
- Another work-around is to use SQL Server Profiler (not available in Express version) to get the SQL Query and run the query in SQL Server Management Studio.

Add functionality to the Report Builder in PlanWise and RegWise to make class diagrams ("with group by-clause").
Wood property models (in progress).
More detailed results for extracted forest fuel (distribution over tree fractions).
Add columns for diameter distribution model parameters, so that users who have these data can enter them in the stand register spreadsheet.

@@ Line 3: / Line 3: @@
 ==Known problems==
 ====Common====
-*Generating reports with large dataset and several columns can lead to "Time out expired" from the connected SQL Server. A workaround  worth testing is set "Query Wait" in SQl Server Management Studio (for the database server) to a larger value (http://msdn.microsoft.com/en-us/library/ms189539(v=sql.105).aspx). Another work-around is to use SQL Server Profiler (not available in Express version) to get the SQL Query and run the query in SQL Server Management Studio. Another workaround is to export data from Optimization Results > Details, and use pivot tables in Excel. Also avoid selecting more than one simulation or plan at a time when creating reports.
+*Generating reports with large dataset and several columns can lead to "Time out expired" from the connected SQL Server.
+**Try to set "Query Wait" in SQl Server Management Studio (for the database server) to a larger value (http://msdn.microsoft.com/en-us/library/ms189539(v=sql.105).aspx).
+**A workaround is to export data from Optimization Results > Details, and use pivot tables in Excel. Also avoid selecting more than one simulation or plan at a time when creating reports.
+**Another work-around is to use SQL Server Profiler (not available in Express version) to get the SQL Query and run the query in SQL Server Management Studio.
 ====RegWise====