Hi Alex, You can run the DBCC FREEPROCCACHE against the Published database. In my case above, the problem was obviously connected to the published DB as shown by the sp_who2 results. You may consider running it against the Draft DB, as well. Brian Smith's blog also notes that if you don't want to run the sledgehammer of the FREEPROCCACHE command, you can do the following: 4. If other applications are running you probably don’t want to run that DBCC command – so instead you could just recompile a couple of the likely stored procedures: Draft DB EXEC Sp_recompile MSP_ProjQ_Lock_Next_Available_Group EXEC Sp_recompile MSP_ProjQ_Get_Status_Of_Jobs_List Published DB EXEC Sp_recompile MSP_TimesheetQ_Get_Status_Of_Jobs_List EXEC Sp_recompile MSP_TimesheetQ_Lock_Next_Available_Group