Stand-alone tables for populating dropdown lists only RRS feed

  • Question

  • Hello All,

    I have researched for best practices regarding the use of database tables which are only used for populating dropdown lists, with no relationship to other database tables, but have been unable to find information relative to this design. I wish to follow best practices of industry standards, so I am posing my question here.

    My application is an Auto Maintenance application to track vehicle maintenance. My database design consists of tables which participate in the ERD, however, I want to add several other 'stand-alone' tables which do not interact with other tables. Is this a valid database design? For example, as part of my ASP.Net/C# app, I want the user to be able to select a vehicle, and during page_load(), I will invoke database access to read from several tables to fill several textboxes on the form. These tables include, Vehicle Manufactured Year, Make, Model, VIN. These tables have no relationship to the other tables in my database.

    Thank You, and any help is appreciated.

    Saturday, January 19, 2019 3:31 PM


All replies