Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
buckeyeJane
Starting Member
11 Posts |
 Posted - 2015-04-27 : 11:08:22
|
| We have customer Types that have different business rules required based by class. CustomersBillingCustomer#OperationalCustomer#CustomerId#...Customer Class Type #1AcquisitionCodeDisposition**PayToCustomerId#Customer Class Type #2LatitudeLongitudeOperationType**PayToCustomerId#Customer Class Type #3Acquisition CodeDispositionNotification Method**SupplierCustomerID#In the example above, both the SupplierCustomerID# and the payToCustomerID numbers are referring back to the Customers Table. In order to get information about the Pay To Customer, a query to the Customer table is needed. What is the best practice for handling this type of database design? Thank you for your help regarding this database design question. |
|
|
gbritton
Master Smack Fu Yak Hacker
2780 Posts |
|
|
|
|
|
Database Design Best Plan