Hello,
I'm replicating from one server to another. The issue is that the objects
on the second server have a different owner than the first server. Is this
possible? If so, how do I set it up?
Jligda,
have a look at the article properties - there is the option to set a
different object owner there. Obviously the user must pre-exist on the
subscriber, but this can be done by selecting to apply a script before the
snapshot is run which uses sp_grantdbaccess.
HTH,
Paul Ibison
Showing posts with label owner. Show all posts
Showing posts with label owner. Show all posts
Friday, March 30, 2012
Saturday, February 25, 2012
Replication jobs owned by sa
The reason sa is often suggested as the owner of
replication jobs is that when the job runs, there is an
active directory lookup performed of the job owner. This
is the reason sa is used - no AD lookup required. The
jobs themselves are run under the authority of the sql
server agent so trusted/non-trusted security doesn't
really apply, as windows logins are always authenticated.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
So are you saying , that even when i change the authentication mode to
Windows only , the jobs will still run even if they are owned by sa
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:170001c4e8d4$3eea74c0$a501280a@.phx.gbl...
> The reason sa is often suggested as the owner of
> replication jobs is that when the job runs, there is an
> active directory lookup performed of the job owner. This
> is the reason sa is used - no AD lookup required. The
> jobs themselves are run under the authority of the sql
> server agent so trusted/non-trusted security doesn't
> really apply, as windows logins are always authenticated.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Correct. The owner of the job is not the login used to
run it, as this is a cmdexec type of job and therefore
runs as the agent.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
replication jobs is that when the job runs, there is an
active directory lookup performed of the job owner. This
is the reason sa is used - no AD lookup required. The
jobs themselves are run under the authority of the sql
server agent so trusted/non-trusted security doesn't
really apply, as windows logins are always authenticated.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
So are you saying , that even when i change the authentication mode to
Windows only , the jobs will still run even if they are owned by sa
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:170001c4e8d4$3eea74c0$a501280a@.phx.gbl...
> The reason sa is often suggested as the owner of
> replication jobs is that when the job runs, there is an
> active directory lookup performed of the job owner. This
> is the reason sa is used - no AD lookup required. The
> jobs themselves are run under the authority of the sql
> server agent so trusted/non-trusted security doesn't
> really apply, as windows logins are always authenticated.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Correct. The owner of the job is not the login used to
run it, as this is a cmdexec type of job and therefore
runs as the agent.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Replication Job Failed. Unable to determine the owner
A former employee at my organization created a replication job to back up our database. The developer has since left and his windows account was deleted. I'm now receiving this error:
SQL Server Scheduled Job 'Replication agents checkup' (0xFC17DD4EF8E5694E8B786EE54CF8AD0D) - Status: Failed - Invoked on: 2007-06-05 15:40:00 - Message: The job failed. Unable to determine if the owner (username) of job Replication agents checkup has server access (reason: Could not obtain information about Windows NT group/user 'username', error code 0x534. [SQLSTATE 42000] (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error 3621)).
How can I fix this? I looked under the Replication folder but didn't see anything.
In Object Explorer, look at the job in SQL Server Agent to see who owns it, and verify the account is valid.
|||That's for the help. I changed the owner but am now getting this error:SQL Server Scheduled Job 'Replication agents checkup' (0xFC17DD4EF8E5694E8B786EE54CF8AD0D) - Status: Failed - Invoked on: 2007-06-07 01:00:00 - Message: The job failed. The Job was invoked by Schedule 175 (Replication agent schedule.). The last step to run was step 1 (Run agent.).
When I executed the maintenance plan manually it worked, but it doesn't seem to work on the schedule. I've never created a maintenance plans so I'm going to look up some more information to see if I can figure out what is going to wrong.
Replication Job Failed. Unable to determine the owner
A former employee at my organization created a replication job to back up our database. The developer has since left and his windows account was deleted. I'm now receiving this error:
SQL Server Scheduled Job 'Replication agents checkup' (0xFC17DD4EF8E5694E8B786EE54CF8AD0D) - Status: Failed - Invoked on: 2007-06-05 15:40:00 - Message: The job failed. Unable to determine if the owner (username) of job Replication agents checkup has server access (reason: Could not obtain information about Windows NT group/user 'username', error code 0x534. [SQLSTATE 42000] (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error 3621)).
How can I fix this? I looked under the Replication folder but didn't see anything.
In Object Explorer, look at the job in SQL Server Agent to see who owns it, and verify the account is valid.
|||That's for the help. I changed the owner but am now getting this error:SQL Server Scheduled Job 'Replication agents checkup' (0xFC17DD4EF8E5694E8B786EE54CF8AD0D) - Status: Failed - Invoked on: 2007-06-07 01:00:00 - Message: The job failed. The Job was invoked by Schedule 175 (Replication agent schedule.). The last step to run was step 1 (Run agent.).
When I executed the maintenance plan manually it worked, but it doesn't seem to work on the schedule. I've never created a maintenance plans so I'm going to look up some more information to see if I can figure out what is going to wrong.
Subscribe to:
Posts (Atom)