# How can we track prepare statement leak on MySQL 5.5

**URL:** <https://forums.percona.com/t/how-can-we-track-prepare-statement-leak-on-mysql-5-5/4299>\
**Category:** Other MySQL® Questions\
**Created:** [July 13, 2015, 8:59am UTC](https://forums.percona.com/t/how-can-we-track-prepare-statement-leak-on-mysql-5-5/4299 "2015-07-13T08:59:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![raghupradeep](https://avatars.discourse-cdn.com/v4/letter/r/c5a1d2/32.png) [@raghupradeep](https://forums.percona.com/u/raghupradeep)\
**Post date:** [July 13, 2015, 8:59am UTC](https://forums.percona.com/t/how-can-we-track-prepare-statement-leak-on-mysql-5-5/4299/1 "2015-07-13T08:59:57Z")

</div>

On one of our production servers, we are suspecting prepare statement leak. This instance is used my more than 100 customers each having individual database. So, on MySQL 5.5 how can we trace who is causing the leak. I think on MySQL 5.6 we can use performance\_schema to do so. But other than using general queries is there a way to trace it in 5.5 ?

With Regards  
Raghupradeep