Hi, We have just upgraded to 3.2 (SpiraTeam) and have noticed significant performance hit. We also upgraded the host, XP -> Server 2008 R2, SQLExpress -> SQL Server 2008 Full, 4GB -> 8GB. Our live system went from 2.3.1 -> 3.2 in a single sweep, but we had also assessed 2.3.1 -> 3.1 in a test env, where the migration was error prone, and led to support tickets, but the performance was not as bad as 3.2 appears to be. The 3.2 upgrade ran smoother and gave us much more confidence, especially as the 3.1 -> 3.2 could not be achieved in house, after our database became corrupted during migration. Do you have any benchmark data for different versions or configurations? Are there any known tweaks that might give us better performance? Significant delays are now seen whenever large sets of data are manipulated (Show All Levels -> Show Level 1). It might be worth pointing out that our SpiraTeam DB is approaching 4GB, which was the main reason for SQL upgrade. Are there any known issues with this? Thanks, Charlie en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/issues-questions/238.aspxthreadId=238Charlie Stott (cstott@tnsi.com)Hi, We have just upgraded to 3.2 (SpiraTeam) and have noticed significant performance hit. We also upgraded the host, XP -> Server 2008 R2, SQLExpress -> SQL Server 2008 Full, 4GB -> 8GB. Our live system went from 2.3.1 -> 3.2 in a single sweep, but we had also assessed 2.3.1 -> 3.1 in a test env, where the migration was error prone, and led to support tickets, but the performance was not as bad as 3.2 appears to be. The 3.2 upgrade ran smoother and gave us much more confidence, especially as the 3.1 -> 3.2 could not be achieved in house, after our database became corrupted during migration. Do you have any benchmark data for different versions or configurations? Are there any known tweaks that might give us better performance? Significant delays are now seen whenever large sets of data are manipulated (Show All Levels -> Show Level 1). It might be worth pointing out that our SpiraTeam DB is approaching 4GB, which was the main reason for SQL upgrade. Are there any known issues with this? Thanks, Charlie Thu, 09 Feb 2012 04:35:41 -05002013-03-04T13:32:54-05:00/Support/Forum/spirateam/issues-questions/238.aspxmessageId=470David J (adam.sandman+support@inflectra.com) Can you check that the database transaction logs are not getting large (you may need to do a backup / truncate of the logs) and that the database indexes are current. The process of migration can cause the logs to get full and the indexes to get out of date (since it's doing a bunch of INSERTs to repopulate the database). This usually explains any post-upgrade performance issues. See https://www.inflectra.com/Support/FAQs.aspx#technical07 for how to refresh the indexes. Fri, 10 Feb 2012 15:58:24 -05002012-02-10T15:58:24-05:00/Support/Forum/spirateam/issues-questions/238.aspx#reply470messageId=966Andy Smith (andy.smith@infoterra-global.com) Hello Adam, we have a performance issue that appears not to be related to an upgrade - although we have recently upgraded to version 4.0 we had problems reported prior to this. The logs look OK and our database is only about 360 MB anyway. Our system administrator was going to re-build the indexes but the link on the previous post gives an error. Can you either fix the link or post the original content on this thread please. Thanks and regards. Mon, 04 Mar 2013 13:32:54 -05002013-03-04T13:32:54-05:00/Support/Forum/spirateam/issues-questions/238.aspx#reply966