Hello,

     I am new to the SQL Azure. When I tried to create table on master DB, i get following error.

Msg 262, Level 14, State 1, Line 1CREATE TABLE permission denied in database 'master'.

I tried to change role to 'db_owner' but have received following error.

Msg 15151, Level 16, State 1, Line 1Cannot alter the role 'db_owner', because it does not exist or you do not have permission.

I logged into master DB using the credentials I created while creating DB on the Azure. This is supposed to be 'sa'.

My question is, does SQL Azure allow to create objects (tables, stores procedures, triggers) on master DB. If yes, what am I doing wrong? If no, why?

My guess is that SQL Azure is not less than the On premises DB. It must be allowing objects creation on master DB.

I have found a similar question on forum but I did not get the answer. Here is the link --> https://social.msdn.microsoft.com/Forums/azure/en-US/cbff1bd2-358f-4106-b238-ec369941099d/master-database-cannot-alter-the-role-dbowner.

FYI, I have gone through following resources but haven't got solution for my problem.

1) https://iainhunter.wordpress.com/2011/06/20/copying-databases-and-creating-users-and-logins-for-sql-azure/

2) http://www.c-sharpcorner.com/forums/thread/126589/create-database-permission-denied-in-database-master.aspx

3) http://stackoverflow.com/questions/20656943/how-do-you-change-the-owner-of-an-azure-database

4) https://msdn.microsoft.com/en-us/library/azure/ee336235.aspx

Thanks in advance.

Hi amtindia,

For all intents and purposes, master is a read-only DB.  Master is a system database that is created per logical server in Azure SQL Database.  The two main purposes of master are 1) managing logins for your server's databases allowing you to create, alter, and drop logins and 2) providing read-only views of DMVs/metrics/metadata.  You are not charged for master and thus the restriction on creating tables/stored procs/triggers.

• Edited by Joseph IdziorekMicrosoft employee 20 hours 1 minutes ago
• Proposed as answer by Joseph IdziorekMicrosoft employee 13 hours 44 minutes ago
• Marked as answer by amtindia 5 hours 16 minutes ago

Hi amtindia,

For all intents and purposes, master is a read-only DB.  Master is a system database that is created per logical server in Azure SQL Database.  The two main purposes of master are 1) managing logins for your server's databases allowing you to create, alter, and drop logins and 2) providing read-only views of DMVs/metrics/metadata.  You are not charged for master and thus the restriction on creating tables/stored procs/triggers.

• Edited by Joseph IdziorekMicrosoft employee 19 hours 49 minutes ago
• Proposed as answer by Joseph IdziorekMicrosoft employee 13 hours 32 minutes ago
• Marked as answer by amtindia 5 hours 5 minutes ago

Hi amtindia,

For all intents and purposes, master is a read-only DB.  Master is a system database that is created per logical server in Azure SQL Database.  The two main purposes of master are 1) managing logins for your server's databases allowing you to create, alter, and drop logins and 2) providing read-only views of DMVs/metrics/metadata.  You are not charged for master and thus the restriction on creating tables/stored procs/triggers.

• Edited by Joseph IdziorekMicrosoft employee Wednesday, February 04, 2015 3:39 PM
• Proposed as answer by Joseph IdziorekMicrosoft employee Wednesday, February 04, 2015 9:56 PM
• Marked as answer by amtindia Thursday, February 05, 2015 6:24 AM

Hi amtindia,

For all intents and purposes, master is a read-only DB.  Master is a system database that is created per logical server in Azure SQL Database.  The two main purposes of master are 1) managing logins for your server's databases allowing you to create, alter, and drop logins and 2) providing read-only views of DMVs/metrics/metadata.  You are not charged for master and thus the restriction on creating tables/stored procs/triggers.

• Edited by Joseph IdziorekMicrosoft employee Wednesday, February 04, 2015 3:39 PM
• Proposed as answer by Joseph IdziorekMicrosoft employee Wednesday, February 04, 2015 9:56 PM
• Marked as answer by amtindia Thursday, February 05, 2015 6:24 AM

Hi amtindia,

For all intents and purposes, master is a read-only DB.  Master is a system database that is created per logical server in Azure SQL Database.  The two main purposes of master are 1) managing logins for your server's databases allowing you to create, alter, and drop logins and 2) providing read-only views of DMVs/metrics/metadata.  You are not charged for master and thus the restriction on creating tables/stored procs/triggers.

• Edited by Joseph IdziorekMicrosoft employee Wednesday, February 04, 2015 3:39 PM
• Proposed as answer by Joseph IdziorekMicrosoft employee Wednesday, February 04, 2015 9:56 PM
• Marked as answer by amtindia Thursday, February 05, 2015 6:24 AM

Hi amtindia,

For all intents and purposes, master is a read-only DB.  Master is a system database that is created per logical server in Azure SQL Database.  The two main purposes of master are 1) managing logins for your server's databases allowing you to create, alter, and drop logins and 2) providing read-only views of DMVs/metrics/metadata.  You are not charged for master and thus the restriction on creating tables/stored procs/triggers.

• Edited by Joseph IdziorekMicrosoft employee Wednesday, February 04, 2015 3:39 PM
• Proposed as answer by Joseph IdziorekMicrosoft employee Wednesday, February 04, 2015 9:56 PM
• Marked as answer by amtindia Thursday, February 05, 2015 6:24 AM

My question is, does SQL Azure allow to create objects (tables, stores procedures, triggers) on master DB. If yes, what am I doing wrong? If no, why?

My guess is that SQL Azure is not less than the On premises DB. It must be allowing objects creation on master DB.

For the answer of the question, you can read Joseph's. Azure SQL, so far, is less than the premise DB except its cloud-based advantage. There're many limitations like less T-SQL features supported. Azure SQL Database Transact-SQL Reference

more links for your reference.
Preview features
Managing Databases and Logins in Azure SQL Database