D
Dmitri Levin
Guest
Thank you Rob. I removed version 8 calculations from my page. I guess there are no version 8 users and if there are ... too bad. proora.com/.../dbuse.html Aggressively eliminating long-running transactions -- is a must, especially in case of crappy code. I have 30 minutes rule. YMMV. As to -bithold setting it depends. And there is no one rule that works for everyone. Mine -bithold value is more then anything mentioned in this or other threads. Since it s a fact that we established there is "crappy code out there" and nobody is going to rewrite Progress application here written in 1980es, then the size of -bithold is a matter of volume of business rather than best practice. For some folks 500MB is enough, for some 19GB is not enough. I -bigrow after each bi truncate to 2 GB just to start with. And on average day that is enough. When bi reaches 5 GB I receive a text on my phone using the code mentioned above and handle that case by case. If bi reaches -bithold I will probably be out of work, because business loss of 10 minutes of downtime exceeds average yearly salary of DBA by the factor of 3 to 5. Same is true about Lock Table overflow (-L). For some 50,000 is too much, for us anything less than 1/2 million means we need to close our business.
Continue reading...
Continue reading...