April 17, 2012 at 9:04 am
Hi, I've created a custom database role for developers in my company, this role has enough permissions for everyday tasks such as creates, alters, inserts, deletes, updates, view definitions and some other permissions that let them create and modify any database object.
We want to implement this role with a set of selected permissions in order to have a better administration. Right now they are in the role of db_Owner
I've made some tests on my desktop before implementing this role in a production server. I've created a SQL user to do some tests and also I've added this user to my custom role in a test database, but everytime I want to create a new table from the GUI in SSMS, it displays a warning message saying that "You are not logged on as the database owner or system administrator. You might not be able to save changes to tables that you do not own.", despite of this, I'm able to create a new table, when a I save it, another warning message appears saying "You are not the table owner", after clicking OK, the table is created correctly, the same happens when I do right click on a table and select "Design", then I add a new column and save the changes and one more time the warning message is displayed.
But when I Create or Alter a table via Transact-sql, it doesn't display any warning message. This warning message will be kind of annoying for developers who are used to the GUI.
I've made some research about this message and it seems to happen with the db_ddladmin role, but nobody has come to a solution yet.
Here's what Microsoft people says http://connect.microsoft.com/SQLServer/feedback/details/467582/db-ddladmin-role-doesnt-allow-use-of-design-functions-in-ssms
I hope you can help me out, thanks 🙂
April 17, 2012 at 9:56 am
Which version of SQL Server are you using? The last message from Microsoft in June 2011 says "This will reflect in an upcoming release of SQL Server." and the item is "Closed as Fixed". The fact that it's closed as fixed means little, as that is often done when there really was no resolution, but in this case it may be true. The "upcoming release" in June 2011 would have been SQL 2012, have you checked there? The SSMS GUI was completely re-worked onto the Visual Studio 2010 Shell so a fix there may not easily backport to SSMS 2008, therefore you may not see a fix there.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
April 17, 2012 at 9:58 am
hiram.osiris (4/17/2012)
This warning message will be kind of annoying for developers who are used to the GUI.
I have no sympathy for those folks 🙂 I would tap my opportunistic side and guide those GUI-developers towards writing more T-SQL 😉
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
April 17, 2012 at 10:43 am
Hello opc.three, I'm using SQL Server 2008R2, I've also made the same test on SQL Server 2012RC0 and the same warning message appears. I understand that this message is just "warning me" that I'm not the database owner, but I've the appropiate permissions to do any operations with db objects. It would be good to force developers to use T-SQL hehehe but according to them, they use GUI in order to save time.
I'll try to workaround to disable this warning message, I can't rely on Microsoft people, if I found a solution I'll share it here, also comments and suggestions are welcome 🙂
June 4, 2014 at 8:45 am
Hello There
I am having the same issues, any ideas on how you solve them please? Thank you
March 31, 2015 at 1:21 pm
Ive run into the same issue lately, seems as though the developers dont like seeing it every time ?! Any help would be appreciated.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply