Property DefaultSchema is not available for Database [DatabaseName]

   I found the root cause of the problem you described and it seems to be a bug in SQL Server Management Studio when trying to create a schema-bound object on SQL Server 2005. The tool is internally trying to find (without success) the default schema for the user and failing.

< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /> 

   What should happen (to have the same behavior found in SQL Server 2000) is that it should create an implicit user and schema for the caller (let¡¯s call it user1 for simplicity) and the table in the specified schema (notice that the default schema name is the same as user name). It is important to observe that at the end you end up creating an implicit user and a schema for every member of the group that creates an object in the database.

   In order to get the same results right now, you have two possible options:

1)      Create the first object using  TSQL directly:

a.       Click on ¡°New Query¡± and connect to the right server

b.      Write the script to create the table and click on ¡°Execute¡±, for example:

use [db_Test]

go

CREATE TABLE [MyTable]( data varchar(10) )

go

c.       If you refresh the view in Object explorer you will notice the following changes:

                                                              i.      Table created = [user1].[MyTable]

                                                            ii.      New user = [Domain\user1]

                                                          iii.      New schema = [Domain\user1]

 NOTE:  At this point you can drop this ¡°dummy¡± table and everything should work fine from now on for this particular user.

2)      Explicitly create a user for [Domain\user1], Schema [Domain\user1] is completely optional

IMPORTANT NOTE: To have an equivalent behavior, you will need to revoke the CONNECT permission on the database to [Domain\user1] (REVOKE CONNECT TO [Domain\user1]), this way the only access to the database would be via the Windows group membership and not by an explicit permission.

  I hope we were able to help you, let us know if you have further questions. We really appreciate your feedback.

  Thanks a lot,

-Raul Garcia

 SDE/T

 SQL Server Engine