Re: File Ownership failing for Domain Accounts

I think I found the root cause of the problem. It looks like the admin has
setup just about every instance of SQL Server I can access to start under a
local machine account. This is preventing lookups against Active Directory.

"Kevin D. White" <kevinDwhite@xxxxxxxxxxxxxxxx> wrote in message
news:ekLZFoAaHHA.2316@xxxxxxxxxxxxxxxxxxxxxxx
I am having a consistent problem on several instances of SQL 2005 setting
the ownership of database files to a windows user. This is not a login
problem but a file ownership problem. Here are the steps:

1. Right-click on any user database, e.g. AdventureWorks and select
"Properties
2. Select the "Files" page from the right-hand list
3. Click the elipsis "..." button to the far right of the "Owner:" label
4. Click the "Browse..." button in the pop-up "Select Database Owner"
window
5. Select any login that maps to a windows or domain account except for
members of the [NT AUTHORITY] group, e.g. [COMPANYDOMAIN\MyName]
6. Click "OK" on the Browse pop-up and then on the Select Database Owner
pop-up
7. Click "OK" on the "Database Properties" dialog to return to the main
SQL Server Management Studio application
8. Repeat steps 1 & 2
9. Notice that the "Owner:" field is now blank

This problem is occuring on multiple instances of SQL Server 2005 at both
SP1 and SP2 patch levels. All of the instances are set to mixed security
mode. All of the windows accounts I have tried are in the local server's
Adminstrators group. Setting ownership to a pure SQL account or a member
of the local [NT AUTHORITY] group works just fine. I have even attempted
to set the permissions manually using ALTER AUTHORIZATION and the
sp_changedbowner proc. Nothing seems to work and I never get an error
message or log.



.

Quantcast