Question

I have a vb.net app using plain old ado.net to run a s’proc on the database server. The proc simply inserts a record that contains binary data.

When this executes, I can see the exec call on the proc being made from within sql profiler.

ado.net claims everything worked, no errors. However, a record isn’t inserted. There are no key collisions or anything like that.

I copied the query I saw from profiler and ran it directly within management studio. When I run it there, the record is inserted.

I have no idea what to even check next. Thoughts?

---

Found the answer. I’d go ahead and delete this but I’m sure I’ll forget someday and run into the same problem.

For whatever reason, sql server and ado.net were conspiring against me. The user account I was attempting to execute the s’proc under did not have execute rights for it. After I set those rights then it was proceeding as normal.

Now, the problem I have is that there should have been some type of warning, error, exception, whatever that said “hey, you can’t do this” instead of simply saying “Everything is good” But that’s a question for Microsoft.

Thanks all.

Answer 1

It was a security rights issue. See post.