A customer recently called after an ASE 12.5 to ASE 15 upgrade, complaining of performance issues of certain, (previously) quick queries. I didn't have this one in my back pocket then, and should have:
We increased statement cache, and enabled literal autoparameterization, the problem dissolved.
Apparently, the optimizer is a lot smarter with 15, but also works much harder. Caching sql statements made a huge difference.
Monday, February 2, 2009
ASE 15, the optimizer, and a quick config tip
Labels:
ASE 12.5,
ASE 15,
ASE upgrade,
sql statement performance,
upgrade
Subscribe to:
Post Comments (Atom)
Hi Jeff, We have ASE 15.0.3 and are using the statement cache, the queries are large average plan size is about 35KB. We are anticipating a very large statement cache on account of large number of queries in the application about 200K. What is the maximum feasible statement cache size as per your experience. Thanks in advance.
ReplyDelete