How do I set the login name for a user?

[David Thielen]

Hi;

I have a user "dbo" as the one user for a database. Under properties
the radio button is set to Login name but there is no login name and
it's disabled so I can't set it.

How can I fix this?

thanks - dave

david@[email protected]
Windward Reports -- http://www.WindwardReports.com
me -- http://dave.thielen.com

Cubicle Wars - http://www.windwardreports.com/film.htm

 

[Cowboy \(Gregory A. Beamer\)]

dbo is a role, not a user.

I am not sure what properties you are talking about? What tool are you
seeing this in? And, how did you get to this "page" in the tool?

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://feeds.feedburner.com/GregoryBeamer#

or just read it:
http://feeds.feedburner.com/GregoryBeamer

********************************************
| Think outside the box! |
********************************************

 

[Jialiang Ge [MSFT]]

Hello Dave,

There are basically two possible reasons for the symptom that the dbo user
does not have a matching login:

1, If a database is created by a Microsoft Windows NT authenticated login
that is granted access to the computer that is running SQL Server through
group membership (such as BUILTIN\Administrators), the security
identification number (SID) stored in the sysusers system table in that
database does not have a matching SID in the syslogins system table.

2, If a database is restored where the dbo user's SID in the sysusers
system table is not matched with the SID in the syslogins system table.

If the dbo user does not have an explicit login, the solution is to change
the owner of the database to a user that has an explicit login. For
example, change the owner of the database to the system administrator (sa),
and then execute the following code:

exec sp_changedbowner 'sa'

Is this solution helpful to you? Please let me know if you still have the
problem after trying it.

Best Regards,
Jialiang Ge ([email protected], remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[David Thielen]

dbo is a role, not a user.

I am not sure what properties you are talking about? What tool are you
seeing this in? And, how did you get to this "page" in the tool?

Hi;

Here's what I am seeing. In SQL Server Management Studio I go to
Databases/KailuaTest/Security/Users and under that I have the user
dbo.

When I bring up the properties for dbo it has a Username of dbo and
under that are 4 greyed out radio buttons: login name, certificate
name, key name, without login. login name is grayed out.

The problem is to the right of login name the text box that lists the
username is blank And as it's grayed out, there is no way to set a
login name.

So I created a seconf user dbo2, set it to db_owner, and was then
goign to delete dbo - but it won't let me.

So how can I fix this?

thanks - dave

david@[email protected]
Windward Reports -- http://www.WindwardReports.com
me -- http://dave.thielen.com

Cubicle Wars - http://www.windwardreports.com/film.htm

 

[Jialiang Ge [MSFT]]

Hello Dave,

"dbo" cannot be deleted and it needs to be in every database by design:
http://msdn.microsoft.com/en-us/library/aa905208.aspx

According to the symptom, there might be some corruptions or missing
information in the system database. Dave, does this issue happen to all the
databases in the sql server instance? What is the result if we create a new
database? Was my suggestion in the initial reply helpful to you?

Because this issue is majorly about SQL server, I think you may also
consider posting the question to one of the managed SQL server newsgroups:
http://msdn.microsoft.com/en-us/subscriptions/aa974230.aspx#SQL
My colleagues dedicated to supporting SQL Server may provide better ideas.

Regards,
Jialiang Ge ([email protected], remove 'online.')
Microsoft Online Community Support

=================================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

This posting is provided "AS IS" with no warranties, and confers no rights.
=================================================

 

[David Thielen]

What I think happened is my username was changed from dave to david
(long story due to a bug in Exchange's IMAP server). So all the
databases created with dave as the dbo now have "" as the dbo.

How do I set sa as the owner of the database? I went to Security,
Logins, sa and tried to map it to a databse but got an error that I
cannot use the reserved name sa.

thanks - dave

Hello Dave,

There are basically two possible reasons for the symptom that the dbo user
does not have a matching login:

1, If a database is created by a Microsoft Windows NT authenticated login
that is granted access to the computer that is running SQL Server through
group membership (such as BUILTIN\Administrators), the security
identification number (SID) stored in the sysusers system table in that
database does not have a matching SID in the syslogins system table.

2, If a database is restored where the dbo user's SID in the sysusers
system table is not matched with the SID in the syslogins system table.

If the dbo user does not have an explicit login, the solution is to change
the owner of the database to a user that has an explicit login. For
example, change the owner of the database to the system administrator (sa),
and then execute the following code:

exec sp_changedbowner 'sa'

Is this solution helpful to you? Please let me know if you still have the
problem after trying it.

Best Regards,
Jialiang Ge ([email protected], remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

david@[email protected]
Windward Reports -- http://www.WindwardReports.com
me -- http://dave.thielen.com

Cubicle Wars - http://www.windwardreports.com/film.htm

 

[Cowboy \(Gregory A. Beamer\)]

That is not a user, in the traditional sense.

It may show up in the tool, but it is not a user you can use. Consider it a
database role or a superuser.

The sa account is "god" on the server. You can use it in connection strings,
et al, but I would highly discourage it. You are better to make a dbo roled
account (database god?), although that is not my first recommendation for
connections. It is best to only give the rights necessary to the account.
read and write priveleges are generally as far as I would go with an account
to read data from an application.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://feeds.feedburner.com/GregoryBeamer#

or just read it:
http://feeds.feedburner.com/GregoryBeamer

********************************************
| Think outside the box! |
********************************************