I have partioned my SQL Server 2008 database tables up using schemas to logically group tables together as [SchemaName].[TableName]

Also this gives me greater access control.

If one looks at the metadata the schema name is not that visible. One has to highlight a table to see what schema it belongs to.

I cloned an existing table present in schema into a table of the same name in a different schema.

When looking at the metadata, both tables are present but one has to highlight each table to see which schema it belongs to.

I can see this as a potential area for making mistakes.

It is possible to make the schema more visible with the current version?

Will this be addressed in the next version (2010)?

I don't think we will have a problem as we don't currently have table name collisions. The schemas are use mainly to group logically related tables.

However this might change.

EntitySpaces 2010 Better Handling of Schemas

We hope to announce a release date for EntitySpaces 2010 very soon.

We now handle schemas better and allow you to have the same table or view name in multiple schemas. You can see the Address table selected twice (in different schemas) in the Custom Template to the right. They will both create an Address.cs file so you would need to generate each schema into a different folder, but it’s great that this all works now.

What if the tables in different schemas are related?