Greetings!
Please help me with the following extremely odd stored procedure behavior on MS. SQL Server 2000.
I have a stored procedure that is executed remotely. When it is executed in our office test environment, the Profiler shows a perfect sequence of execution & return of results.
However...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.