Heenan, Lambert
Lambert.Heenan at AIG.com
Fri Jul 20 14:54:35 CDT 2007
If it was performance above all we'd all be working with non-normalized flat databases. Joins cost time = reduce performance. But as we all know normalization is about having good data, not about getting at it as fast as possible. Just like Susan said. Lambert -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Friday, July 20, 2007 3:40 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] One-to-One relationships LOL, and I somewhat disagree. The first rule is to be useful and usable. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins Sent: Friday, July 20, 2007 3:06 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] One-to-One relationships The first rule of database development is performance, above all other considerations. ======I strongly disagree -- the first rule is to ensure data integrity. Susan H. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com