In OnTime 2007 we moved the filtering of items to the SQL Server so we can do paging on the SQL Server as well.  Doing this means we have to pass all the filtering criteria to the stored procedures, and because we want to support SQL 2000 it means we are restricted to 4000 character length parameter (nvarchar(4000)).  The problem happens when you have a large number of projects or a large number of custom fields, which causes the filters being passed into the stored procedures to be larger than 4000 characters.

There is a workaround for this if you are using SQL 2005.  SQL 2005 introduces the concept of nvarchar(max), which basically removes the 4000 character limit on the nvarchar data type.  There are 9 stored procedures which need to have all instances of nvarchar(4000) changed to nvarchar(max):
spS_Defects_WithNames
spS_Defects_WithNames_Count
spS_Features_WithNames
spS_Features_WithNames_Count
spS_Incidents_WithNames
spS_Incidents_WithNames_Count
spS_Tasks_WithNames
spS_Tasks_WithNames_Count
spS_Dashboard_MiniDashboard
Each stored procedure has 2-3 parameters of that type as well as a couple of variables. Make sure to back up your database before modifying anything.

If you are using SQL 2000, unfortunately there is no easy fix for this.  You may want to consider upgrading to SQL 2005, or using the free SQL 2005 Express edition.

We plan on addressing this issue, but because it involves multiple stored procedures it will most likely not be in the 7.0.2 release, which is already in testing.  I apologize for the inconvenience, but we are trying to make sure the fix will not cause any further problems.