September 5, 2014 at 8:32 am
Hello there,
A problem is vexing me and I am wondering if someone else has encountered this and knows the solution. Setting up a test AlwaysOn Availability Group for one database.
However, whenever I restore the database to the replica server and join it, it ends up with my user account as the owner of the database.
Obviously I do not want a user account as the database owner, but since it is read-only I cannot modify it directly. If I were able to fail the AG over to the replica, I could change the owner then, but I cannot due to business requirements. this AG is to essentially serve as a replacement to log shipping.
I tried doing the backups and restores using EXECUTE AS login = 'sa', and yet it still shows up as my user account.
Anyone have any suggestions?
----
September 5, 2014 at 9:22 am
If there are no dependencies on the actual owner of the database (such as the application runs as that ID), then you probably do not need to worry about this. The problem is that the system tables in the master database have recorded you as the user, but if you look at the sys.database_principals table in the database itself, you should see the owner from the primary server.
September 5, 2014 at 9:30 am
would there not be an issue in the future if the user account was disabled?
that is my concern.
----
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply