|Date: ||Thu, 20 Jun 1996 14:10:28 -0400|
|Reply-To: ||Roger Deangelis <deangel@HORIZSYS.COM>|
|Sender: ||"SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>|
|From: ||Roger Deangelis <deangel@HORIZSYS.COM>|
|Subject: ||Keyed Lookups set x/key=y;|
There are several facts I learned about
keyed lookups (The hard way).
When you are creating an index that should
be unique, always create the index with
the unique option.
If possible do not include columns in a
key that you know will always be null
Use different names for the keys in the
master and transaction tables ( especially
if you expect to do many keyed lookups
or sql processing ).
Pehaps the keys should have different
names on all tables???
Obviously you pay a penalty when
using merge, modify and update.
You may need to rename columns.