Hi EM,

One of the issues noted with prefixes is that the type of object can actually be changed.  For instance, you might have a table named "tSales" or even "t_Sales" to use your recommendation.  What happens when you change "t_Sales" to a View?  You now have to change the name to "vw_Sales" on the server, and you have to change all client code that used to query the "t_Sales" table.

If the justification for using prefixes like "t_" and "vw_", etc., is to make it easier on the eyes in Enterprise Manager, this should not be a problem in SQL 2005.  You can prefix all your objects with a schema (other than "dbo.") in SQL 2005, so all your "Sales"-related tables (for instance) will group together nicely (and separately from "dbo.") in SSMS without the need for redundant prefixes in your naming convention.

To use your example, you could group all the Sales-related tables into a "Sales" schema on SQL 2005:

Sales.Sales

Sales.History

Sales.Categories

Sales.Reps

Sales.Contacts

Same goes for SP's and UDF's.  You can use the simple "ObjectAction" naming convention and assign them to the proper respective schemas.