Well I found the problem. With the help of the SQL Configuraion Manager I noted my SQL was on my 'D' drive. I knew I had a larger 135gb partition...

See below. Yes I know it says SQL express that's what's throwing me. Full SQL 2005 is installed. This is in a VM.

2012-12-04 10:28:24.28 Server ...

Okay, my bad. I was clicking the green check mark instead of 'Execute'. Finally remembered.

Doh!

Same thing, Command(s) completed successfully. Essentially I am writing a procedure to change the SQL name as we use images of systems to deploy to developers and SQL is pre-installed....

Understood, SA to execute jobs. What permissions are needed? He can see other databases  he does not manage but not his own. And he is a user in said database.

No, I did have orphaned users. I tried SQL 2000 Query analyzer from a suggestion by another admin. Sure enough, it worked. Cleared up the orphaned users and then I...