June 27, 2008 at 11:52 am
I'm hoping someone can shed some light on this for me: If you're calling a stored procedure from some client, should the driver that the client is using to connect to SQL Server have any affect of what is or isn't supported within the procedure? I've ran into two situations here that are perplexing to me.
We have two different apps that are using jdbc drivers to connect to SQL Server. In both cases they're executing stored procs on the server. In one case, the call blew up becuase I had BEGIN and END transactions within my code. When I commented out this code, it ran fine. In the other case, in my proc I'm using xmcmdshell to make a bcp call. When I execute in Mgmt Studio it runs fine. When i executed it from within this app, with a different jdbc driver, it actually crashed the server!
I don't get this. Shouldn't what happens inside the proc not matter to the client and be independent of the driver? Why does the driver care what I do inside my stored procedures?
Thx!
H
June 27, 2008 at 12:07 pm
Your situation sounds a bit fishy, but the driver does need to comply with the way the database engine accepts queries and parameters and it also must comply with the way the database engine returns data, messages, and other output. That is why drivers change with the version of the database engine.
Make sure the jdbc driver you are using is compliant with the version and service pack of SQL you are running and you have the appropriate versions of anything else the driver depends on.
As far as the server crash because of a call in a stored procedure through the jdbc driver - that is very odd. It could be something to do with the way the feedback from the command line gets returned and the driver not being compliant, but typically something like this would cause client-side failures.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply