Re: Problem with Sql Server

From: Sushil Chordia (sushilc_at_online.microsoft.com)
Date: 02/10/04 

Date: Tue, 10 Feb 2004 11:08:59 -0800

There is one difference between the way QA and SqlClient retrieve data, they
have a different default value for arithabort.

Can you try setting arithabort on and off before running your stored
procedure in either QA or your code to see if this is what you are running
into?
"set arithabort on" 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"JoshuaLuke" <josh@mentura.com> wrote in message
news:01E86EA8-BDB6-41F1-9CE7-315A3485FFE4@microsoft.com...
> I have a sproc on sql server that I am calling from an asp.net app using
the data application block v2 method ExecuteDataSet. The sproc returns data
that is bound to a datagrid. The problem is that the command times out when
being called through .net but only takes 1-3 sec when run from query
analyzer.
>
> I've used sql profiler to try to diagnose the problem, here are the
results:
>
> Command                                      Agent    CPU     Reads
Duration
> ------------------------------------------   ------   -----   ------   ---
-----
> RptInvRoyalty 126, '2/1/2004', '2/29/2004'   SQL QA     562     2187
1266
> RptInvRoyalty 126, '2/1/2004', '2/29/2004'   .net     26578   231648
30530
> ------------------------------------------   ------   -----   ------   ---
-----
>
> Things I have tried (sa account was used for all tests):
>
> - Executing the command as an sproc by passing the sproc name and the
parameters to the executedataset method.
>
> - Executing the command using CommandType.Text and passing the same string
I use in query analyzer (for example: "dbo.MySp 5, '01/02/2004'").
>
> - Executing the command by creating my own SqlCommand and other objects
directly (as opposed to using SqlHelper).
>
> - Executing the command using the oledb data provider.
>
> - Increasing both the command timeout and connection timeout to 120 sec
for all of the above.
>
> - Running the command against a backup db. It works the first couple times
but then starts timing out.
>
> - Running the command from different web servers.
>
> - Running both web server and db server on same machine.
>
> - Creating a new sproc with the same tsql code.
>
> - Using ExecuteReader and ExecuteNonQuery.
>
> - Running it in both c# and vb.
>
> - Stopping and starting the db server.
>
> - Rebooting the db server.
>
> Any help would be appreciated.
>
> Thanks,
> Josh

Relevant Pages

  • Re: Problems running remote batch copy from wshshell asp script
    ... differently than opening a command line and executing a program by ... just used the "NET USE" command to attach to the server i need in my ... >> from an internal development server a external server. ... >> trying to use the wshshell component to kick off a batch script that I ...
    (microsoft.public.scripting.wsh)
  • Problem using exec() from Java servlet
    ... Note that this error ONLY occurs when executing from a servlet. ... I am trying to run the help command on pcli.exe. ... That executable is on a different machine than the server, ...
    (comp.lang.java.help)
  • SQL server 2000
    ... osql command is not executing on Remote server ... After executing the above command I got time out expire messsage ... It is noted that 35 server is connected with the gateway where the osql ...
    (comp.databases.ms-sqlserver)
  • Problem with Sql Server
    ... - Executing the command as an sproc by passing the sproc name and the parameters to the executedataset method. ... - Executing the command by creating my own SqlCommand and other objects directly. ... - Running both web server and db server on same machine. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: dcdiag - advertising errors on newley promoted domain controller
    ... Can you do the following on uksccmads01 ... The problem may actually have nothing to do with the new server but the ... From a command prompt try and see if you get any additional info ... Skipping site UK-CCM, this site is outside the scope ...
    (microsoft.public.windows.server.active_directory)