I've got a bit of a puzzle. I have a job that restores the production databases to reporting servers every morning, then runs a step to fix the logins so they have permissions to the restored databases.
Basically, it loops through all the logins, and for each one it runs:
When the job runs automatically, it gets partway through the list, then fails, but I don't see why. If I run the stored procedure, it completes. If the users are already in the database, I will get the message:
User, group, or role 'Angie' already exists in the current database.
But the SP keeps running until they are all processed.
Is there some limiter that causes it to fail after a certain # of errors in a scheduled job?
The scheduled job processed 6 of the 20 logins, even though "Angie" is first and throws an error. I can run the SP manually and after all the logins have been processed and in the DB, they all throw errors, but the SP at least runs all the way through.