Change dbo user login

After a database move the dbo user login is orphaned from the new master
sysusers.
How can I change the dbo user login name?
TIA,
Fred
Hi Fred
Change the owner of the database with sp_changedbowner. Then the dbo user
will map to the new login.
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Fred - change net to nl to email" <hfblum@.wxs.net> wrote in message
news:uNcD3E2uEHA.1312@.TK2MSFTNGP09.phx.gbl...
> After a database move the dbo user login is orphaned from the new master
> sysusers.
> How can I change the dbo user login name?
> TIA,
> Fred
>
|||The problem is not just affecting the moved database. All new databases
created have dbo with domain\administrator as login name. This NT account
has been renamed because of security issues.
How can this be corrected?
TIA,
Fred
"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:eOSV092uEHA.2804@.TK2MSFTNGP14.phx.gbl...
> Hi Fred
> Change the owner of the database with sp_changedbowner. Then the dbo user
> will map to the new login.
> --
> HTH
> --
> Kalen Delaney
> SQL Server MVP
> www.SolidQualityLearning.com
>
> "Fred - change net to nl to email" <hfblum@.wxs.net> wrote in message
> news:uNcD3E2uEHA.1312@.TK2MSFTNGP09.phx.gbl...
>
|||When created, a database is owned by the LOGIN name creating it. If your
people are login in as domain\administrator, then that will be the owner of
any databases they create.
They will either have to login using SQL Server security as 'sa', or under
some other domain name, or you will have to run sp_changedbowner.
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"Fred Blum" <h.f.blum@.marketconnectnospam.nl> wrote in message
news:uRiD6h$uEHA.3624@.TK2MSFTNGP09.phx.gbl...
> The problem is not just affecting the moved database. All new databases
> created have dbo with domain\administrator as login name. This NT account
> has been renamed because of security issues.
> How can this be corrected?
> TIA,
> Fred
>
> "Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
> news:eOSV092uEHA.2804@.TK2MSFTNGP14.phx.gbl...
>
sql

challenge (permission denied) no sense, please help !

I have a database named MCP and a SQL Login MCP_USER (not sysadmin).
MCP_USER has db_datareader, db_datawriter and db_ddladmin permissions on MCP
database
I created a JOB (simple select on the MCP database) = select * from
mcp.tbl_test
the JOB has the MCP_USER as owner
the MCP_USER has SQLAgentOperatiorRole, SQLAgentReaderRole,
SQLAgentUserRole and targetServersRole permissions on the msdb database
if I try running the JOB with MCP_USER (that is what I need) I got: "the
EXECUTION permission was denied on the object sp_start_job, database msdb,
schema dbo"
This looks like a easy issue, but i think I've done all steps needed.
All I need is run a JOB with a non sysdmin user ..
thanks heaps ..
Julio MattosJulion
One question , when you start the job , did you log in as a MCP_USER ?
BOL says
Members of SQLAgentUserRole and SQLAgentReaderRole can only start jobs that
they own. Members of SQLAgentOperatorRole can start all local jobs including
those that are owned by other users. Members of sysadmin can start all local
and multiserver jobs.
"Julio Mattos" <JulioMattos@.discussions.microsoft.com> wrote in message
news:87A1E4F0-2C93-4821-AA51-2C2CE0E11D77@.microsoft.com...
>I have a database named MCP and a SQL Login MCP_USER (not sysadmin).
> MCP_USER has db_datareader, db_datawriter and db_ddladmin permissions on
> MCP
> database
> I created a JOB (simple select on the MCP database) = select * from
> mcp.tbl_test
> the JOB has the MCP_USER as owner
> the MCP_USER has SQLAgentOperatiorRole, SQLAgentReaderRole,
> SQLAgentUserRole and targetServersRole permissions on the msdb database
> if I try running the JOB with MCP_USER (that is what I need) I got: "the
> EXECUTION permission was denied on the object sp_start_job, database msdb,
> schema dbo"
> This looks like a easy issue, but i think I've done all steps needed.
> All I need is run a JOB with a non sysdmin user ..
> thanks heaps ..
> Julio Mattos|||Hi Uri,
yes I am logged in as MCP_USER. The good news I found the issue. I had
assigned MCP_USER to SQLAgentOperatiorRole, SQLAgentReaderRole and
SQLAgentUserRole, but I just need to assign to one role not all the 3.
MCP_USER is SQLAgentOperatiorRole only and its working fine. If you want to
understand better why, have a look to the role descriptions. Basically one
role was overlaping the restrictions to another role.
thanks a lot
Julio
"Uri Dimant" wrote:

> Julion
> One question , when you start the job , did you log in as a MCP_USER ?
> BOL says
> Members of SQLAgentUserRole and SQLAgentReaderRole can only start jobs tha
t
> they own. Members of SQLAgentOperatorRole can start all local jobs includi
ng
> those that are owned by other users. Members of sysadmin can start all loc
al
> and multiserver jobs.
> "Julio Mattos" <JulioMattos@.discussions.microsoft.com> wrote in message
> news:87A1E4F0-2C93-4821-AA51-2C2CE0E11D77@.microsoft.com...
>
>|||Thanks for the info Julio
"Julio Mattos" <JulioMattos@.discussions.microsoft.com> wrote in message
news:9D0D446D-2961-44DC-8D61-ED5B6ED12CF1@.microsoft.com...[vbcol=seagreen]
> Hi Uri,
> yes I am logged in as MCP_USER. The good news I found the issue. I had
> assigned MCP_USER to SQLAgentOperatiorRole, SQLAgentReaderRole and
> SQLAgentUserRole, but I just need to assign to one role not all the 3.
> MCP_USER is SQLAgentOperatiorRole only and its working fine. If you want
> to
> understand better why, have a look to the role descriptions. Basically one
> role was overlaping the restrictions to another role.
> thanks a lot
> Julio
> "Uri Dimant" wrote:
>