September 1, 2014 at 5:50 am
i have sql server 2008 SP1 installed on OS( windows server 2008).
i've placed my application folder of server drive and i call them from remote client machines.
if the client machine is xp,2003 the query execution is very fast from the server.
but if it is executed from windows 7,8 client machine, it takes lot of time, and most of the time it gives TIME OUT Error.
we checked using sql profiler, it seems like sql takes lot of time to verify the query.
i have resolved LLMNR protocol issue also, still the problem exist.
we have very powerful network so can't say there is network issue, as it works like charm on other OS.
September 1, 2014 at 5:59 am
I would guess that you're using different network libraries on the two OSes and that's responsible for the difference. Different settings will be used depending on your network library, and that can make a difference to query execution. Since you have already run a trace, have a look through it again, and (depending on what you set it to capture), you should have a row like this:
SET ROWCOUNT 0 SET TEXTSIZE 2147483647 SET NOCOUNT OFF SET CONCAT_NULL_YIELDS_NULL ON SET ARITHABORT ON SET LOCK_TIMEOUT -1 SET QUERY_GOVERNOR_COST_LIMIT 0 SET DEADLOCK_PRIORITY NORMAL SET TRANSACTION ISOLATION LEVEL READ COMMITTED SET ANSI_NULLS ON SET ANSI_NULL_DFLT_ON ON SET ANSI_PADDING ON SET ANSI_WARNINGS ON SET CURSOR_CLOSE_ON_COMMIT OFF SET IMPLICIT_TRANSACTIONS OFF SET QUOTED_IDENTIFIER ON
Compare this for the slow client and the fast client. Are any of the settings different?
John
September 1, 2014 at 11:01 pm
thank you for your response.
i tried with the steps you gave.
both Protocol are identical for XP and windows 7. i run a trace through profiler.
it seems like the application execution is slow...it takes time to execute application..(i guess)
because i found that query got executed very quickly.
i found that the time is consumed between clicking application and before query comes in profiler.
September 4, 2014 at 11:17 pm
I tried with a dummy .net application without sql connection....just few forms.
and i placed them on server 2008. and executed from windows 7 client machine.....
this worked very fast and smooth...
then i made a connection with sql 2008 database and just fetched date from sql server...
i followed same steps again..placed on server 2008 and executed from windows 7 Client machine.....
same situation occurred again....it took lot of time just to get date from server..
so the problem is still there.
Over all scenario is
Sql server 2008
|
Windows server 2008 R2
|
Windows 7,8 Client Machine
this combination makes the query execution very very slow....
where xp take only 1 minute to execute that process, windows 7 takes 25-30 minutes to execute a process with timeout error....
September 5, 2014 at 2:11 am
pyarakiku2004 (9/1/2014)
i tried with the steps you gave.
So what are the results? What did you see when you compared the SET options for the two clients?
John
September 5, 2014 at 5:06 am
it seems windows 7 and windows server 2008 R2 got some trouble....
i tried a lot but couldn't figure out what is happening...
windows server 2008 R2 and XP are working very fast.....
this issue is only with windows 7
September 5, 2014 at 10:19 pm
Finally I found the issue...
its Connection.Open();
when i request from Windows 7 client machine...
Connection.Open() Take lot of time to respond....;
no need to find what connection string should i try which will connect it quickly.
Data Source=#####;Initial Catalog=######;Persist Security Info=True;User ID=#####;pwd=####;
What else can i provide in this connection string which will connect quickly.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply