I have a SQL Server service connecting to a Database in order to execute a few stored procs.
For some reason, the service only recognizes a subset of the actual procs on the server. Now, I know there are limitations to what types of procs it can use. However, what's REALLY odd is that when we deploy to a different environment, I get a DIFFERENT subset of procs. The procs that do show up in DEV, do not show up in QA.
The main difference in environments is that QA has SQL on a different box - but selecting that "On different Sql Server" setting didn't seem to have any effect at all.
Also, Qa is using Kerberos authentication. But if open SQL Manager on the K2 box, and login using the K2 service account, we can see and execute all of the procs - so I don't think it's a permission issue. But it sure behaves like it might be.
Any Ideas?
Thanks!
