Online Engine vs Standard

> > Hi! > > -> ONLINE IS A COMPLETELY DIFFERENT ANIMAL FROM SE. It requires much > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > This is not an idle statement. One of the most common problems I've > experienced is that transaction logging becomes a major issue. If you > *do* have use logging, HEED THESE WORDS: > > 1. Make your logs big. Very big. Huge. > > 2. Make lots of logs. Plenty. > > 3. Run continuous backups. Continuously. > Addendum (should this go an our non-existant FAQ?): 4. Lower the default Transaction high water marks from: LTXHWM 80 # Long TX high-water mark (percent) LTXEHWM 90 # Long TX exclusive high-water mark (percent) to: LTXHWM 70 # Long TX high-water mark (percent) LTXEHWM 80 # Long TX exclusive high-water mark (percent) 5. Monitor the running of the continuous backups so that when it asks for a new tape you can mount one. (Alternatively use a diskfile instead of a tape, make it big enough to handle a weeks worth of logs, archive daily and clear it). 6. Never, ever, ever kill an sqlturbo. tbmode -z it. 7. Teach users not to do things likely to cause a long transaction error: e.g. "LOAD FROM .... INSERT INTO ...." 8. When doing DELETEs, lock the table exclusively (otherwise may cause lock overflow). Others? cheers j. _____________________________________________________________________________ Jack Parker | Hewlett Packard, BSMC Boise, Idaho, USA| jparker@hpbs3645.boi.hp.com | "A mind is a terrible thing." (208) 396-5388 (W) (208) 384-1623 (H) | _____________________________________________________________________________ Any opinions expressed herein are my own and not those of my employers. _____________________________________________________________________________