The answer, is quite simply "No."

Someone shot a post from Google Groups through my inbox this morning where some people were having problems with session timeouts (they were seeing rsExecutionNotFound exceptions). Their "solution" was to edit the stored procedures that manage user session in our catalog database in attempt to prevent them from encountering this issue.

This is wrong for a couple of reasons:

  1. If you think you are encountering a bug, please let us know about it.  You are probably not the only person hitting it.  We would like to fix the issue or provide a workaround to make all of our customers happy.
  2. You don't know what you are doing.  Unless you have access to the source code for the entire product you are not going to be able to infer all of the semantics associated with the stored procedure.  Altering it will put your system in a completely untested state, making it very difficult for us to provide support for you.