Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
darkdusky
Aged Yak Warrior
591 Posts |
 Posted - 2008-11-10 : 11:58:32
|
| Hi,I have a stored procedure to copy a table from a linked server to my db. The proc runs fine when exec'ed, but not as a job. The linked server connection is fine.When I run job I get:Unable to perform a SETUSER to the requested username 'xxx' because the username is invalid for database 'xxx'. This lead me to:http://support.microsoft.com/kb/811031I tried the option:Be made using this security context .. But got same error.I have tried with the "Run as" in job step as the local user who is mapped to the remote login.Any advice?Also are there security implications using the 'Be made using this security context' option.Will this give other jobs higher permissions if they were going to fail? |
|
|
darkdusky
Aged Yak Warrior
591 Posts |
Posted - 2008-11-11 : 05:14:18
|
| I decided to use SSIS and "rely on SQL Server" to deal with permissions. |
 |
|
|
|
|
|
[Solved] linked server job