Good software is useless if your infrastructure is not performing well. While working with our clients, we see that some face issues related to QAD Infrastructure itself: QAD database, server issues, etc. Nectar Daloglou of OmegaServe provides excellent service to some of our customers and joins us for this webinar. Nectar knows that the best way to avoid disasters is to learn from mistakes — preferably someone else’s. Join us for an entertaining and informative session as Nectar tells horror stories of some of the most dangerous, and destructive things that he and other senior DBAs have encountered in the OpenEdge/QAD world. He’ll talk about …

• Human error
• User process kill
• Excessive BI growth
• Lock table overflow
• Host name change

• Additional Webinars

Questions from the webinar

	Where can I download a free trial of ProTop?
1) Download ProTop here. 2) Contact nd@omegaserve.com to activate your trial
	You mentioned that -L overflow can use memory from -Mxs. Where can I find what my excess shared memory (-Mxs) parameter is set to?
Ideally, you want to monitor your Lock Table highwater mark and never get to the point where you run out of Mxs. ProTop is a great tool for that 😀. To see what your Mxs has been set to, there are two ways: 1) In the database log file, grep or do a find for “Mxs” 2) From Promon: R&D>1>12 Startup Parameters. Look for “Excess shared memory”
	Can you give some example blogs that help with best practices?
OmegaServe blog 32 Soft blog WSS blog Facebook: OpenEdge Zone And many others on Facebook and LinkedIn