Hungarian Notition is great for apps but not databases. You change one field and then you have to change 15 stored procedures, 13 views, 3 triggers, etc all because of a name change.

The only Hungarian Notation you shoud use if any is to stipulate between table and field and not any further than that (as in int or varchar) as this will not change. So if you had a table with customers in it call it tblCustomer and its fields could be fldCustomerId, fldFamilyName, fldGivenName, ... etc. You could change fldCustomerId from int to string and never have a major problem (I'm not saying you won't have a problem - but it won't be caused by a name change that for sure).

Besides a RDBMS isn't designed to communicate with .NET, VB, Java or whatever is being used. It's designed to store information and allow it to be retrieved in an effective way. So keep it effective. Don't allow the technology to dictate the design, good design should always shine through.