> We are running SQL Server 2005 enterprise with SP2. Recently, after
> assigning db_ddladmin permissions to someone, I ran across something
[quoted text clipped - 11 lines]
> behavior appears inconsistent between the GUi and TSQL. Is the behavior
> different or am I missing something?
I ran Profiler to see what queries Mgmt Studio runs, and I found that it
runs:
select Has_Perms_By_Name(N'dbo.binary', 'Object', 'ALTER') as ALT_Per,
Has_Perms_By_Name(N'dbo.binary', 'Object', 'VIEW DEFINITION') as
View_def_Per,
Has_Perms_By_Name(N'dbo.binary', 'Object', 'CONTROL') as Contr_Per
This query returns 1, 0, 0 for a user with db_ddladmin, why Mgmt Studio
thinks that this guy is not good enough. It appears that Mgmt Studio
has overlooked db_ddladmin.
This could be construed as a good thing, at least when it comes to
the Table Designer and the diagrams, as these tools are seroiusly
buggy and are dangerous to use for table modifications, unless you
understand what they do, including what they shouldn't do.

Signature
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx