There's also the cognitive overload of reading long identifiers, multiplied by the naming conventions of some large corporate databases. I'd rather see: E

There's also the cognitive overload of reading long identifiers, multiplied by the naming conventions of some large corporate databases. I'd rather see: EmployeeReferences eFrom JOIN EmployeeReferrals eTo ...and then see ON eFrom.ID = eTo.ID ... JOIN xyz ON eFrom.Source = ... rather than have to read acres of EmployeeRe-something 4 or 5 times through an 8-table BI join. Similarly, I've had to deal with (admittedly legacy) tablenames like A12R18SALE and A12B14PROD. Aliases come in really handy there.