Hi Cetin,
The SQL DB I am querying is a third Party DB, I don't have control over their DB, I cannot create any indexes etc. So the query only returns 55 rows & 6 columns of data, it is a very complex query invloving multiple SQL DB's, so the processing time is ok considering the compexity involved, So I used the following command before my SQL Statement.

set nocount off
set arithabort on
set concat_null_yields_null on
set ansi_nulls on
set cursor_close_on_commit off
set ansi_null_dflt_on on
set implicit_transactions off
set ansi_padding on
set ansi_warnings on
set quoted_identifier on


It works much faster now just a little more than SQL QA. I don't know which command did the trick, as I did not have time for an elimination process. Thank your for your help.

>>HI Guys,
>>I am using visual Studio.net 2003 with sql server 2005. When I run a SQL Statement in the query analyzer it takes 11 seconds, when I put the same code in my c#/ASP.net program it takes 3 minutes and then times out. Can anyone help me.
>>
>>in code i am using sqldataadapter.fill to fpopulate a dataset
>>
>>TIA
>
>Fred,
>Not really an answer but a check.
>If you create a simple SQL statement that'd execute fast and return just a few rows from same database and table(s) does it execute without a problem? If yes then my suspicion is that incoming data is so big that .Net is running of memory space to create the dataset (with lots of disk swap) or a connection loss problem. If not then sounds to be a connection problem.
>PS: With .Net 1.1 it was much slower than it is with 2.0. Taking 11seconds in query analyzer, I think it is a huge result. Do you have a chance to test it with say VFP and/or htm with ADO and some J/VBScript?
>Cetin