performance difference between query analyzer and .NET code.

Dear Sir,
I used dynamic SQL on stored procedure to do the paging in my site.
I often hit a connection time out problem with that dynamic SQl when I call
it from .NET code.
However if it run it under query analyzer, everything works fine.
Who can explain this to me and what should I do in this case?
regards,
Guoqi Zheng
http://www.ureader.comWhen you say "everything works fine", do you also mean that the execution
time in Query Analyzer is within the connection timeout you have set in your
.Net application?
ML
http://milambda.blogspot.com/|||> I used dynamic SQL on stored procedure to do the paging in my site.
> I often hit a connection time out problem with that dynamic SQl when I
> call
> it from .NET code.
> However if it run it under query analyzer, everything works fine.
> Who can explain this to me and what should I do in this case?
If "everything works fine" still means it's slow, and extends beyond the
timeout setting that ML mentioned, then everything is not working fine.
One thing you might try is a different paging approach. There are probably
a handful of samples here that will be faster and safer than dynamic SQL:
http://www.aspfaq.com/2120

performance comparision of different connection types

Do you know some performance differences between reading data from a stored procedure using:

1. OLE DB Connection and OLE DB Source

2. ADO.NET Connection and DatareaderSource

Przemo

If you could do some testing and share it here I'm sure people would be intreested in reading it.

-Jamie

Performance

Hi to all,
I know that we should close sql connection when it's complete its job for
performance and sql server's resources. But i can't find article or text
for
this subject on the internet. Or i know not true?
Could you share with me if you have like this article ?See other post.
"Erencan SADIRODLU" wrote:

> Hi to all,
> I know that we should close sql connection when it's complete its job for
> performance and sql server's resources. But i can't find article or text
> for
> this subject on the internet. Or i know not true?
> Could you share with me if you have like this article ?
>
>
>

Performance

Hi to all,
I know that we should close sql connection when it's complete its job for
performance and sql server's resources. But i can't find article or text for
this subject on the internet.
Could you share with me if you have like this article ?Hi
You don't say how you are connecting to the server! For instance ADO has a
close method for disconnecting a connection object
http://msdn.microsoft.com/library/d...r />
lose.asp.
It is not always a good idea to close the connection if you expect to
re-connect again soon after as the time taken to connect can slow down your
application, and creating/destroying the connection takes resources on the
server. This is why things like we applications use connection pooling, so
that a client can re-use an already open connection. This make more effectiv
e
use of the connections that are open and does will help limit the total
number of connections. [url]http://msdn2.microsoft.com/en-us/library/8xx3tyca.aspx[/url
]
HTH
John
"Erencan SADIRODLU" wrote:

> Hi to all,
> I know that we should close sql connection when it's complete its job for
> performance and sql server's resources. But i can't find article or text f
or
> this subject on the internet.
> Could you share with me if you have like this article ?
>
>

Performance

Hi to all,
I know that we should close sql connection when it's complete its job for
performance and sql server's resources. But i can't find article or text for
this subject on the internet.
Could you share with me if you have like this article ?Hi
You don't say how you are connecting to the server! For instance ADO has a
close method for disconnecting a connection object
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdmthclose.asp.
It is not always a good idea to close the connection if you expect to
re-connect again soon after as the time taken to connect can slow down your
application, and creating/destroying the connection takes resources on the
server. This is why things like we applications use connection pooling, so
that a client can re-use an already open connection. This make more effective
use of the connections that are open and does will help limit the total
number of connections. http://msdn2.microsoft.com/en-us/library/8xx3tyca.aspx
HTH
John
"Erencan SAÃ?IROÃ?LU" wrote:
> Hi to all,
> I know that we should close sql connection when it's complete its job for
> performance and sql server's resources. But i can't find article or text for
> this subject on the internet.
> Could you share with me if you have like this article ?
>
>

Performance

Hi to all,
I know that we should close sql connection when it's complete its job for
performance and sql server's resources. But i can't find article or text
for
this subject on the internet. Or i know not true?
Could you share with me if you have like this article ?See other post.
"Erencan SAÃ?IROÃ?LU" wrote:
> Hi to all,
> I know that we should close sql connection when it's complete its job for
> performance and sql server's resources. But i can't find article or text
> for
> this subject on the internet. Or i know not true?
> Could you share with me if you have like this article ?
>
>
>

Perf Mon creating large temp files

I am using a remote connection to connect to a specific server (13B) and I a
m
running a trace from there against another server (138). I have a template t
o
track performance points and am saving the results to a table. My problem is
that when I run this trace, I also am creating a very large set of tmp files
on the local C drive of 13B. The files are named nst1.tmp,prf3.tmp,prf4.tmp.
The C drive space is not very large so I max out the space quickly. I am
looking for a way to point the tmp files to another drive or elimate them
altogether.
ThanksNever go directly to a table. Place the files on a local hard drive first
and then import them later. Otherwise you will incur more overhead than you
need to. If you want to import Perfmon files take a look at the Logman.exe
utility.
Andrew J. Kelly SQL MVP
"MNDiver" <MNDiver@.discussions.microsoft.com> wrote in message
news:1F3F9BF1-5D66-4882-83A2-19C28F1522B1@.microsoft.com...
>I am using a remote connection to connect to a specific server (13B) and I
>am
> running a trace from there against another server (138). I have a template
> to
> track performance points and am saving the results to a table. My problem
> is
> that when I run this trace, I also am creating a very large set of tmp
> files
> on the local C drive of 13B. The files are named
> nst1.tmp,prf3.tmp,prf4.tmp.
> The C drive space is not very large so I max out the space quickly. I am
> looking for a way to point the tmp files to another drive or elimate them
> altogether.
> Thanks