SQL Azure automated export fails silently with new user. Permissions perhaps?

Question

Using the Windows Azure portal I tried to complete the configuration required for the new (July 2013) automated export feature.

My default SQL Azure users password is more than 12 characters long so was rejected by the portal. I created a new user and login, set the permissions EXEC sp_addrolemember 'db_owner', 'myuser'; but even though these details are accepted by the portal the automated export does not occur, failing silently.

Other users have it working with the user that was created when the database was created, but others also have my problem: they can't get it to work with a new user.

If I list the user roles via

SELECT
    dbU.[name] AS [user]
    , dbGp.[name] AS [Group]
FROM
    sys.database_role_members AS dbRM
    JOIN sys.database_principals AS dbU ON dbU.[principal_id] = dbRM.[member_principal_id]
    JOIN sys.database_principals AS dbGp ON dbGp.[principal_id] = dbRM.[role_principal_id] 

all the users are db_owner - I can't see any difference between the default user and the new user.

Any ideas?

Answer 1

When performing a CREATE DATABASE X AS COPY OF Y operation you can only copy the database using the login that created the database on SQL Azure in the first place (As indicated in this article)

I could not see a similar restriction noted for the automated exports process however this is likely the case for Import / Export operations against a database on SQL Azure.

It appears that you would have to use the original login.

Edit: Under the Cost Impact section of this article, it indicates that prior to exporting the database, a copy is created on the same server. This means that you do indeed need to use the login that originally created the database.