Re: default schema (SQL Server 2005)

And I did try changing the dbo user's default schema to something else, but
SQL Server will prevent that with:
Msg 15150, Level 16, State 1, Line 1

Cannot alter the user 'dbo'.


(And, if it did work, it would be a bad idea.)

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: Create Procedure Permission ONLY
    ... Schema dbo owns all objects. ... Developer's should not create or alter tables. ... CREATE LOGIN testdev WITH PASSWORD = 'sldkjlkjlkj 987kj//' ...
    (comp.databases.ms-sqlserver)
  • Re: Create Procedure Permission ONLY
    ... Schema dbo owns all objects. ... Developer's should not create or alter tables. ... CREATE LOGIN testdev WITH PASSWORD = 'sldkjlkjlkj 987kj//' ...
    (comp.databases.ms-sqlserver)
  • RE: Please help with deleting a user.
    ... MCITP: Database Administrator ... it says that it can not alter "dbo" schema. ... I am new to SQL Server. ...
    (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)
  • DDL Permissions - CREATE PROCEDURE, but no CREATE TABLE
    ... I want to allow devlopers to create and alter sprocs in the dbo ... schema, but not create or alter tables. ...
    (microsoft.public.sqlserver.security)