SQL Server 2000 / ADO.NET / VB.NET
undemanding environment / 20 occasional users / 5 constant users
The major table of the application (customer table) has 12 references
to other tables. I don't expect it to grow beyond this. All these
relationships come into play during customer creation and most during
statistical reporting, but only a few come into play during daily use.
• Seven of the retionship talbles are only lookup tables that put
integers into the fileds of the customer table.
• Five of the seven lookup tables serve the purpose of classifing
customers for reporting statistics or other business rules.
• Two of the seven lookup tables track status. (Customer status,
project manager status)
• The other four relationships are of a more vital business nature.
I heard something of a 14 or 16 referenced tables limitation relating
to performance.
Are there any design suggestions to insure good performance for this
scenario?