According to my understanding, a default schema should apply when issuing SQL statements on tables using unqualified table names.
My problem is that the following statement fails, because the table name cannot be resolved.
-- Table name : [mydb].[myschema].[mytable] USE mydb SELECT * FROM mytable Msg 208, Level 16, State 1, Line 2 Invalid object name 'mytable'.
I have a database user defined based on a Windows login user
mydomain\myuser with the following properties:
- The login user is not a member of the
sysadmingroup, but only of
public. According to the documentation, these memberships should not be a problem.
- The mapped database user (also called
mydomain\myuser) has the default schema
- The database user is member of
When connecting with MS SQL Management Studio as
dbo. This indicates that for some reason, the default schema
myschema is ignored. This is consistent with the failed SELECT statement.
But why is the default schema ignored?