It does, but the moment you introduce changes to the program like my OrderPayments example you ultimately reduce the number of columns in the long run.
Software changes frequently in most places, because business rules change and because feature requests come in.
Designing your database this way, makes you more agile / quick to respond to those changes.
-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Monday, August 28, 2017 1:25 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Database design question
As far as the space considerations adding a surrogate key, in addition to order number and line number, takes space also.
Rob Berendt
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
