• ZZartin - Monday, December 11, 2017 12:11 PM

    Eric M Russell - Monday, December 11, 2017 11:57 AM

    When I'm wearing the DBA hat, I really don't comment much at all regarding the application developer's choice of naming convention, because ultimately they are the one's who have to code against it. I'd rather focus on normalization and optimization.

    I would tend to agree with this, as long as the table name gives a general idea of what's in it i don't really care if it's called say SALES_ORDER or SALES_ORDERS.

    And when I was a DBA, we did the naming of all tables and columns as a part of the database design, and provided them to the developers.  We, as DBAs, also wrote most of the stored procedure code, and had final review of all procedures before they were implemented.

    Rick
    Disaster Recovery = Backup ( Backup ( Your Backup ) )