January 26, 2016 at 12:06 pm
I'm still trying to wrap my head around Azure, I've only been using it a couple of weeks. So far it's been pretty interesting with some definite learning curves.
So here is my issue. I am a subscription co-admin which includes me in the owner role on the SQL Servers. This allows me to do pretty much anything...create/delete a DB, manage settings etc. However, I can't actually see the databases listed under a server BUT I can select one from the portal. I also can't export a DB to a storage account unless I use an SQL login. As far as using an SQL admin login to do an export, I suspect this may be an intentional layer of security. Unfortunately, I haven't been able to confirm that yet as I'm still going through documentation.
Does anybody familiar with Azure know if this behavior is intentional?
FYI - I'm only doing an export to have a final copy of the DB before being decommissioned; not as a backup solution.
February 12, 2016 at 8:24 am
I'm not sure if this is intentional, but it's probably an artifact of the way in which Azure has evolved. The subscription people have tended to be in charge of the payment and resources, but this is separate from the process of working with the databases.
I agree, it can be strange to access the portal and create the resource, but have to move elsewhere to deal with it. I'm hoping some of this smooths out over time.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply