Subject | FK and OAT |
---|---|
Author | Duleep |
Post date | 2007-06-04T11:27:37Z |
Hello there
I run a large database application with over 300 tables. The client
complains about frequent client freeze in high volume billing areas.
This problem disapprears when I do a gbak and restore.
After analysing with some tools, I found out that the OAT was in the
range of 500K. I read somewhere that duplicate indices could be the
problem, hence I deleted some of the FK contraints in master detail
relationship
(productmaster->billitemdetails,Categorymaster->productmaster etc).
The result has been a drastic reduction in OAT count.
Am I heading the right way ? My application handles transactions
pretty well (At least it seems to)
Please suggest
Thanks
Duleep
I run a large database application with over 300 tables. The client
complains about frequent client freeze in high volume billing areas.
This problem disapprears when I do a gbak and restore.
After analysing with some tools, I found out that the OAT was in the
range of 500K. I read somewhere that duplicate indices could be the
problem, hence I deleted some of the FK contraints in master detail
relationship
(productmaster->billitemdetails,Categorymaster->productmaster etc).
The result has been a drastic reduction in OAT count.
Am I heading the right way ? My application handles transactions
pretty well (At least it seems to)
Please suggest
Thanks
Duleep