Fwd: application tuning

I've answered Fergal but I find the question and his own insights worth posting for all to take a stab at. Any comments. ---- Original Msg from: Fergal Flanagan <flanagaf@syntegra.bt.co.uk> At: 12/10 12:54 I was just thinking of other ways one can tune or make better an application in terms of say 4GL. Do you agree/disagree with below and is there any other/better ways of making an application work better and more effeciently providing the IDS is tuned. Avoid correlated subqueries Avoid 'not like' expressions Use unions to avoid seq access Do not index a table with <200 rows unless you need it to ensure data integrity Drop/Re-Create table that has changed by 25% Use set explain to optimise query Use update statistics with distribution to optimise query SELECT the tables with the fewest ROWS FIRST Use EXECUTE/PREPARE's IF the SQL statement is executed inside a loop Use Clustered Indexes if large table is sequentially processed in order of an index Borders should be kept to a MIN ( take longer to draw and appear on screen ) Use LET's instead of INITIALIZE AFTER CLOSE CURSOR / FREE unless using it again Use BUFFER INSERTS if inserting large amount of rows Avoid SQL mathematical operations like COUNT and complete calculations in the applic Avoid using program.* and use individual columns in update/selects instead Thanks for your kind help again,