Anyway to just tell the webservers (I assume JNDI) to drop all prepared statements?
On Tue, Jul 21, 2009 at 4:09 PM, Glenn Barnard <barnardgl...@gmail.com>wrote: > restart your webservers! > > > On Tue, Jul 21, 2009 at 5:00 PM, Michael Schall <mike.sch...@gmail.com>wrote: > >> We run are running iBATIS within WebSphere 6.1 on Windows using JNDI >> against a DB2 database. During a performance tuning session we found a >> query using an index that did not have a vital column. We added the missing >> column to the end of the index on a test database and using a db2 query >> analyzer we saw a big performance gain. We moved the index to our >> production servers and see similar gains using db2 tools, however we do not >> see the benefit in the WebSphere application. How/Where are are prepared >> statements cached and how can I clear them to get a plan that takes >> advantage of the new index. >> Thanks >> >> Mike >> > >
