What I'm trying to do is improve the program's response time when it comes to executing command statements against the database.

Currently, each time a command is executed it goes through a process whereby the command is created, then configured with parameters, then the parameters are given their proper values and then the command is executed.

What I'm thinking of doing is trying to set up a system similar to the GC in the .NET framework. So, when the program executes a command object after the execution is complete it will get stored in a hash. After the command is stored there, the program can then just recall the command; provide new parameters; and then, execute the command again. My idea to keep the hash from growing out of control is to only allow commands to live there for a limited amount of time before they are discarded.

My question is whether or not this is a waste of time to even bother creating?

Laurence -