Home Forums Database Design Design Ideas and Questions List of Database Naming Convention Decision Points RE: List of Database Naming Convention Decision Points

  • December 5, 2012 at 10:16 am

    #1565847

    we use this one at our shop:

    primary key and foreign key column name must contain name of the table...ie tbCity has tbCityID as it's PK, and all foreign key columns are name tbCityID

    in the cases where multiple FK's need to exist, the FK must still START WITH the same name, so tbCityID_Business and tbCityID_Personal would be used , for example.

    our "lookup" tables all start with tb or lu, more for sorting purposes than anything else. tables related to specific purposes/modules for an application are "tibbled", but with an eye towards organizing the tables by application or purpose. cmsEntities for contact managment, acctHeader/acctDetail for accounting tables, stuff like that.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!