INFORMATION:

One aspect of good database design that often gets overlooked is naming conventions. It seems silly that something as easy as consistently using the same name for the same data object could make a different but it does, both on the database design side and the user side. For example, if half of your tables use the field Invoice_Date and the other half uses Invoice_Creation_Date for the same data, it would be very easy to assume those fields hold different information. Even small things like using Camel Case (InvoiceDate) versus underscoring (Invoice_Date) makes a big difference

Question:

How do you keep all of the fields, triggers and views straight on a large database that might contain tens of thousands of objects?

How do you know which naming convention to follow in the first place?

please answer in your own words and provide a website link so I can study this question in detail.