Re: default schema (SQL Server 2005)

A sysadmin works within databases in the dbo context, so it will use the dbo
schema (which has always been the default schema for sysadmins, except that
is was called 'owner' in SQL ).

So, I don't think you have an option on this.

RLF
<dnlgauthier@xxxxxxxxxxx> wrote in message
news:1187272016.929096.136070@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Is there anyway to change the default schema for a user who is a
member of "sysadmin". It appears that Microsoft has made the default
schema for this role "dbo" and our application has been writtem not to
include owner/schema name.



.

Relevant Pages

  • Re: Alter User for domain user
    ... Any member of sysadmin will always be the dbo inside a DB. ... connect to the server with Windows Authentication, the default schema ...
    (microsoft.public.sqlserver.security)
  • Re: default schema (SQL Server 2005)
    ... schema (which has always been the default schema for sysadmins, ... schema for this role "dbo" and our application has been writtem not to ... I agree with the statement that a sysadmin works with in teh database ... so how can I provide user access via an application ...
    (microsoft.public.sqlserver.security)
  • Re: Alter User for domain user
    ... while still having a default non-dbo schema. ... If you are sysadmin, you are ... dbo in the database, and your default schema is dbo. ... Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx ...
    (microsoft.public.sqlserver.security)
  • Re: Access 2007, SQL 2000
    ... Since users are not dbo, and SQL 2000 used the user name as the schema identifier, you have to make sure that every reference to a SQL Server object is fully qualified with the dbo. ... Normally a user should not be able to create any new objects in the db, but if they do, those new objects will be in the userName schema, not the dbo schema, assuming the user is not a db owner. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: exporting into a SQL Server schema
    ... inside of the schema. ... The thing that's most confusing is that the dbo schema isn't ... take a look at the way the objects in the AdventureWorks database are ... It turns out that I'm moving some tables to a web hosted solution with sql ...
    (microsoft.public.access.externaldata)