David Ziffer (10/13/2010)
With regards to the "xxx": this is no different that putting things into .NET name spaces. Once again, the relational database does not give us any tools for compartmentalizing our tables, so we must unfortunately do it ourselves.
Ever heard of schemas?
MSDN: http://msdn.microsoft.com/en-us/library/ms365789.aspx
A schema is a container that holds tables, views, procedures, and so on. … Every securable in a specific schema must have a unique name. The fully-specified name of a securable contained by a schema includes the name of the schema that contains it. Thus, a schema is also a namespace.
David Ziffer (10/13/2010)
At some point we are potentially going to want to name one thing "table X" and another thing "view X", and the only difference in the names will be whatever we choose to designate something as being a "view" vs. "table".
If that's the case then your database design sucks. If there's a table called "Customers", why would there ever be a view called "Customers" in the same schema? It's pointless and confusing.