I'm trying to debug a problem along similar lines to this old question: http://stackoverflow.com/questions/1568852/sqldatasource-timeout-ok-in-management-studio
Complex stored procedure always times out when run from ASP.NET 1.1 via .NET SQL Client, but runs no problem from SQL Management Studio. I looked at sys.dm_exec_sessions to see what the settings were for the respective connections. For some reason, the connection from the ASP.NET app is using client_version 4 (SQLServer 2000 sp1) while the management studio connection is (appropriately) using version 5 (SQLServer 2005).
I assumed I'd have to change the connection string to prompt ASP.NET to use the correct version, but I don't see how or where to do that. Google is oddly unhelpful... can I specify the client_version that the ASP.NET app should use somewhere?
Any help is much appreciated.
(PS... the arithabort settings were also initially different for the two connections, but setting them both to "on" doesn't seem to help, unfortunately.)