This article is a good start.
There are even better reasons not to use Hungarian Notation. I don't care about the data type of a column often enough. I create a table once, then I care about the type. When selecting from a table into another, if you are going into differently named columns, the data type is not an issue, its getting columns into the correct destination. If you are creating a table with select, you don't care about the datatype.
When writing t-sql, I might care about data type when declaring a temporary variable. But I do not need a crutch telling me the data type, any good development environment will give it to you. I write procs using Query Analyzer and I'm browsing the object browser to get columns names, so data type is at hand.
The cost of wordiness exceeds the usefulness of the information.
Now would you write about prefixing column names with an abbreviation for the table, or prefixing object names with the object type? I am against both of these practice for the same reason I dislike Hungarian Notation.
Here is a practical reason for not prefixing columns with table names. Table aliases already give you a prefix. In complicated queries, you will use table aliases. In simple queries, you don't need the table prefixed to the column name. When I developed a complicated series of queries for a report, many tables were involved and intermediate tables were used in multiple steps. All tables involved had an alias. There is no benefit, and there is a cost to writing code like
Select * from tblEmployees emp join tblSupervisors sup
ON emp.Emp_EmpID = sup.Sup_EmpID
Ugly code. No beneficial information. The same fields existed in multiple tables and I sometimes had to change the join. Using prefixes, I'd have to change the table alias, then the table prefix. A poster mentioned don't prefix for FKs. Before you ask, in the real case, there were no FKs involved. But more importantly, rules with exceptions are a lousy idea.
Don't repeat information. Don't make code verbose.
Don't prefix objects with the type. I don't care if I'm joining a table to a view. Prefixes just make the code verbose. The cost of wordiness exceeds the usefulness of the information. Crutches are no substitute for knowing your database.