I realized that my database utility network owner user account is not the owner of a majority of the domains in the utility network. (I must have been using my personal user account when I created the domains.)
Is it best practice to have the database UN owner account also own all of the domains? Are there drawbacks to having an individual own the domains?
Solved! Go to Solution.
I would say it's definitely a best practice for the schema owner to own all domains as well as datasets.
As far as drawbacks to having individually owned domains, I could imagine some errors applying the asset package to an enterprise GDB. If you've already accomplished that without issue, the other concern down the road could be another administrator being unable to modify your domains. You can get creative and work around this in SQL Server, but it's not ideal.
I would say it's definitely a best practice for the schema owner to own all domains as well as datasets.
As far as drawbacks to having individually owned domains, I could imagine some errors applying the asset package to an enterprise GDB. If you've already accomplished that without issue, the other concern down the road could be another administrator being unable to modify your domains. You can get creative and work around this in SQL Server, but it's not ideal.