For the benefit of exasperated developers in years to come, here's how I fixed it. Firstly, jump ahead to the step 4. I'm certain I'd done that prior to re-installing, but...

Well, at least I'm not going mad. Mine's apparently set to Alt-D

But that doesn't work, and neither does CTRL-ALT-J.

Thanks for your help everyone, at least it's confirmed that...

We've ended up just typing in the password multiple times when we load the solutuion. As you say, User Key is no use with multiple developers, Do Not Save isn't...

The vast majority of them...

We have our packages password-protected because they have credentials in them, and Project Deployment Model...

Thanks a lot for that, ShowPlan XML should be enough for me to investigate. It's an intermittent problem, so at least now I'm prepared for the next time it happens!

Thanks for all your replies, and apologies for the lack of information in my original post. I was going off the information I had at the time, which turned out...

Problem solved. The abc login was part of the 'sysadmin' role. Once I've taken it out of that role everything's working fine.

Thanks again for the help.

interestingly user_name() is returning as 'dbo', not 'abc' as I would have expected. I'll have a dig and see what's going on.

Thanks Steve

Thanks for the quick repsone. The default schema is set to 'abc'. I've tried changing that to dbo and back, to no avail. Similarly dropping and recreating the user didn't...

Almost, you missed out a SELECT, see above

the same worked for me. I assume it's because the SP being called is generating a lot of "(1 row(s) affected)" lines (over 20,000 in my case) which SQL Server...