When I create a job it typically creates the job with my account as the owner, e.g. domain\login. The jobs fail regularly because SQL Server is unable to determine if my login ID has server access. This is stupid, and another typical problem I have run into for years. Anyway, since this occurs often, when I create a job I change the owner to SA so that SQL Server will run it without complaint. I have noticed lately though, that if I change this in SQL 2008, and select "sa" from the list of users, I get the message "No object was found with the name "[sa]", but objects with names containing "[sa]" were found. Select one or more names from this list of click Cancel to re-enter the name."
It presents a list of users, of which none contain the string "[sa]", except, low and behold, "[sa]". See attached image.
This seems to be the dumbest thing I have ever seen SQL Server do.
Anyone else ever run into this?
Learning something new on every visit to SSC. Hoping to pass it on to someone else.