Database... Give it a name that's meaningful

Tables... Pluralized version of what they store, so for customer data use Customers

Columns... Just use what they are. If it's first name, just use FirstName. Do not do CustomerFirstName. It's not needed, does not add meaning, and requires lots more typing.

Casing... CamelCasing

I NEVER use underscore if I can help it. I've found it doesn't increase readability over camel casing and needlessly increases typing by two keystrokes every time it's used.

If you use stored procs, don't begin them with sp_. Think of that as "system procedure"

Why do you have five tables with Address1? Create an Address table and then link to it with a foreign key.

>Hi
>About to start a new app.
>Plan to use Entity Framework, and will be using Winforms initially and some Web Forms (Or MVC ) down the line
>Will be using MS Sql Server for the Database
>
>Wondering whats best approach with Naming Conventions
>
>e,g,
>For DataBase (Use MyGreatDataabse MYDATABASE My_Databas etc
>for Table Names (Use CustTable Customers, Customer , Customer_Table CUSTTAB etc
>for Field Names (Use Ad1 or CustAd1 or CustomerDeliveryAddress1 or CUST_ADDRESS1 etc)
>If using for instance Address1, there will probaly be 5 different tables with an Address1
>
>Any particular casing recommended
>
>Tia
>Gerard